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.

@sean You cannot query values per se, that's not the intended purpose of a time series DB. One suggestion I have is generating values and filtering the output based upon the provided timeframe, the input field, and displaying those timestamps for those records entered. The other is having a dedicated virtual datasource of virtual points whose Xids align with the accessCardID numbers and updating the corresponding datapoint everytime that accessCardID is entered into the system... Fox

@ryanlo To answer your initial question, the default login is still admin : admin. The easiest way to do a reset would be to stop Mango, move the database (move it to root ~/) from the /opt/mango/databases/ directory (from directory use, mv mah2.200.* ~/ command), then restart Mango. Similar direction could be found on our document site, you will not need to do the restore since this is a new unit. Thank you!

@MaP Understandable, that's why I went with the reverse proxy route, using ip tables is too low level in the OSI for the CORS related issues in the application layer. You may be able to set the env.properties to set the ip address of the interface you're trying to access to force it to only listen on that host ip address. See if that bears any fruit... Fox

@emeinig I got it resolved with a workaround. I'm going to post what I did for posterity and to hopefully help anyone who might come across the same issue in the future. What I ended up doing is creating a scripting data source. The datasource uses Rhino as its scripting engine so you can use some Java in it. With the Java, you can read/write to files and leverage the "Everything is a file" philosophy in *nix systems. The code: // import the file reader var FileReader = java.io.FileReader; var BufferedReader = java.io.BufferedReader; // import the writer. We must use OutputStreamWriter to write to device files var OutputStreamWriter = java.io.OutputStreamWriter; var FileOutputStream = java.io.FileOutputStream; // Be careful because this could change on us depending on how many USB devices // are plugged in var serial_port = "/dev/ttyUSB0"; // Initialize a bunch of blank strings to store measurements var max_time_measurements, temp_and_pressure, wind_attrs, solar_and_precip = new String(); // Set up the writer var file = new FileOutputStream(serial_port); var output = new OutputStreamWriter(file); // Set up the streamer var fr = new FileReader(serial_port); var br = new BufferedReader(fr); // Write the measurement command to the serial port and flush to ensure the // buffer is empty for the next command. output.write("0M!\r\n"); output.flush(); // The sensor takes around 3 seconds to return 9 values, so we sleep for 4 // seconds to give it a generous margin RuntimeManager.sleep(4000); // Now we write our data commands to get it all. output.write("0D0!\r\n"); output.flush(); output.write("0D1!\r\n"); output.flush(); output.write("0D2!\r\n"); output.flush(); output.close(); // readLine will read the return values max_time_measurements = br.readLine(); solar_and_precip = br.readLine(); wind_attrs = br.readLine(); temp_and_pressure = br.readLine(); //split the 0D0! result var solar_and_precip_array = solar_and_precip.split("+"); solarRad.set(solar_and_precip_array[1]); precipitation.set(solar_and_precip_array[2]); lightningStrikes.set(solar_and_precip_array[3]); //split the 0D1! result var wind_attrs_array = wind_attrs.split("+"); windSpeed.set(wind_attrs_array[1]); windDirection.set(wind_attrs_array[2]); gustWindSpeed.set(wind_attrs_array[3]); //split the 0D2! result var temp_and_pressure_array = temp_and_pressure.split("+"); temp.set(temp_and_pressure_array[1]); vaporPressure.set(temp_and_pressure_array[2]); atmosphericPressure.set(temp_and_pressure_array[3]); The code isn't the prettiest or most elegant but it does work. Just make sure you have the necessary variables created as data points and that they're settable and you're all good to go.

@tomatopi We are still working on documentation. I know it has been a very slow process but we are adding what we can to the doc sites (v4 and v5) as well as adding scripts to our script-examples in GitHub.

@terrypacker Fantastic, thanks Terry! Looks like I'm on the right track! Thanks I'll give it a go! Fox

@sean Are you providing a JWT key in the request ?

@fishfacs so you don't have noSql then. There should be a pointvalues table in your h2 db that is populated with data then. Fox

@CraigWeb mango version is 3.7.12 this datapoint is temperature sensor point so, recorde is normaly 2x °C so 4376.54 and 459.62 is incorrect, so I want to reset value or delete this 2 values in timestamp [PointValueTime(22.6@2023/05/24 13:30:12.836), PointValueTime(4376.54@2023/05/24 13:35:12.836), PointValueTime(459.62@2023/05/24 13:40:12.836), PointValueTime(22.8@2023/05/24 13:45:12.836), PointValueTime(22.886666666666667@2023/05/24 13:50:12.836)] time = 1684906212836 , point= PointValueTime(22.6@2023/05/24 13:30:12.836) time = 1684906512836 , point= PointValueTime(4376.54@2023/05/24 13:35:12.836) time = 1684906812836 , point= PointValueTime(459.62@2023/05/24 13:40:12.836) time = 1684907112836 , point= PointValueTime(22.8@2023/05/24 13:45:12.836) time = 1684907412836 , point= PointValueTime(22.886666666666667@2023/05/24 13:50:12.836)

Hi @CraigWeb , actually I was trying to install a new Mango 5 instance. Everything is totally new. These are what I did: 1/ Install MySQL 8.0, create a database (scheme) named mango 2/ Install Mango 5 and paste a mango.properties file with MySQL info as above mentioned in mango_data folder. 3/ Start mango service and change admin password. 4/ Create a data source with some data point. 5/ Backup with Backup feature in System Setting -> SQL backup 6/ Delete data source and restore with System Setting -> SQL backup. 7/ See that orange warning pop up, but the deleted data source and data point is back, but I'm not sure if it normal or not.

@CraigWeb Heya Craig. Thanks for that! That's exactly what I was thinking. It's absolutely great now that Mango runs under its own user, but that user can't be logged into (at least, at least not without a fair amount of headache). Once CertBot is deployed, Mango will (likely) have no trouble updating them, but on the first run, almost everyone using those scripts will be logging in or SUDOing into root or whatever to make that happen. The easiest solution (I think) is to juts do something like: export mango_paths_data=/opt/mango-data export mango_paths_home=/opt/mango Or something when you sudo in to do these scripts. or you have to enable the mango user account to be loggable-innable, but that's the whole point (I think) of creating a mango-user in the first place, to not have it be a login account.. Which is sound design practice. I'm probably going to try that over the weekend again- Thanks so much for looking through those scripts. When I first was trying this, I thought I was out of my mind, but it turns out there's both an easy solution (at least temporarily) to make this work, and no problem when the certbot hook runs (since it's already running as the mango user). This problem only popped up because the new mango install script does everything under a user it creates, and the interactive config stuff happens because users are logging in and modifying another users's (mangos) settings. It all makes pretty solid sense, but only once you sit down and think through it. Who knew environment variables would continue to be such a headache?

@cbyrne Ye, I hear what you saying but the component was designed to enable highly accurate filters and we can't lose that. it's needed in the bulk editor and other pages. Maybe adding 2 different filter modes would be helpful to use in general dashboards.

@CraigWeb We just tried to make this change and I noticed a couple of things. There is no option for setting intervalLoggingType once you've set loggingType to "Interval and when point value changes" via the GUI. We ended up just changing the JSON and pushing that out, which it seems to have taken the changes. Also interesting, when hitting the API endpoint for data point details...if the point is configured as ON_CHANGE_INTERVAL it does not return a key for "intervalLoggingType" nor is any value for any keys set to "AVERAGE" but I certainly do see those for points configured as "INTERVAL" I honestly always assumed the way ON_CHANGE_INTERVAL worked was it logs on changes and the current value once per minute, I had no idea this would be averaging over that minute and then recording the average. Anyway...I'll let you know the results, just wanted to give that info.

@MattFox said in Java problem may crash my instance: @tungthanh500 stick to adopt11, it's fast and works Fox Thank you for your advice. How are you doing? @terrypacker said in Java problem may crash my instance: I have seen situations where our monitoring library can't handle the hardware it is running on. You can disable this using the mango property: # enables getting operating system, process, and hardware information via the OSHI native library internal.monitor.enableOperatingSystemInfo=true Thank you, I will try to add that.

@CraigWeb That's a good re-assurance I'm on the right train of though. It would be neat if there was a data point that could capture sunrise and sunset for a given location. Changes in those values would trigger a context change and update the statistical point. Sunrise and Sunset values would be great if they could be used in the advanced scheduler, too, as one could save energy by using those values to trigger events like setpoints and the like. I was hoping to use the envcands Environment Canada module to capture weather data and perhaps sunrise/sunset, but I never managed to make it work. There's a distinct lack of documentation on that module. If there is documentation, that would be extremely useful.

@rob987 Hi, have you find solution for you JSON timestamp?

@kyle-Hughes its kind of hard for me to follow your configuration and identify what the actual problem is. Maybe you could do a diagram on how each Mango assets links together ?

@cbyrne I'd build an overridden mangoUI with development mode enabled, then you can do whatever you want, could likely also do a hack with the userModule, but the overriding would be giving you more freedom Fox