GTench

Just did the upgrade. The disabled programs issue has been fixed at least for me. Thanks!

@kzboray I posted my results so did not need to DM. Don't need a ticket as I re-enabled the programs as I mentioned. Everything working fine for me. I just posted about the disabled programs as I did the upgrade after @Chris Jahnsaid the issue was resolved

Also tried this but got this so I manually enabled them

just did the upgrade but all programs are still being disabled

ok thanks. It is the first and only time that I have seen it.

Yolink was in a failed state today. Got a bunch of error messages in the log file today around 14:45. Loop forever message seems ominous. I attached the log file. A restart was successful YoLink_9-5-2023_33424_PM.zip

ok thanks. It's not a problem to change the time on the cellphone as once I set it I am not likely to need to change it

@Panda88 I had set up a scene that works very well all by itself without needing a program. I guess what I was asking is it possible to add a custom parameter to the node server config file which would be the time that the motion sensor does not respond to motion once motion has been detected. You can set this time in the yolink cellphone app now but not as a parameter/value in the node server config file

@drprm1I deleted and readded the same device. That worked for me. I suspect doing that creates a new .REC file to replace the corrupted one. An IoX restore from an old backup might work as well if the file in that backup was nor corupt but I did not try that

Just set up a scene with a yolink sensor and the insteon light switch for my cold room. Works quite well. The sensor is set to basically stay on for a few minutes then go off. So now when I open the cold room door the light goes on then shuts off after a few minutes all under the control of the scene - no program involved. I can adjust the on/off time for the motion sensor using the yolink cell phone app which works fine. Just wondering if this can be set with the node server as well. Gary

Looks like a corrupt file for insteon device 21.CF.D0. I had a similar problem and I needed to delete and readd the device. Or a restore from backup might work. Gary

@Geddy thanks but power cycling does not clear the problem. Will submit a ticket Gary

Update seemed to go ok but when I tried to do a backup for IoX, I got these messages. Tried 2x with same result Gary

I get a number of Yolink not connected followed by Yolink is connected messages. It is my only node server that shows this behavior. Just wondering why. I attached the log file. YoLink_7-7-2023_52913_PM.zip

OK thanks... like UD mobile very much... very impressed with it... great work

Just added the Notification plugin via UD mobile. Went well. Then purchased the standard version but now have this message on the details page for the node server. Not sure what this means. This version of PG3 3.1.31 will not work properly with Pushover or UDPortal nodes, Please upgrade modules and restart PG3. isyVersion=5.6.2 isPG3x=True pg3Version=3.1.31

Here is the PG3x log file based on a test that I just did pg3_6-22-2023_124130_PM.zip

The modem is also the dhcp server and is a router

I don't know if this will help but here are a few more details concerning what I did. I have an incoming fiber connection to a modem. The modem is connected to a unifi switch with an ethernet cable. The modem has its wifi turned off. Wifi is provided through out the house by unifi access points connected to the switch. I never enabled wifi on the eisy. Eisy is connected directly to the unifi switch with an ethernet cable. My testing consisted of unplugging the ethernet cable from the modem to the unifi switch for a couple of minutes then plugging it back in. If the disconnect/reconnect time is say 15 to maybe 30 seconds the node servers do do show fail but I have not timed this. Disconnect/reconnect of a few minutes caused a fail of all node servers I am using the latest releases of PG3x and IOX.

Bob, The node server authors are passing the issue back to PG3x. EnvisaLink-DSC_6-21-2023_10902_PM.zip YoLink_6-21-2023_11016_PM.zip

I did that first. Here is the reply that I got

I already did that and this is what the response was

Here is the log file. It seems to take an outage of a few minutes to trigger the fail. A short outage of say 15 to 20 seconds appears to be survivable but I did not time it Maybe just some background on this for interest sake... I( have a number of Zwave leak sensors connected to a Zwave shutoff valve but find working with Zwave wireless sensors to be quite frustrating especially trying to get them to reliably report battery level. I set up a number of YoLink leak sensors in place of the Zwave ones. The Yolink sensors are much easier to work with and the always report status, battery level etc. Knowing that they normallyYoLink_6-21-2023_11016_PM.zipYoLink_6-21-2023_11016_PM.zip require internet access to Yolink's cloud servers to report, I decided to direct connect them to a Yolink relay that I could check the status of even if the Yolink cloud was down. I can check the relay status using either an insteon device or a zone in my alarm panel. In order to test if the direct connect to the relay worked, I disconnected the internet in order to simulate the loss of the YoLink cloud server and that when I discovered all of my node servers failed not just YoLink

Here is the log file. It seems to take an outage of a few minutes to trigger the fail. A short outage of say 15 to 20 seconds appears to be survivable but I did not time it EnvisaLink-DSC_6-21-2023_10902_PM.zip

I will try again later and get the log file