GTench

Wow... Nice - thanks, looks like everything is there in the AC. Just need to spend some time today figuring out exactly what I am seeing and doing a bit of testing. If you need me to do anything else please let me know. I have attached new log file and a screen shot from AC hunterdouglas_2-27-2024_115158_AM.zip

@sjenkins ok did as you suggested. I still don't see shades in the AC. I rebooted eisy after deleting and again after reinstalling. I have attached the log file. hunterdouglas_2-26-2024_105227_AM.zip

@sjenkins Thank you for doing this. I am no hurry and would be happy to help anyway i can. Enjoy your hockey game.

@sjenkins Wow thank you very much! I was not expecting this. I updated to 0.1.2. I get a message saying "start up". Not sure what it means. I rebooted eisy but I still do not see any shades under HunterDouglas in the AC. I attached a log file. Please let me know if there is anything else you would like me to do Gary hunterdouglas_2-25-2024_120645_PM.zip

@sjenkins thanks. I have 8 shades so not worth it to replace everything with gen 3. I am using network resources for some limited functionality (open/close) now based on info from another poster a few years ago. Although this generally works, it is not totally reliable. Recently I added some zwave smartwings shades which wife likes and have worked pretty reliably

FYI... Got this reply from Hunter Douglas If you currently have PowerView Gen2 shades, hub and repeaters they are not compatible with PowerView Gen3 Gateways. PowerView Gen3 is Bluetooth operated and the motors run on a BLE signal. The only way to use PowerView Gen3 Gateways is to purchase new PowerView Gen3 shades. PowerView Gen2 shades cannot be converted to PowerView Gen3 operation as the internal components are also not compatible unfortunately.

OK thanks. I will look into the V3

Not sure what version the gateways are but I have had them for a number of years. I get {"message":"Not Found","error":{}} for http://192.168.2.239/home. I am not getting a response for the other one

Yes I did. I added the gatewayip key with a value of ['192.168.2.239','192.168.2.233']

Just installed this. Thanks! I have 8 shades and 2 gateways. All I see in the AC is just the HunterDouglas node with status of True. Just wondering why I don't see any shades. Gary

I notice that the server status goes from green to disconnected whenever I do a software update on blue iris. I need to manually restart the blue iris node server to return the server status to green. Is there a way to automatically restart the node server when this disconnection condition occurs? Gary

Been using Yolink now for about a year. I have a few motion, and humidity detectors along with 7 or 8 leak detectors. Echoing other users comments, I found everything very easy to set up and has been very reliable. Leak detectors are set up to trigger a Zwave water shut off value. This worked perfectly the two times it was needed. My only wish is that there be a local api instead of relying on the cloud. I was worried about this with the leak detection so I direct connected the leak detectors to a Yolink relay whose output can then trigger my Zwave water shutoff valve. I realize Yolink has a water shutoff valve that can be direct linked to the leak detectors but I already had a functioning Zwave water shutoff value and did not want to spend the money to replace it. If and when there is a local api, I will consider expanding my Yolink system. Gary

@Techman I updated eisy

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