Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

That is a kind sentiment to share, surely!

Hi everyone, Thank you for all the advice. The information is very helpful. Best regards Ramhuzaini

Hi psysak, is that instance up to date? If not, Jared's explanation of the permanent fix toward the end of this thread may be of interest: https://forum.infiniteautomation.com/topic/3551/data-sources-does-not-appear/14

Lovely job, thanks Phil.

Upon a screenshare with Fox, we discovered there were \n and null characters in the incoming bytes that were not being matched and consumed by the serial data source, which caused the data source to seize up when these characters started clogging the buffer. A combination of rewriting the regex and preventing the nulls from transmitting brought this issue resolution! Edit: A similar issue happened again after I proclaimed resolution. This led me to a concurrency bug in the virtual serial server socket.

Looks like i'm going to have to find a way to upgrade sometime... Thanks man. Will see what I can arrange...

Perhaps, I can't say what the original intention was. To me, it seems like it was for a new meta point, where you enabled it at some time and it begun to acquire data, then you can generate history without having to figure out when you enabled the point.

Thanks Phil, I hacked up the current watchlist code from source and did my own in the meantime to get around the issue. Also enabled me to change how the timestamp is displayed too. I also noticed a nodeJS version of the UI. Any idea when that might be ready to work from? Would enable me to separate mango from the dashboard server wise.

Hi BlueSoft, welcome to the forum! Yes, I can confirm the problem. I found the cause and fixed it, which will be in the next 3.5 release. Thanks for bringing this to our attention! The problem is that the active / inactive scripts are not being set on the import, which means you cannot create a new event handler that is using scripts or modify an existing script through the configuration import / export.

@joey-uson When I post this issue I'm using Chrome and when I change to FireFox the problem disappear. No Idea what causing Chrome to hinder multiple addition in a folder

Nicely identified Phil, glad I could be of assistance,

Hi KroniK907 Thanks for bringing that to our attention! It should be working again.

Thanks Phil, all is good here. I'll just wait for the new release.

Okay, understandable.

@craigweb said in HTTP 500 internal Server erro: @Jared-Wiltshire We in the same building. I noticed he was using IE and quickly opened chrome and it worked first time. Tried to replicate it again on my PC with IE but couldn't get mango to load up on IE on my PC and then got side tract by something else. Ill try replicate it again tomorrow. To answer the first question it was to upload a file to the file store. Thanks, I'd be interested to know what the error was. That said, Internet Explorer is not a supported browser, I'm not surprised it failed.

Well I certainly have this configured under the Scheduler Events tree in Event types under the Event Handlers page. Oh I see! man after all this time.... and I never even once noticed the type was a drop down. Need more coffee... And a holiday I think.. Thanks Jared!

Still occuring, just FYI: [image: V4Xw7ed.png] Happened when I tried to make a new post

Just wanted to ask, how do I apply that fix? Don't want to bring anything down when I apply the change.... Alas it won't be released until 3.4 probably. But, you shouldn't really need it. It only prevents the extra empty serial events, but those shouldn't really cause problems. I'll use your datasource and point as a testing baseline and will fire random text to it. Great! Let us know how it goes!