hart2hart

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.

Yes, they are access points with board just like PLM.

@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.

Replace the capacitors. I’ve got several that are 15 years old after a little TLC and yes the C is capacitors.

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.

PMed them. Thanks,

Thanks. The response for mixed scenes with Insteon switch controlling a fan and fan light no longer works more than 1 in 10-20 times. I've removed them from scenes and added them back. Will await your feedback.

@Goose66 Does the Bond NS use MQTT as I appear to be having issues with the Bond Node Server controlling ceiling fans since this upgrade. I turn them on and off and it appears to have an issue if I turn it on and then turn it off quickly or vice versa as it starts ignoring the updates for some time. Als, I tagged @bmercier in the PG3X 3.2.20 support thread. I've done all the usual restart reboot etc with exact same results.

@bmercier I appear to be having issues with the Bond Node Server controlling ceiling fans since this upgrade. I turn them on and off and it appears to have an issue if I turn it on and then turn it off quickly or vice versa as it starts ignoring the updates for some time. I've done all the usual restart reboot etc with exact same results.

Thanks.

Should those of us that have already moved to the NVME drive create that directory! If so what permissions should it have? Thanks!

FWIW. My magic home LED strips are working after the upgrade.

Thanks. I’d forgotten the cable length requirements. To get my PLM in clear RF space, it’s always been about 25 ft from the ISY and now eISY.

I migrated over my serial PLM from ISY to eISY. Works great. Significant Internal processing are same between it and USB. Unless the serial to usb converter adds latency should be same speed.

Here it is. It uses the Timedata node server renamed to Date Time and Celestial Info in eISY. DayLight Saving Time:Check For Change If 'Date Time and Celestial Info / Calendar' DST is not '$Daylight_Saving_Time_Current Boolean' Then Wait 5 minutes Send Notification to 'MeSparkMail' content 'Daylight Saving Time Change' $Daylight_Saving_Time_Current Init To 'Date Time and Celestial Info / Calendar' DST $Daylight_Saving_Time_Current = 'Date Time and Celestial Info / Calendar' DST System: Restart IoX Else - No Actions - (To add one, press 'Action')

Historically I always rebooted ISY after time change. With eISY upgrade last year, I have a program that detects DST changes and reboots the eISY several minutes later. Works great and sends me a message at time change and my standard reboot message comes a short time later.

Depending on number of breakers in your box, you might start by turning off a few breakers at a time to see if remaining still work and narrow it down to the circuit making it easier to find the device.

Do you get errors doing a backup?