I've got users receiving pop-up events/alarms that belong to other users. They also show in the events page. How can I make sure users only receive their own events?
Mango 3.7.7
Posts made by till
-
Users receiving pop-up events/alarms that belong to other users
-
RE: Email send failure
Turns out that the SEND TEST EMAIL doesn't send a test email using the values that you just entered but using the values that are saved. So you cannot test before saving.
-
Email send failure
Hi,
I'm using Mango 3.7. Recently I noticed I don't get any email alerts from Mango anymore. Event handlers are set up to send emails and they worked for years and years.
I went to email settings and confirmed the SMTP settings are still correct. I also tested the settings in a different tool and they definitely work.
When I hit the button to SEND TEST EMAIL, I get no email but an error message in Mango: Error sending email to 'test@mytestcompany.co.uk' — Email send failure
What can be wrong?
Cheers T -
Caching issues
Re: Problem with userModule caching
Is there any solution out there that does not require fiddling with NGINX?
THanks
-
RE: How to connect to the mango database (for resetting admin password)?
@terrypacker Cool that works. Removing both .h2 and .db was the key. I'll
Thanks -
How to connect to the mango database (for resetting admin password)?
I've got the Web Console running (sudo)
Web Console server running at http://127.0.1.1:8081 (others can connect)
But it cannot find the DB. The path is correct, there is a
/opt/mango/databases/mah2.199.h2.db
-
RE: Too much data for a datapoint
@terrypacker said in Too much data for a datapoint:
I shall give that a go, thanks.
-
Too much data for a datapoint
I get this exception
device_hub 'myDevice': Script error in point "myPoint": com.infiniteautomation.tsdb.IasTsdbException: com.infiniteautomation.tsdb.impl.BadRowException: Exception trying to serialize bytes: Data length can not exceed 65536
when trying to stuff too much into a virtual datapoint.
What other options do I have for storing a large amount of alphanumeric data. It's JSON, so I'm eying the JSON store but can't find any working examples of how to access that from a meta datapoint.
The code in https://forum.mango-os.com/topic/4495/calling-json-store-item-in-scripting-datasource/2?_=1630557115032 gives me another exception:
java.lang.RuntimeException: java.lang.ClassNotFoundException: com.serotonin.m2m2.Common.getBean
I need to publish these JSON objects to another mango instance eventually, which works fine with my datapoints.
-
RE: Script context points as enumerable
So I found this on CONTEXT_POINTS
CONTEXT_POINTS CONTEXT_POINTS is a variable declared in all scripting environments. It is a map of variable names to context point runtimes.
Is there more documentation somewhere?
.
Your example gives me a list of elements like this:
DataPointRT(id=1, name=MyPoint) DataPointRT(id=2, name=MyOtherPoint)
From there, how do I get to the full datapoint details, like value, last value, timestamp etc?
Where do I find out more about context point runtimes
Thanks
-
Script context points as enumerable
Hi,
I was wondering if there is any way to iterate over all context points in a meta datapoint script, without spelling them out?
I want to write a generic script that is oblivious to them but can still access their values.
E.g. dumping all their values to an error log if something goes wrong.
Thanks -
RE: How to purge/delete data point history programmatically
@joelhaggar Many thanks for your swift responses.
I expected no logging to not hold the value for long enough for my purpose. But that works - currently.
This way it's storing the value in memory only, instead of in the database, right? So in a fault situation, resulting in a Mango restart, that value is gone?
Cheers
-
RE: How to purge/delete data point history programmatically
@terrypacker, I had abit of a look.
I realise that I can actually avoid this if there's an option to only keep the last (few) value(s) in the database and purge everything else.
Of course there is the purge option in a data point but it's not very much customisable. Setting it to purge daily (fixed at 3.05am apparently) is too often but weekly is not often enough. Ideally I just keep a single value.
Even better would be a way to only update the current value and not create a history of values in the first place. I'll never need any historic value, just the current one. Is there a setting or a specific data point type that allows this? I currently use a virtual data point.
Thanks!
-
RE: How to purge/delete data point history programmatically
Thanks @terrypacker,
I'll read up on this. -
How to purge/delete data point history programmatically
Can you, from a meta data point script, purge the history of another data point? How?
Thanks -
Alert: A context point is unavailable
I keep getting alerts like these even though the relevant points are NOT disabled.
'Data Modifier Datasource': A context point is unavailable in point "MyPoint" because Point with xid XY_DP_afea8094-77ea-4bb8-b673-5c7c27356ed7 for variable named 'myPoint' is disabled
This one is currently an active event (for 8 hours now) but I can clearly see that the referenced point with that XID is not disabled. What else could be behind the message? It's a PTCP point, so could it be caused by connection issues with the originating device?
Saying that, though the originating device is connected well and truly, the point is enabled and receives all values just fine.
-
RE: Config Import
@joelhaggar said in Config Import:
To set a PTCP data point it will send the set command down to the originating data point.
Ah! That's very good to know, thanks for that note. I wasn't aware the PTCP points are working in both directions like that.
-
RE: Config Import
Follow-up question - I seem to not be able to import values for points that are published to me via Persistent TCP. And that's just consequential as I cannot set the value manually either. However there is an option to make it settable and there is an input field to set it. So... can you set a Persistent TCP data point manually or not?