stevehoyt

Done check your messsages and let me know if you did not get the info @Panda88

@Panda88 UDI just logged in and took a look....The current best guess is that the payload being sent back is too large to get transferred before a timeout. They are investigating. I will let you know what I hear. This all started around the time I added 2 new sensors to my yolink. That may explain it.

I have been running the YoLink nodeserver for months without issues. A couple days ago, I noticed that the values are no longer being sent to the ISY. They are fine in the YoLink app I checked the nodeserver log and am seeing this error. See below. Many messages in the pg3x logs too but no idea what they mean. The developer mentioned he had seen it too and also on other node servers and that rebooting Polisy fixed it. I have rebooted my polisy and ISY multiple times and upgraded all modules to no avail. Also I have reinstalled all node servers. Has anyone else seen it? Does anyone know where I should look to figure out what is causing it. I am thinking perhaps I need to write a UDI ticket. Thanks

i have updated everything, rebooted everything multiple times and it is still happening. @Panda88 should I submit a ticket to UDI support?

I have been running this nodeserver for months without issues. A couple days ago I noticed that the values are no longer being sent to the ISY. They are fine in the YoLink app I checked the nodeserver log and am seeing this error. See below. I have rebooted my polisy and ISY and upgraded all modules to no avail. Does anyone know where I should look to figure out what is causing it. Thanks @Panda88

I assume Polisy too though, I have not tried any yet. Am running all my Insteon via the plugin/Nodeserver and it works great.

Yes he was working with the devolper and me on the issue. It is my understanding that the state now is the best we can expect.

I have been having the same problem with another pluginfor a number of months ...Here is the response I got from the developer. When something happens at the same time every day, it is usually something external to the plug-in that's causing that disruption. I.E. router reboot, dhcp server restart, etc. The reality is that those types of events effect your entire network, but it may just be the UDI system that notices them and reports it as an issue. The plug-in's are working correctly. They log the network error and then re-establish the connection and continue working as if nothing had happened. The only reason you even know that this happened is because we make use of the MQTT broker's built in facility to notify PG3 when a client (plug-in) connects and disconnects. We do that so that PG3 can send out notifications and set the plug-in status appropriately.

FYI @bpwwer it has been awhile since I posted about this... The problem seems to have largely gone away. I maybe, but not always, get 1 or 2 errors a day. The odd thing is that I get one like clock work at midnight every night.

Same here all programs disabled with DST change. I had to manually enable all of them. Polisy PG3X v 3.2.8 IOX 5.7.0

@bpwwer Check with benouit I just had a couple errors with I believe the new software installed. I sent him all the log files

Just to make sure that I get this correct. @bmercier The time zone is currently set to SF CA. The time in the AC is correct and the PG3x is 2 hours behind. Are you suggesting that to get them in sync, I change the time zone in the AC? If I do, should I change it to another city in the same time zone or to a different time zone and then back again to the correct one. It is not a big deal I can also just wait until I boot the Polisy again and see if it fixes itself. Thanks

Since I am the one seeing the errors every few hours, I just updated per your instructions. All appeared to go fine, though I could not find the message confirming the new version. I will let you know if the errors stop. @bmercier I did notice something odd in looking through the PG3x logs for the message. All the PG3 log messages have an incorrect time. It is 2 hours behind the actual time. I checked my Admin console for IOX and it is correct. Any idea why this might be and how I could set the time to the correct value Thanks

@bpwwer Saw your post to benoit about a new version. The error is happening a lot today for some reason. I am seeing it about every 5 to 10 minutes today. Let me know when it is in the non production area and I will install. Steve

@bpwwer I had a whole bunch of errors yesterday. Have you had a chance to connect and did you see them Ignore the ones around 2AM and 4AM. My eero routers updated and restarted causing them

No problem go ahead and run it for a couple days and lets see what happens. I don't know if Davis has any limitations on how often we can query. If so, I can shut mine off for awhile until you get the data you need and it won't hurt me. I am not sure what your options are for changing the nodeserver are, but I don't have a problem deleting a station in the node server for now. I rarely restart it so no big deal. Per benoit's answer below to me. Is it hard to just do the poling via 1 thread only as a permanent fix? "I think the problem appears when the nodeserver tries to publish data simultaneously from 2 threads. I contacted Bob, and the nodeserver indeed can publish from 2 threads. When polling, there will be one thread per weather stations, and they basically get polled at the same time. This means that it is likely that publishes can happen at the exact same time.

@bpwwer I see that Benoit has talked to you about this issue. What are your thoughts? Should we have the option to turn off one of the consoles? I know I can delete it in the config section. I would be perfectly satisfied to turn off one of the consoles. Most of the data ( except indoor temp humidity etc) is all coming from the same outside source, so it is redundant. I have multiple consoles so that I see the info in different rooms. The one I would turn off in my case would be "Steves House" Steve

FYI I am seeing about 10 of these errors per day. Also see an occasional similar error from the solar edge nodeserver. If you think it would be of value, I can open a ticket with UDI. About all I could say is to contact you as you know what is going on. As I am running a Polisy not EISY I doubt anything would get done. Let me know if you think it would be of value otherwise I will just live with it for now.

I'll keep your comments in mind and watch what is going on when I see the errors again. Xfinity internet has been flakey the last few days here. That may be the cause. Pardon my ignorance I know nothing about MQTT, but where is the MQTT broker living. Since I have a polisy I assumed everything was on it. Thanks

@bpwwer Got the fixed version installed. So far all looks OK. I'll keep checking. I have been seeing disconnects every few hours though. I have attached a log file for you to look at. Note the ones around midnight and 3 AM. Are you seeing the same thing on your connection to me. Steve Davis_V2_10-4-2023_61205_AM.zip

@bpwwer I just tried the new version. No change as far as data for the airlinks being displayed. Also for the fun of it I tried to write a program with an if statement on both of the airlinks and the parameters do not appear in the if. I am not sure if that means anything. No idea why you would not see both airlinks, but if I had to guess it probably is related to the weather link pro share. I will message you privately with the API v2 keys. Why don't you see if that makes a difference. I am not sure how much polling they will allow, but for now lets give it a try. If you need me to I could delete one and see if the data would display then. I prefer not to do that if possible but will if needed. I could try deleting it from your config file too if that would help. Let me know what else I can do.

I should have told you I changed the name from office to equip closet. as I moved it. We both should be looking at the same thing, perhaps the renaming caused the problem. Anything I could do to help figure this out?

@bpwwer a bit of new info. I stumbled on this z-wave X-ray this morning. It shows the airlink info is there, apparently the admin console can't display it for some reason. FYI i cleared java cache and redid the test. Still the same results.

just updated to 5.7.0 on Polisy and all programs were disabled.

@bpwwer There does appear to be something wrong with my airlink fields getting updated the admin console.It does not appear ever to be updating. I never see what you had shown in your other post for an airlink. . Whenever I select airlink it shows the last item I selected. See an example below I had selected the Vantage pro first and then went back to the airlink. To make sure all was well, this AM I updated all modules on the PG3. I then deleted Davis V2 and restarted the Admin Console to clear everything. I then reinstalled the Davis V2 node server and restarted the Admin Console. Same thing. If I look in the PG3 nodeserver logs it is setting up my 2 airlinks OK. I quickly checked if they showed up in the info sent from UDI to Home assistant app and they appear to be ok. So it looks like an Admin Console issue. Here are the versions I have currently installed. Let me know what you think I should try next. PS When you try it from your side connecting to my station is everything ok? Very weird if it is. Thanks Steve