jca001

Based on the label on the module, it supports Z-Wave and Zigbee. Your suggested name has Matter in it. I suggest Z-MatterZ

I will do that if it happens again. I have already clicked on START and it is running for now. I my other topic I stated I now have ISY Programs that will send me an email when the status indicated disconnected so I will know when it stops sooner.

I had not checked the values of OpenWeatherMap or looked at the NS for a couple of days. It has stopped again but there is no trace back. Here are the last lines in the log file. OpenWeatherMap_log.txt

The next time it shows disconnected I will send you the log file.

It has stopped at different time. The day before it was around 06:?? and then at about 20:30. Nothing specific happened on my network that I am aware of and my cable modem, router, switch and RPI are all on an UPS. I know it would take more coding, but maybe it would be good if there was an option to change the precision to what the user wanted to see. I just think it is bad to cause the ISY to trigger a program each time a value changes by 100th or even 10th when the test may be for a whole value. Maybe I am wrong about this but I am pretty sure I had a test program that just incremented a counter when the temperature was above say 80 F and it counted a lot probably each time it changed to 80.1, 80.2, 80.3 and then back to 80.2, etc. This is just my opinion, but other may have different ones.

I know I have already replied to this, but I was looking at my RPI Node Server and noticed for the last 2 days OpenWeatherMap has showed offline. I just click on start and it is OK. I don't see an error, it just seems to stop. I can provide the log file if you want to look at it. Looking at the values on the AC it has temperatures and wind speed with NNN.NN, which is what I was talking about in general. I think they should be whole numbers. I cannot really see somebody want to trigger a program if the temperature was say above 88.6 F. Maybe 1-digit fraction precision is needed for "C".

No. I was just making a general statement about any thing that has a temperature values, weather or thermostats. Some others that I think should have less precision, no fraction are MPH and humidity.

I think not sending values unless they change is a good thing in general. But values should be sent every so often even if they do not change in case ISY is rebooted so the values will get updated after some amount of time. Maybe every 5 or 10 minutes or a configurable parameter. While I am making suggestions I don't think temperatures should be NNN.NN. I think they should be NNN.N. Who needs to know if the temperature changed by 100th of a degree? This can cause programs to trigger every time the value is updated because it changes between say 81.11 and 81.12.