GTench

Sorry to hear it is not working for you. I found that I needed the 1 minute wait because a number of my disconnects occurred when the computer running blue iris did an automatic windows update. This 1 minute delay gave the computer time to reboot and restart blue iris allowing the rediscover command time to see blue iris

I have 10 or 12 motion sensors used for both alarming and triggering room lights when not armed and they work fine with the plugin... no problems Gary

This is how I handle it: If 'Blue Iris' Server Status is Disconnected Or 'Blue Iris' Server Status is Red Then Send Notification to 'Gary' content 'Blue Iris Disconnected' Wait 1 minute Set 'Blue Iris' Re-Discover Else - No Actions - (To add one, press 'Action') Followed by a second program: If 'Blue Iris' Server Status is Green Then Wait 1 minute Send Notification to 'Gary' content 'Blue Iris Node Server Reconnected' Else - No Actions - (To add one, press 'Action')

I realize not all devices can be direct linked but I checked with Yolink about direct linking the relay before buying it. I believe Yolink promoted this direct link capability in particular for their water shutoff valve as a means to overcome criticism about their system depending upon the cloud. In my case, it came down to a choice of direct connecting the relay or replacing my Z-wave shutoff valve with the Yolink one, which was considerably more expensive than the relay. Also, I had already mechanically attached the Z-wave shutoff valve to my water shutoff valve. The speaker hub can not be triggered locally without an internet connection. I tried it and it did not work. Not sure if the local hub gets around this issue. The reason I used the alarm panel was because the relay needs to be powered (12V I believe). So, I mounted the relay on the alarm panel and powered it from that... just easier for me

I relaced all my Z-wave leak sensors with Yolink leak sensors because the reporting from the Z-wave sensors was spotty and battery life was poor. Since Yolink has the capability to direct connect wirelessly devices together, I made use of that capability so I would not have to depend on the internet/cloud being available. This way they are operating in a local mode as well. I direct connected all the leak sensors to a Yolink relay which then connects to a home automation zone in my alarm panel which is being monitored by eisy (although I could have used an insteon sensor instead of an alarm panel zone). The eisy then triggers a Z-wave water shutoff value (which I originally got with the Z-wave leak sensors) when a leak is detected. It will also send an email if the internet is up. I set this up before the Yolink local hub was available. This has operated/triggered 2 or 3 times successfully over the past year or so. I don't use Alexa but I do have 4 speaker hubs scattered through the house. They are used to announce various events like garage door being left open and water being shutoff due to a leak. @Panda88 It looks like you can have more than 10 messages. I believe you suggested earlier in the year to try more; so, I did. I tried 11 messages and that worked. Not sure what the limit would be Gary

@sjenkinsso far everything is working just fine. I will let you know if I run across any problems. Here are the logs from the non production install HunterDouglas_10-9-2025_124159_PM.zip

@sjenkinsthanks again for looking into this. The reinstall worked without raising the error message. I am running on eisy and have been since it was introduced

@sjenkinsOK here it is HunterDouglas_10-6-2025_110206_AM.zip

@sjenkinsOK here is the log file. AC shows it as connected but programs not working HunterDouglas_10-5-2025_102538_AM.zip

@sjenkinsSeems to be running according to the AC but PG3 shows this message

@sjenkins Glad to help. I was initially delaying testing because I thought IOX 6 was about to be released and I was hoping to install it first before testing. I installed your production version and it is working well.

@sjenkinsYes everything appears to be working normally. Thanks for your help. You were correct about the app. it did not show status either. I refreshed the battery status and it now appears in both the app and your plugin. I suspect the AC lockup issue that occurs with both plugin versions installed might just be a problem with the AC

@sjenkinsOK thanks. No matter what I do/try I cannot get the AC programs tab to open if I have both the production and beta versions installed at the same time in different slots even with one or the other stopped - the AC just freezes; so I deleted the beta version and installed the beta version into the production slot. This seems to be working o.k. I can open the AC programs tab and a test of one of my programs worked successfully. I can also manually open and close a shade from the AC. I notice one of my shades battery status says "no status". All the other shades show battery status

@sjenkinsJust a follow up. I tried manually opening and closing one of the shades from the AC using both the beta and production versions once I identified the shade using the number and that worked ok. Both beta and production were installed. I still cannot load programs with both beta and production installed.

@sjenkinsI was thinking of biting the bullet and just install the beta version as a replacement for the production version and test it that way but first I thought I would see if I could manually operate the shades from the beta version in the AC; however, I noticed that the names are not correct now. Just wondering if you changed anything.