johnnyt

how do I go back? I lost all my airthings nodes in ISY and my programs are all have Node Status [null entry] Then Wait 2 seconds $sAQ.CO2.MasterBedroom.Value = Node Status [null entry] $sAQ.CO2.MiddleBedroom.Value = Node Status [null entry] $sAQ.CO2.NWBedroom.Value = Node Status [null entry] $sAQ.CO2.SWBedroom.Value = Node Status [null entry] $sAQ.CO2.MainFloor.Value = Node Status [null entry] $sAQ.CO2.RecRoom.Value = Node Status [null entry] Wait 1 second $sAQ.VOC.MainFloor.Value = Node Status [null entry] $sAQ.VOC.MasterBedroom.Value = Node Status [null entry] $sAQ.VOC.MiddleBedroom.Value = Node Status [null entry] $sAQ.VOC.NWBedroom.Value = Node Status [null entry] $sAQ.VOC.SWBedroom.Value = Node Status [null entry] $sAQ.VOC.RecRoom.Value = Node Status [null entry] Wait 1 second $sTemp.MasterBedroom.Airthings = Node Status [null entry] $sTemp.MasterBedroom.Airthings *= 100 $sTemp.MiddleBedroom.Airthings = Node Status [null entry] $sTemp.MiddleBedroom.Airthings *= 100 $sTemp.NWBedroom.Airthings = Node Status [null entry] $sTemp.NWBedroom.Airthings *= 100 $sTemp.MainFloor.Airthings = Node Status [null entry] $sTemp.MainFloor.Airthings *= 100 $sTemp.RecRoom.Airthings = Node Status [null entry] $sTemp.RecRoom.Airthings *= 100 $sTemp.SWBedroom.Airthings = Node Status [null entry] $sTemp.SWBedroom.Airthings *= 100 Wait 1 second $sHum.MainFloor.Airthings = Node Status [null entry] $sHum.MasterBedroom.Airthings = Node Status [null entry] $sHum.MiddleBedroom.Airthings = Node Status [null entry] $sHum.NWBedroom.Airthings = Node Status [null entry] $sHum.RecRoom.Airthings = Node Status [null entry] $sHum.SWBedroom.Airthings = Node Status [null entry] Wait 1 second $iAQ.Pressure.MainFloor = Node Status [null entry] $iAQ.Pressure.MasterBedroom = Node Status [null entry] $iAQ.Pressure.MiddleBedroom = Node Status [null entry] $iAQ.Pressure.NWBedroom = Node Status [null entry] $iAQ.Pressure.SWBedroom = Node Status [null entry] $iAQ.Pressure.RecRoom = Node Status [null entry] Wait 1 second $sAQ.Radon.MainFloor = Node Status [null entry] $sAQ.Radon.MasterBedrm = Node Status [null entry] $sAQ.Radon.MiddleBedroom = Node Status [null entry] $sAQ.Radon.NWBedroom = Node Status [null entry] $sAQ.Radon.RecRoom = Node Status [null entry] $sAQ.Radon.SWBedroom = Node Status [null entry] $sAQ.Radon.UtilityRoom = Node Status [null entry] Wait 1 second $sAQ.HRV.Hum = Node Status [null entry] $sAQ.HRV.Radon = Node Status [null entry] $sAQ.HRV.Temp = Node Status [null entry] $sAQ.HRV.VOC = Node Status [null entry] Wait 1 second Send Notification to 'jean' content 'IAQ - Raw Data - HRV' Run Program 'Calc AQ Averages and add Weather data' (Then Path) Else - No Actions - (To add one, press 'Action')

@Jimbo.Automates Am getting errors after uninstalling and reinstalling to get v1.0.0, per this workaround: 2022-12-12 21:03:19,507 Thread-19 udi_interface DEBUG Controller:add_node: Adding: Guest Bedroom 2022-12-12 21:03:19,508 Thread-19 udi_interface ERROR udi_interface:write: Exception in thread will PM log to you

Bought a new SD card that's 32GB and, when I double checked the instructions on how to replace it, it says "ISY supports up to a 16GB SD card". See https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing/Formatting_an_SD_Card It's a bit old so thinking it's outdated, and I wasn't able to find anything smaller than 32GB. Is it just a case that it won't format/use more than 16GB (no big deal), or will using a bigger SD card actually fail?

Thanks for the update! Did a restart of the Node Server after seeing message that a restart was needed but it still says v 0.0.6. This is *after* PG3 upgrade to 3.1.16, which I think was supposed to fix this issue with another NS:

very interesting. thanks for posting, @IndyMike. It's UDI support that brought the -10 errors and what they mean to my attention when looking into something else. Even the ebay guy that refurbished 3 of the 4 PLMs I have is a little surprised that all three of my refurbished PLMs are seeing "so many problems". The reality is that I'm not noticing any problems in real life. There may be a bad/missed command at the time of the -10 that recovers thanks to retries? Overall, though, my insteon is working as well as it has been in general. While I don't understand why devices (mostly KPLs) end up with bad links over time, hey, I've been living with it for more than a decade now so that's Situation Normal AFU. So what is this problem really? is it it a 994i issue, will any repair one can do today fix it? Also, does the PLM/ISY recover from it, meaning they are really just warnings, if that? Also, if it is a warning sign of a degraded unrepairable PLM, could it still function for another year or two? Looks like it has worked fine for you for 3 years! Maybe just having 4 spares with good capacitors will allow me to continue using Insteon until I can move off it (which is the plan, but I did want to drive my multi thousand dollar insteon device investment into the ground)

oh yes. before I posted here. The answer I got that way was basically the second post above.

Thanks! Interesting other post, especially about the repair service in Toronto area (more than just PLM too) as I'm in Canada. Missing info on what one gets for how much, and history/depth of feedback compared with NY-based ebay service I've used but will keep close eye on that. RE: 994i serial port. Interestingly I replaced the 994i I was using just last weekend with an older one to fix unrelated issues but I still see -10 errors with this other one. Would be even more rare to see that problem with two separate units.

A couple days ago, on your suggestion, I replaced the cable to the PLM with a brand new cable that I first tested using my managed switch 'cable test' function. While the old cable also tested okay, I was nonetheless hopeful about the new cable because I took the opportunity to check/restore all my keypadlincs (about 8 of them), which almost all had some bad links (common after a while or when replacing PLM, which I did 3 days ago). I figured that was a good stress test and no errors were reported. But, alas, last night I got hit with a couple -10 errors during query all, which is when majority of them occur. I think I'll send one back to refurbisher see if the comms repair was the issue I should have sent them in for in the first place...

I went through error logs going back to before I got the PLMs refurbished. In about a month of testing 4 PLMs prior to refurbishing 3 of them, I saw about 23 "-10" errors in about 3 1/2 weeks. After the refurbishing, the first refurbished one I tested (a v 1.7) simply would not hear anything anymore. While it may have had some -10 errors, it was hearing insteon events before I refurbished it. I expect I will sent it back but waiting to see what else I might need to send in again. The second one I tested (v 2.6) has now been in production for at least 6 weeks and I found 29 "-10" errors in that time, so about 4.8 errors per week. That's more than I thought was happening. It seemed less frequent when I was spot checking things. I've replaced it (today) to see if the third one I had refurbished (a v1.C) does any better. I do see the ebay PLM fixer has a "Communication Repair" service that I did not think was my situation since things were working in general (I actually really notice anything not working). Before I go potentially throw out good money after bad, would the -10 errors fall into this category? (The first part was done as part of the refurbishing so the part after "Also" is the key stuff I didn't get done.)

wouldn't refurbishing them fix this?

I occasionally get -10 errors in ISY error log. I was told it indicates a defective PLM. The official error code description is "-10 UNEXPECTED DEVICE RESPONSE". It has occurred intermittently with 4 different PLMs of different vintages that I've gone through with no noticeable issues. It's possible I just missed the issues when they happened but the point is that overall my different PLMs have been working. Furthermore I've had 3 of the four PLMs refurbished to upgrade the capacitors and other components designed to make them last longer by this ebay service with positive feedback and it didn't eliminate the errors. The guy who did the refurbishing didn't really know what this ISY error meant. He was familiar with ISY but not a user of it himself. Does anyone know what they mean in practice? Why wouldn't upgrading capacitors and other pieces not fix them? Any info would be appreciated.

same here. No rain expected for another couple days so can't say if the issue is fixed but I assume it is.

PG3 is reporting an error updating WeatherFlow NS RAINRT value 11/30/2022, 08:34:05 [pg3] error: ISY Response: [Try: 1] [00:21:b9:02:55:cd] :: [404 - OK] :: 352.140541ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_207296/report/status/RAINRT/0.07758000000000001/46 11/30/2022, 08:41:05 [pg3] error: ISY Response: [Try: 1] [00:21:b9:02:55:cd] :: [404 - OK] :: 357.517191ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_207296/report/status/RAINRT/0.8210999999999999/46 11/30/2022, 08:43:03 [pg3] error: ISY Response: [Try: 1] [00:21:b9:02:55:cd] :: [404 - OK] :: 356.864566ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_207296/report/status/RAINRT/0.43776000000000004/46 This seems similar to a previous post I made that I can't find right now where I think the NS was receiving a number in a format it couldn't handle (number of decimals, I think). Strange that I didn't see this particular one when I saw the other ones. I guess I just haven't looked my logs when it was raining... Here's what the NS shows right now - seems to only accept 5 decimal places when it's getting lots more How come there isn't an error entry in NS log, only in PG3 log? here's the 08:43:03 entry in NS log: 2022-11-30 08:43:03,802 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: RAINRT to 0.43776000000000004 UOM 46 Is the PG3 error an error?

I restarted what is a 2nd instance of the this NS (with separate API as first instance) after several weeks of not using it. One of the airthings device that was fine before, was labeled as "undefined" instead of the name I gave it in Airthings. The data seems to be coming through to ISY okay and I was able to rename it on ISY side but it's stuck as 'undefined' in NS. I tried deleting it on ISY side to see if the process of re-adding it would clean things up. It appeared to go through a process that I thought would have re-added it but without doing so. It then sent data to the node even though it no longer exists on ISY 2022-11-28 09:01:52,847 Thread-339 udi_interface INFO Controller:shortPoll: enter 2022-11-28 09:01:52,849 Thread-339 udi_interface INFO Controller:_query_all: enter 2022-11-28 09:01:52,849 Thread-339 udi_interface INFO Sensor:shortPoll: enter 2022-11-28 09:01:52,850 Thread-339 udi_interface INFO Sensor:query: enter 2022-11-28 09:01:53,806 Thread-339 udi_interface INFO Sensor:query: exit 2022-11-28 09:01:53,807 Thread-339 udi_interface INFO Sensor:shortPoll: exit 2022-11-28 09:01:53,808 Thread-339 udi_interface INFO Sensor:shortPoll: enter 2022-11-28 09:01:53,809 Thread-339 udi_interface INFO Sensor:query: enter 2022-11-28 09:01:54,168 Thread-339 udi_interface INFO Sensor:query: exit 2022-11-28 09:01:54,169 Thread-339 udi_interface INFO Sensor:shortPoll: exit 2022-11-28 09:01:54,170 Thread-339 udi_interface INFO Sensor:shortPoll: enter 2022-11-28 09:01:54,171 Thread-339 udi_interface INFO Sensor:query: enter 2022-11-28 09:01:54,449 Thread-339 udi_interface INFO Sensor:query: exit 2022-11-28 09:01:54,450 Thread-339 udi_interface INFO Sensor:shortPoll: exit 2022-11-28 09:01:54,451 Thread-339 udi_interface INFO Sensor:shortPoll: enter 2022-11-28 09:01:54,452 Thread-339 udi_interface INFO Sensor:query: enter 2022-11-28 09:01:54,789 Thread-339 udi_interface INFO Sensor:query: exit 2022-11-28 09:01:54,790 Thread-339 udi_interface INFO Sensor:shortPoll: exit 2022-11-28 09:01:54,791 Thread-339 udi_interface INFO Sensor:shortPoll: enter 2022-11-28 09:01:54,792 Thread-339 udi_interface INFO Sensor:query: enter 2022-11-28 09:01:55,217 Thread-339 udi_interface INFO Sensor:query: exit 2022-11-28 09:01:55,219 Thread-339 udi_interface INFO Sensor:shortPoll: exit 2022-11-28 09:01:55,219 Thread-339 udi_interface INFO Controller:_query_all: exit 2022-11-28 09:01:55,220 Thread-339 udi_interface INFO Controller:shortPoll: exit 2022-11-28 09:02:01,537 MQTT udi_interface.interface INFO interface:_message: Successfully set s_2930133779 :: CO2LVL to 501.0 UOM 54 2022-11-28 09:02:01,578 MQTT udi_interface.interface INFO interface:_message: Successfully set s_2930133779 :: BARPRES to 998.4 UOM 56 2022-11-28 09:02:01,580 MQTT udi_interface.interface INFO interface:_message: Successfully set s_2930133779 :: GV3 to -37 UOM 56 2022-11-28 09:02:01,582 MQTT udi_interface.interface INFO interface:_message: Successfully set s_2930133779 :: CLITEMP to 22.7 UOM 4 2022-11-28 09:02:01,584 MQTT udi_interface.interface INFO interface:_message: Successfully set s_2930133779 :: GV2 to 1669644043 UOM 56 2022-11-28 09:02:01,620 MQTT udi_interface.interface INFO interface:_message: Successfully set s_2930133779 :: GV4 to 125.0 UOM 56 I restarted the NS and that resulted in recreation of the device in ISY as "undefined" Seems like a bug that the NS isn't using the device name that I gave it in Airthings in first place, and then isn't self correcting, though maybe the latter is more of a feature than a bug assuming this doesn't stem from an Airthings device defect - is there a way to tell? It looks fine on my Airthings Dashboard: I haven't tried unpairing device from hub then re-pairing it. I may do that later as another potential workaround. For now I've just renamed it in ISY

It's come to my attention that the WeatherFlow NS log does not report errors that are reported in PG3 log. Below are two examples from this morning (using latest 3.0.25 version of NS, with log level set to "Info"): Example 1: PG3 Log entries 11/23/2022, 10:15:04 [pg3] warn: ISY Response: [Try: 1] [00:21:b9:02:55:cd] :: [ECONNABORTED] :: 5036.919286ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_207296/report/status/GV4/1.94/32 11/23/2022, 10:15:04 [pg3] warn: ISY Response: [Try: 1] [00:21:b9:02:55:cd] :: [ECONNABORTED] :: 5015.150309ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_207296/report/status/GUST/1.94/32 WeatherFlow log entries: 2022-11-23 10:14:56,819 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: DEWPT to -2.5 UOM 4 2022-11-23 10:14:57,567 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: GV0 to -1.4 UOM 4 2022-11-23 10:14:57,610 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: ATMPRES to 1023.223 UOM 118 2022-11-23 10:14:58,738 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: CLIHUM to 75.7 UOM 22 2022-11-23 10:14:58,741 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: BARPRES to 1013.24 UOM 118 2022-11-23 10:14:59,447 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: SPEED to 1.94 UOM 32 2022-11-23 10:14:59,490 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: BATLVL to 2.371 UOM 72 PG3 error occurs here for next two updates but Weatherflow log gives appearance of successful update 2022-11-23 10:15:08,898 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: GV4 to 1.94 UOM 32 2022-11-23 10:15:08,940 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: GUST to 1.94 UOM 32 2022-11-23 10:15:09,278 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: LUMIN to 15778 UOM 36 2022-11-23 10:15:10,019 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: SOLRAD to 131 UOM 74 2022-11-23 10:15:10,061 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: UV to 1.29 UOM 71 2022-11-23 10:15:10,764 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: GV3 to 297 UOM 76 2022-11-23 10:15:10,807 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: WINDDIR to 297 UOM 76 2022-11-23 10:15:25,789 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: GV4 to 7 UOM 57 Example 2: PG3 log entries: 11/23/2022, 10:25:03 [pg3] warn: ISY Response: [Try: 1] [00:21:b9:02:55:cd] :: [ECONNABORTED] :: 5036.783711ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_207296/report/status/UV/0.54/71 11/23/2022, 10:25:03 [pg3] warn: ISY Response: [Try: 1] [00:21:b9:02:55:cd] :: [ECONNABORTED] :: 5015.511116ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_207296/report/status/SOLRAD/61/74 WeatherFlow log entries: 2022-11-23 10:24:56,556 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: CLIHUM to 75.05 UOM 22 2022-11-23 10:24:57,663 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: GV4 to 0.0 UOM 32 2022-11-23 10:24:57,705 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: SPEED to 0.0 UOM 32 2022-11-23 10:24:58,398 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: LUMIN to 7227 UOM 36 2022-11-23 10:24:58,440 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: GUST to 0.0 UOM 32 PG3 error occurs here for next two updates but Weatherflow log gives appearance of successful update 2022-11-23 10:25:07,861 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: UV to 0.54 UOM 71 2022-11-23 10:25:07,901 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: SOLRAD to 61 UOM 74 2022-11-23 10:25:08,242 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: WINDDIR to 0 UOM 76 2022-11-23 10:25:08,613 MQTT udi_interface.interface INFO interface:_message: Successfully set 207296 :: GV3 to 0 UOM 76 2022-11-23 10:25:25,578 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: GV4 to 7 UOM 57

I'm confused by this: First, to be clear, I only have one instance of this NS actually running/connected but I do have two installations of it: one for ISY and one for IoP. Not only did I think this was okay because of this prior message: But also because I did have three node servers running fine for both ISY and IoP as same time, namely Airthings, WeatherFlow, and this one as long as I put them in the same slot (which they are now, but the slot issue was a problem with this NS and us what started this thread) I'm now on PG3 3.1.14 and wasn't at that point when I reported this so probably the PG3 bug is no longer an issue if that's what was the issue. Since I now know how to avoid the problem, I'll leave it to you and @simplextech to determine if there are any fixes needed (to whatever) to avoid problems in future. I'm not going to be using this NS much once I move to IoP (just waiting for new dongle and zwave migration capability). I'm only using it periodically (I start then stop it) to check the number of programs I have on ISY because I'm close to the maximum allowed.

Any idea why the same three nodes or subnodes (not sure what they're called), namely SPEED, GV4, and GUST, are always involved in 404 errors? It's not like those calls don't succeed sometimes - I do see the values change in ISY. It's also not like there are no other nodes that get a 404. it's just that when there are 404's these three nodes are always involved from what I've seen. 11/18/2022, 02:55:13 [pg3] error: No code in error response 11/18/2022, 02:55:13 [pg3] error: ISY Response: [Try: 1] [00:21:b9:02:55:cd] :: [404 - OK] :: 348.399805ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_207296/report/status/SPEED/0.5760000000000001/32 11/18/2022, 02:55:13 [pg3] error: No code in error response 11/18/2022, 02:55:13 [pg3] error: ISY Response: [Try: 1] [00:21:b9:02:55:cd] :: [404 - OK] :: 68.046758ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_207296/report/status/GV4/0.5760000000000001/32 11/18/2022, 02:55:13 [pg3] error: No code in error response 11/18/2022, 02:55:13 [pg3] error: ISY Response: [Try: 1] [00:21:b9:02:55:cd] :: [404 - OK] :: 22.453674ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_207296/report/status/GUST/0.5760000000000001/32 11/18/2022, 02:56:03 [pg3] error: No code in error response 11/18/2022, 02:56:03 [pg3] error: ISY Response: [Try: 1] [00:21:b9:02:55:cd] :: [404 - OK] :: 36.875933ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_207296/report/status/SPEED/0.14400000000000002/32 11/18/2022, 02:56:03 [pg3] error: No code in error response 11/18/2022, 02:56:03 [pg3] error: ISY Response: [Try: 1] [00:21:b9:02:55:cd] :: [404 - OK] :: 16.920775ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_207296/report/status/GUST/0.14400000000000002/32 11/18/2022, 02:56:03 [pg3] error: No code in error response 11/18/2022, 02:56:03 [pg3] error: ISY Response: [Try: 1] [00:21:b9:02:55:cd] :: [404 - OK] :: 56.705772ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_207296/report/status/GV4/0.14400000000000002/32 11/18/2022, 02:57:02 [pg3] error: No code in error response 11/18/2022, 02:57:02 [pg3] error: ISY Response: [Try: 1] [00:21:b9:02:55:cd] :: [404 - OK] :: 33.619906ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_207296/report/status/SPEED/0.036000000000000004/32 11/18/2022, 02:57:02 [pg3] error: No code in error response 11/18/2022, 02:57:02 [pg3] error: ISY Response: [Try: 1] [00:21:b9:02:55:cd] :: [404 - OK] :: 17.546125ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_207296/report/status/GUST/0.036000000000000004/32 11/18/2022, 02:57:02 [pg3] error: No code in error response 11/18/2022, 02:57:02 [pg3] error: ISY Response: [Try: 1] [00:21:b9:02:55:cd] :: [404 - OK] :: 57.084195ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_207296/report/status/GV4/0.036000000000000004/32 Also, am really struggling to understanding why I get these errors when response times are fine. I get your point that an overloaded (or defective) ISY is bound to cause problems but these problems are happening without an obvious overload. Attached is PG3 log for today (up to now). As you'll see this NS (#6) results in the most errors. While for sure it is the one that gets the most activity and therefore opportunity for errors, my Airthings NS (#8) updates every 5 minutes, Envisalink-DSC every 6.5 mins or so, and OpenWeatherMap every 10 mins or so. There are a few but not that many Airthings errors and I didn't see any errors from the other ones. pg3-Nov18.log

Thanks for info on different meaning for controller variables/sub nodes (not sure what you call those) Note that Server Status asks for a number when used in a program, not true/false. I assume '0' means false and anything else means true but would be better if it said true/false (or adjust documentation)

@bpwwer, is this something on your radar? Do you need any more info from me?

Thanks. I did notice there were some airthings cloud issues yesterday. After this is fixed and the cloud returns 403, am I right to think it will change the NoderServer Status to "Unconnected" in ISY? And/or would it change the Server Status? I'm a bit confused about the difference and what events change them. Sometimes they are blank for me for a while - I think after an ISY restart. Also do you have timeline for when you will provide a new version? It looks like there are 9 open issues going back to July, most of which do affect my setup. Not critical, of course, although this latest one, while hopefully a rare event, did result in the NS crashing without any notification, i.e. my program notifying me when NS Status is "unconnected" did not trigger. Thanks again. I really like the ability to get my Airthings data into ISY.

I recently upgraded to PG3.1.14 and, today, after noticing a value in ISY was not getting updated, I check NS logs and it had stopped working at 02:03AM after a number of occurrences of errors I haven't seen before. 2022-11-17 01:48:36,971 Thread-693 udi_interface ERROR udi_interface:write: Exception in thread 2022-11-17 01:48:36,973 Thread-693 udi_interface ERROR udi_interface:write: Thread-693 2022-11-17 01:48:36,973 Thread-693 udi_interface ERROR udi_interface:write: : 2022-11-17 01:48:36,974 Thread-693 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-11-17 01:48:36,975 Thread-693 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner 2022-11-17 01:48:36,979 Thread-693 udi_interface ERROR udi_interface:write: self.run() 2022-11-17 01:48:36,980 Thread-693 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 917, in run 2022-11-17 01:48:36,983 Thread-693 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2022-11-17 01:48:36,984 Thread-693 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/<my ISY ID>_8/nodes/Controller.py", line 149, in handler_poll 2022-11-17 01:48:36,986 Thread-693 udi_interface ERROR udi_interface:write: self.shortPoll() 2022-11-17 01:48:36,987 Thread-693 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/<my ISY ID>_8/nodes/Controller.py", line 153, in shortPoll 2022-11-17 01:48:36,988 Thread-693 udi_interface ERROR udi_interface:write: self._query_all() 2022-11-17 01:48:36,989 Thread-693 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/<my ISY ID>_8/nodes/Controller.py", line 183, in _query_all 2022-11-17 01:48:36,990 Thread-693 udi_interface ERROR udi_interface:write: node.shortPoll() 2022-11-17 01:48:36,991 Thread-693 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/<my ISY ID>_8/nodes/Sensor.py", line 104, in shortPoll 2022-11-17 01:48:36,993 Thread-693 udi_interface ERROR udi_interface:write: self.query(force=False,authorize=False) 2022-11-17 01:48:36,993 Thread-693 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/<my ISY ID>_8/nodes/Sensor.py", line 113, in query 2022-11-17 01:48:36,995 Thread-693 udi_interface ERROR udi_interface:write: st = self.controller.api_get(f"devices/{self.serial}/latest-samples") 2022-11-17 01:48:36,996 Thread-693 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/<my ISY ID>_8/nodes/Controller.py", line 202, in api_get 2022-11-17 01:48:36,997 Thread-693 udi_interface ERROR udi_interface:write: res = self.session.get( 2022-11-17 01:48:36,998 Thread-693 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/<my ISY ID>_8/pgSession.py", line 65, in get 2022-11-17 01:48:37,000 Thread-693 udi_interface ERROR udi_interface:write: return(self.response(response,'get')) 2022-11-17 01:48:37,000 Thread-693 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/<my ISY ID>_8/pgSession.py", line 88, in response 2022-11-17 01:48:37,002 Thread-693 udi_interface ERROR udi_interface:write: self.logger.error("Forbidden: %s: text: %s" % (response.url,json_data['message']) ) 2022-11-17 01:48:37,002 Thread-693 udi_interface ERROR udi_interface:write: KeyError 2022-11-17 01:48:37,003 Thread-693 udi_interface ERROR udi_interface:write: : 2022-11-17 01:48:37,004 Thread-693 udi_interface ERROR udi_interface:write: 'message' The node value that I noticed not getting updated was GV4 for device s_2930027997. There may be others too - I didn't go fishing for others. A restart of the NS seems to have fixed things for now. Attached is log for today, including entries after the restart. If needed I could SSH into Polisy to pull out older log files. Let me know if that would help at all. Thanks.

So I'm working with UDI support on possibility of ISY or Polisy network interface issue. As part of fathering more data I restarted the WeatherFlow NS with PG3 log level at debug and I'm seeing things that to me suggest issues that may not be related to network, including unhandled errors, "REPORT THIS" messages, and a ton of these: 11/16/2022, 09:33:53 [pg3] debug: 207296 is LOCKED by addnode(), waiting... I would also mention that it's not like I don't ever see normal response times from ISY. There are plenty of responses that are well below 100ms when I'm not restarting a NS or PG3. I've attached a chunk of logs from yesterday when ISY was obviously not busy to show this. I guess I'm wondering if every error is really a network problem or is there are other things going on that would continue to happen even if I got all new hardware? Or is there anything in the debug logs that would help UDI troubleshoot the problem? I've already sent a bunch of stuff and don't want to send more at this point unless it would be helpful. Thanks. PG3Debug-WeatherFlowNSrestart.zip

Ok, I've reported this to UDI. So the messages are for this NS and I see the nodes that are reported as not there in ISY so it's strange. How do I force a reload of the nodes? Restarting NS doesn't do it. I also tried "Load Profile" but it just sits there "clicked" and does nothing. see screenshot.

So I moved the 994i and Polisy off the unmanaged switch I was using and connected them directly to my main managed switch. I then ran a cable test and it returned "normal" (ports 11 and 12 below). Port 9 shown is connection to unmanaged switch so cables being used aren't the problem. I also don't see any Tx / Rx errors on those ports on the switch monitoring page. Finally, I did some packet capturing at router of 994i and Polisy routing calls and traffic to/from my PC to them and there were no errors reported. I'm still, however, getting roughly the same errors in PG3 when I stop/start WeatherFlow NS after the switch changes. So I think I'm now trying to figure out whether 994i or Polisy NIC might be struggling/failing. Is there a tool I can use at Polisy OS level to test the Polisy NIC to see if it's failing? I don't believe there's anything I can run on 994i, but if you know of something, please let me know. Also, I'm wondering if the following message is an error or "OK". Normally http 404 code is an error but this entry also says "OK" so I'm confused. 11/15/2022, 13:24:49 [pg3] error: ISY Response: [Try: 1] [myISYid] :: [404 - OK] :: 32.008351ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_207296/report/status/SPEED/2.7720000000000002/32

I'll play with network path to see if there's an issue with switches connecting 994i and Polisy to router (both are on same switch now). I should mentioned that I often get sub-100ms responses so it's not clear to me I'm having a general network issue. In the meantime if you don't know what ECONNABORTED who would? Cause I get those all the time. Also I just upgraded PG3 from 3.1.12 to 3.1.14, which required a PG3 restart. Below is a chunk of the PG3 logs I got at startup. There are a number of unhandled errors, a couple "REPORT THIS" messages, several driver errors, and, of course the pretty normal "ECCONNABORTED" messages. Other than the unhandled errors, would the other errors be due to network problems or failing ISY, or could there be something else going on? If changing switches doesn't fix the problem I will reach out to UDI support but want to be sure I've ruled other possibilities out. Node 6 is WeatherFlow NS and node 8 is Airthings NS. Attached is screenshot of the PG3 Dashboard for my 994i 11/15/2022, 09:43:57 [pg3] error: Error: GET http://192.168.200.251:80/rest/nodes Failed :: ECONNABORTED 11/15/2022, 09:43:57 [pg3] error: [<my ISY ID>_6] checkDrivers failed :: TypeError: Cannot read properties of undefined (reading 'data') at Object.checkDrivers (/var/polyglot/node_modules/@universaldevices/pg3/lib/modules/Node server/status.js:269:64) at async /var/polyglot/node_modules/@universaldevices/pg3/lib/modules/Node server/command.js:144:13 at async Promise.all (index 0) 11/15/2022, 09:43:57 [pg3] info: [<my ISY ID>_6] adding node forecast_8 to ISY 11/15/2022, 09:44:02 [pg3] warn: ISY Response: [Try: 1] [<my ISY ID>] :: [ECONNABORTED] :: 5020.398338ms - http://192.168.200.251:80/rest/ns/8/nodes/n008_controller/report/status/GV2/1/56 11/15/2022, 09:44:07 [pg3] warn: ISY Response: [Try: 1] [<my ISY ID>] :: [ECONNABORTED] :: 10003.68036ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_forecast_8/add/forecast?primary=n006_controller&name=Forecast%208 11/15/2022, 09:44:10 [pg3] error: No code in error response 11/15/2022, 09:44:10 [pg3] warn: ISY Response: [Try: 2] [<my ISY ID>] :: [400 - OK] :: 2459.073208ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_forecast_8/add/forecast?primary=n006_controller&name=Forecast%208 11/15/2022, 09:44:10 [pg3] error: No code in error response 11/15/2022, 09:44:10 [pg3] warn: ISY Response: [Try: 3] [<my ISY ID>] :: [400 - OK] :: 42.763673ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_forecast_8/add/forecast?primary=n006_controller&name=Forecast%208 11/15/2022, 09:44:10 [pg3] error: No code in error response 11/15/2022, 09:44:10 [pg3] error: ISY Response: [MAX TRIES EXCEEDED] [<my ISY ID>] :: [400 - OK] :: 434.252744ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_forecast_8/add/forecast?primary=n006_controller&name=Forecast%208 11/15/2022, 09:44:10 [pg3] error: Error: GET http://192.168.200.251:80/rest/ns/6/nodes/n006_forecast_8/add/forecast?primary=n006_controller&name=Forecast%208 Failed :: 400 - OK 11/15/2022, 09:44:10 [pg3] info: [<my ISY ID>_6] addnode sucessfully added node forecast_8 11/15/2022, 09:44:10 [pg3] error: unhandledRejection REPORT THIS!: [object Promise], reason: TypeError: Cannot read properties of undefined (reading 'status') 11/15/2022, 09:44:10 [pg3] warn: node forecast_0 on profile 6 already exists, no nodeDef or driver changes detected 11/15/2022, 09:44:11 [pg3] warn: node forecast_1 on profile 6 already exists, no nodeDef or driver changes detected 11/15/2022, 09:44:11 [pg3] warn: node forecast_2 on profile 6 already exists, no nodeDef or driver changes detected 11/15/2022, 09:44:11 [pg3] warn: node forecast_3 on profile 6 already exists, no nodeDef or driver changes detected 11/15/2022, 09:44:11 [pg3] warn: node forecast_4 on profile 6 already exists, no nodeDef or driver changes detected 11/15/2022, 09:44:11 [pg3] warn: node forecast_6 on profile 6 already exists, no nodeDef or driver changes detected 11/15/2022, 09:44:11 [pg3] warn: node forecast_5 on profile 6 already exists, no nodeDef or driver changes detected 11/15/2022, 09:44:11 [pg3] warn: node forecast_7 on profile 6 already exists, no nodeDef or driver changes detected 11/15/2022, 09:44:11 [pg3] warn: node forecast_9 on profile 6 already exists, no nodeDef or driver changes detected 11/15/2022, 09:44:11 [pg3] warn: node s_2930037297 on profile 8 already exists, no nodeDef or driver changes detected 11/15/2022, 09:44:11 [pg3] warn: node s_2930027997 on profile 8 already exists, no nodeDef or driver changes detected 11/15/2022, 09:44:12 [pg3] error: addnode add driver error: UNIQUE constraint failed: driver.uuid, driver.profileNum, driver.address, driver.driver 11/15/2022, 09:44:12 [pg3] error: addnode add driver error: UNIQUE constraint failed: driver.uuid, driver.profileNum, driver.address, driver.driver 11/15/2022, 09:44:12 [pg3] error: addnode add driver error: UNIQUE constraint failed: driver.uuid, driver.profileNum, driver.address, driver.driver 11/15/2022, 09:44:12 [pg3] error: addnode add driver error: UNIQUE constraint failed: driver.uuid, driver.profileNum, driver.address, driver.driver 11/15/2022, 09:44:12 [pg3] error: addnode add driver error: UNIQUE constraint failed: driver.uuid, driver.profileNum, driver.address, driver.driver 11/15/2022, 09:44:12 [pg3] warn: ISY Response: [Try: 1] [<my ISY ID>] :: [ECONNABORTED] :: 7534.005203ms - http://192.168.200.251:80/rest/nodes/n006_207296 11/15/2022, 09:44:12 [pg3] warn: node 207296 on profile 6 already exists, no nodeDef or driver changes detected 11/15/2022, 09:44:17 [pg3] warn: ISY Response: [Try: 1] [<my ISY ID>] :: [ECONNABORTED] :: 5007.305041ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_forecast_9/report/status/GV1/-5.0/4 11/15/2022, 09:44:23 [pg3] warn: ISY Response: [Try: 1] [<my ISY ID>] :: [ECONNABORTED] :: 5020.107423ms - http://192.168.200.251:80/rest/nodes 11/15/2022, 09:44:28 [pg3] warn: ISY Response: [Try: 2] [<my ISY ID>] :: [ECONNABORTED] :: 5027.978098ms - http://192.168.200.251:80/rest/nodes 11/15/2022, 09:44:33 [pg3] warn: ISY Response: [Try: 3] [<my ISY ID>] :: [ECONNABORTED] :: 5015.460456ms - http://192.168.200.251:80/rest/nodes 11/15/2022, 09:44:36 [pg3] warn: node s_2930071732 on profile 8 already exists, no nodeDef or driver changes detected 11/15/2022, 09:44:38 [pg3] error: ISY Response: [MAX TRIES EXCEEDED] [<my ISY ID>] :: [ECONNABORTED] :: 5010.138324ms - http://192.168.200.251:80/rest/nodes 11/15/2022, 09:44:38 [pg3] error: Error: GET http://192.168.200.251:80/rest/nodes Failed :: ECONNABORTED 11/15/2022, 09:44:39 [pg3] error: [<my ISY ID>_8] checkDrivers failed :: TypeError: Cannot read properties of undefined (reading 'data') at Object.checkDrivers (/var/polyglot/node_modules/@universaldevices/pg3/lib/modules/Node server/status.js:269:64) at async /var/polyglot/node_modules/@universaldevices/pg3/lib/modules/Node server/command.js:144:13 at async Promise.all (index 0) 11/15/2022, 09:44:39 [pg3] info: [<my ISY ID>_8] adding node s_2930029938 to ISY 11/15/2022, 09:44:41 [pg3] error: No code in error response 11/15/2022, 09:44:41 [pg3] warn: ISY Response: [Try: 1] [<my ISY ID>] :: [400 - OK] :: 2917.629801ms - http://192.168.200.251:80/rest/ns/8/nodes/n008_s_2930029938/add/Sensor?primary=n008_controller&name=Main%20Floor 11/15/2022, 09:44:41 [pg3] error: No code in error response 11/15/2022, 09:44:41 [pg3] warn: ISY Response: [Try: 2] [<my ISY ID>] :: [400 - OK] :: 17.414811ms - http://192.168.200.251:80/rest/ns/8/nodes/n008_s_2930029938/add/Sensor?primary=n008_controller&name=Main%20Floor 11/15/2022, 09:44:41 [pg3] error: No code in error response 11/15/2022, 09:44:42 [pg3] warn: ISY Response: [Try: 3] [<my ISY ID>] :: [400 - OK] :: 13.28028ms - http://192.168.200.251:80/rest/ns/8/nodes/n008_s_2930029938/add/Sensor?primary=n008_controller&name=Main%20Floor 11/15/2022, 09:44:42 [pg3] error: No code in error response 11/15/2022, 09:44:42 [pg3] error: ISY Response: [MAX TRIES EXCEEDED] [<my ISY ID>] :: [400 - OK] :: 35.297172ms - http://192.168.200.251:80/rest/ns/8/nodes/n008_s_2930029938/add/Sensor?primary=n008_controller&name=Main%20Floor 11/15/2022, 09:44:42 [pg3] error: Error: GET http://192.168.200.251:80/rest/ns/8/nodes/n008_s_2930029938/add/Sensor?primary=n008_controller&name=Main%20Floor Failed :: 400 - OK 11/15/2022, 09:44:42 [pg3] info: [<my ISY ID>_8] addnode sucessfully added node s_2930029938 11/15/2022, 09:44:42 [pg3] error: unhandledRejection REPORT THIS!: [object Promise], reason: TypeError: Cannot read properties of undefined (reading 'status') 11/15/2022, 09:44:55 [pg3] warn: ISY Response: [Try: 1] [<my ISY ID>] :: [ECONNABORTED] :: 5004.806641ms - http://192.168.200.251:80/rest/nodes 11/15/2022, 09:45:00 [pg3] warn: ISY Response: [Try: 2] [<my ISY ID>] :: [ECONNABORTED] :: 5007.780992ms - http://192.168.200.251:80/rest/nodes 11/15/2022, 09:45:01 [pg3] error: addnode add driver error: UNIQUE constraint failed: driver.uuid, driver.profileNum, driver.address, driver.driver 11/15/2022, 09:45:01 [pg3] error: addnode add driver error: UNIQUE constraint failed: driver.uuid, driver.profileNum, driver.address, driver.driver 11/15/2022, 09:45:01 [pg3] error: addnode add driver error: UNIQUE constraint failed: driver.uuid, driver.profileNum, driver.address, driver.driver 11/15/2022, 09:45:01 [pg3] error: addnode add driver error: UNIQUE constraint failed: driver.uuid, driver.profileNum, driver.address, driver.driver 11/15/2022, 09:45:01 [pg3] error: addnode add driver error: UNIQUE constraint failed: driver.uuid, driver.profileNum, driver.address, driver.driver 11/15/2022, 09:45:01 [pg3] error: addnode add driver error: UNIQUE constraint failed: driver.uuid, driver.profileNum, driver.address, driver.driver 11/15/2022, 09:45:01 [pg3] error: addnode add driver error: UNIQUE constraint failed: driver.uuid, driver.profileNum, driver.address, driver.driver 11/15/2022, 09:45:01 [pg3] error: addnode add driver error: UNIQUE constraint failed: driver.uuid, driver.profileNum, driver.address, driver.driver 11/15/2022, 09:45:01 [pg3] error: addnode add driver error: UNIQUE constraint failed: driver.uuid, driver.profileNum, driver.address, driver.driver 11/15/2022, 09:45:01 [pg3] error: addnode add driver error: UNIQUE constraint failed: driver.uuid, driver.profileNum, driver.address, driver.driver 11/15/2022, 09:45:01 [pg3] error: addnode add driver error: UNIQUE constraint failed: driver.uuid, driver.profileNum, driver.address, driver.driver