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.

Brilliant, thanks Phil. Appreciate your explanation. That second regex works perfectly!

Great, thanks Joel – I'll check that out. Mango reports that the JVM free memory is 144 MB and JVM maximum available memory is 241 MB.

Thanks Jared! I had somehow overlooked that in the examples - I will give that one a shot. Cheers!

Yes, Bosch sensors are excellent. Great documentation, unlike most "Chinese" sensors. Can't wait to get a BME680. It suppose to sense Volatile Organic Compound gases., as well as temp, humi and pres..

Oi. We recently changed our branching and it looks like my fix didn't get pulled into the main branch. My mistake. I have just put 3.1.1 in the store and it definitely has it. Sorry about that.

Yes you can delete that folder and the NoSQL files in the /backups folder. You are deleting all the data that is stored in the NoSQL database so be sure you have imported it into H2 :)

There is not an entirely direct method in the SSH data source for that that I know of. You cannot do output=$(command); export output; then do echo $output; in another data point. I think this is because every point runs it its own channel (not session, but channel). So, you have two options: Make the first point on the data sources query the script and write the value to a file (it could also parse a value if need be). So, python readSensor.py > ~/DHT22-live-data; cat ~/DHT22-live-data | grep -o "Temp1: [0-9]+" | grep -o "[0-9]+" and then every data point below can read the data from that file. It would be nice if we had a way to explicitly order the points in the SSH session. There are probably still potential improvements to be made to the SSH data source. Or... Use point links or meta points to parse out the individual values from the SSH point, which is then just an alphanumeric doing python readSensor.py and you can do regex in the point link or meta point to extract the value, i.e. return /.*Temp1 (\d+) .*/.exec(source.value)[1]

Hi Jeremy, We recently discovered this issue as well and will have an update available soon. Thanks for letting us know.

Ah yes, same bug. I'll make a note of that and re-open it while closing #489.

Generally true Hussam, but not always. If a datasource fails polling some points but not others, it will only update the times of those it successfully polled. Or, if the entire poll fails, no timestamps will be updated. The timestamp displayed for a point on the data point details page does reflect the cache's perspective, meaning what the value of a point is and when that value was reported last. Other ways of accessing data can get you timestamps that reflect those which will ultimately be logged in the database. For example, compare two meta scripts being run on a point receiving 1 second updates, but not always changing (I used a virtual binary point on random): It is set to log on change. return new Date(p1.time); //returns the date of the last update return new Date(p1.lastValue(0).time); //returns the date of the last logging

OK thanks, that seems straightforward enough. For the record: I've created a high level detector on a kW measurement point that should fire when the customer connects for the first time. I also created an empty binary meta-point called 'one-time detector'. I set up my event detector to set this meta-point to 1 when the high kW condition triggers. On my 'one-time detector' point, I set an event handler to send an email when the point value is 1.

I agree, this would be a great feature and we have been thinking alongs the lines of a tool to allow you to remotely manage the whole mango configuration but this would be a good place to start.

I was just playing around with this and found that if you want to use the query 'select count() from datapoints' you need to use the data source as a 'non row based query' and then set the column name to 'Count()'. You can see this in the test utility if you look at the Column name, its shown as COUNT(*) when you test the query. You could also use this query if you want to have a specific column name: select count(*) as pointcount from datapoints; As for your last question you can put this all together like this: SELECT ( SELECT COUNT(*) FROM datapoints ) AS pointCount, ( SELECT COUNT(*) FROM datasources ) AS datasourceCount, ( SELECT COUNT(*) FROM events ) AS eventCount, ( SELECT COUNT(*) FROM eventHandlers ) AS eventHandlerCount, ( SELECT COUNT(*) FROM users ) AS userCount FROM dual The thing to notice here is the keyword 'dual' at the end, this is required as you cannot perform a select without a from clause and the dual table that all accounts can access for common needs and it has one record. Just make sure you change the data source back to not use the row based query. FYI To format as code just make sure your lines are all indented by a tab or 4 spaces and has whitespace lines above and below.

Hi Terry It is definitely possible to have one listener receiving data from mulitiple publishers, I have done this by accident a few times :-} Do you know whether I can have multiple listeners configured and all using the same port? Would that be recommended? I would like to avoid having too many ports open. Kind regards

Jeremy, Due to the 'login required before getting data' restriction you will have to create an intermediate step that would login, collect the data, then push it to Mango somehow. To my knowledge Mango doesn't have a module that would do this out of the box. Some Ideas: See if you can get/setup a public api for SunnyPortal Write a small script/app in your favorite language that would retrieve the data as you mentioned above Build a custom Mango Module to do this.

Hi Jeremy, Something like this has been on our development path and I agree would be a really great thing for everyone. I'm not sure of the time line but it's something I'd personally like sooner than later so we'll see what we can do. Thanks,

Hey Jeremy, The update rate is stored in the serialized data so it's not going to be available in an SQL statement. The only thing I can think of without writing any Java code would be to grab it out of the JSON from the export page or the API.