hart2hart

I notice a light was not coming on when I walked through Ring light with motion. Finally got around to sorting it out. I did following: Checked all conditions and the motion event was the only thing missing for program execution. Looked at NS log and events were not showing Restart NS Rebooted eISY Stopped and Started NS Authenticated to Ring At least two times each above I reinstalled the NS and motion is detected again. Programs run and can see activity in the NS log works Let me know if you want me to DM logfile

It would be highly coincidental if it failed at same time of 5.8 install but I’ve had to recap both of mine as they fail like a PLM.

I’ve got two of them working with 5.8. At some point since the last irrigation season, scenes that included the device zones had an issue. I had to set the zones Scene On status in the scene. It had become Off and I selected it to On.

Open a support ticket with UD.

@Jimbo.Automates What do you think of adding the possible leak status?

Me too! My question is would it even be possible to use the ESP Home FW in our environment.

@Goose66 I’ve recently flashed with erase for second time. As you noted and others, the ESP Home FW does not appear to have this issue. Feel certain you’re tired of GDO at his point, but if MQTT FW is not fixed at some point is moving plug in to ESP Home even a possibility?

@Goose66 , thanks for the update.

Hi. ISY used serial PLM. You didn’t happen to purchase a USB PLM?

Sorry, I believe you want to replace plm.

If you manage it all with ISY, Polisy, or eISY, you do the restore from Admin Console. No drivers ever required for me.

At sunset, does the program show as true meaning it ran but the light is not coming on so a communication or device issue?

@Jimbo.Automates Just reviewed their api docs and looks like Leak is there but could not quickly determine if it’s a polled item or a true subscription.

@Jimbo.Automates Does the api used for node server include a value when a possible leak is detected?

Michel and UDI are always excellent!

Not a direct response… I don’t know if they’re sold now but I have Filterlincs on all noisy devices.

I had to enter their IP addresses when I first started using the node server.

I flashed them one at a time this morning (now I know why I took time to 3D print an enclosure for easy access) with erase and they are working again. I'll post and as you said we should post the issue on ratgdo site because it's likely to occur again. On the topic of rolling codes, I wondered on original install why the ratgdo did not require being "learned" by the garage door opener -- it just worked. I made sure this morning not to open door manually before reinstalling it and it worked first press again and seemingly did not have a chance to learn/teach.

I went to the ratgdo site. This might be issue #17. RATGDO not controlling opener · Issue #17 · ratgdo/mqtt-ratgdo · GitHub I did the OTA update with same version and it didn't fix it. In next few days, I'll get a laptop and erase and then reflash it. If that works does it imply there is an area of config data that is corrupted or bad from a bug and the erase is the only fix to get it back in sync?

Do I have to do this from USB port or can I do it with OTA flashing back to the same version it’s already running 2.57?

Same here. ratgdo did not control the lights or doors but the states tracked perfectly. @Goose66 I said sky was falling last week so hate to do it again… any chance the recent PG3x update for MQTT may have been part of issue? It was working early last week but I don’t know when it stopped. Edit: wife used the MyQ app to remote open and close door last week. She did not use UDMobile as I thought so can’t say last time it worked.

@oskrypuchRunning 5.8.0 on eISY. Don't know when it was included.

Its been quite a while since I used it but the ratgdos are no longer controlling my garage doors or lights. I've confirmed: Stable wifi to the two ratgdos Power cycled the ratgdos Restarted the node server Sent logs via PM. Thanks.

Thank you, @Goose66, and as always you are right about the timing issue. When I walk into the room and turn on the ceiling fan light via insteon switch mixed scene, it now turns right on. However, if I immediately turn on the ceiling fan via an insteon switch mixed scene, it does not typically come on and I have to wait some time and try again or press the fan remote on my desk. I'll turn on debug-level and send a log in next few days. Again, thanks for great plugins and excellent support. Paul

Thanks. I noticed the issues day before yesterday and didn't have time to look into it until this morning. As part of that, I saw the Bond Bridge had a firmware update pending so I installed it thinking it might be part of the issue. Version is v3.21.6. The off and on more rapid on off sequences were me stress testing looking to isolate the issues. I was turning off and on from insteon dimmer, switch and from the AC with control of Bond device and through the scene. By disconnecting are you seeing it leave the WiFi network? I have multiple access points and most access is accomplished through same SSID on all of them. However, for HA devices, I have specific SSIDs on each AP so I can know where they are connecting for issues like this. I updated it to another SSID and hence AP to see if that helps. What do you know... Results look very good so it could be a coincidence with the PG3x release but I'm in the office many times a day and it started Tuesday after the upgrade. Maybe Bond was on the verge of issue and something minor pushed it over the edge. I'll try to remember to update all again tomorrow. As always, thank you for excellent support Goose66.