GTench

Nice to see someone is still using it. I had an Ocelot/Leopard setup for many years as well. I used it to control my HVAC, a few baseboard heaters, sprinkler system, and lights in the house. It was a nice system and worked well for many years but I switched over to ISY in 2014 because of 3 main issues: my leviton 4 button X10 switches kept failing because of heat problems; a bug with the X10 preset dim commands; and the screen on my Leopard failed and a replacement was a special (and expensive) order.

Yes... latest firmware. It is a responder link in a scene assigned to an Int Var that contains the percent value for the shade to open to. It works fine just had to figure out what the UoM's meant

Is it possible to change UOM 25 and UOM 51 to more meaningful text such as index, percent

@wmcneil Here is what I do for checking the battery level and it work fine. Have not tried for shade position but should work for it I think Gary Spare Bedroom Right Shade If 'Zwave / ZY 035 Spare Bed Right Shade' Battery Level < '$Int_Shade_Battery_Low_Level Percent' Then $Int_Shade_Battery_level = 'Zwave / ZY 035 Spare Bed Right Shade' Battery Level % Send Notification to 'Gary' content 'Spare Bedroom Right Shade Battery' Send Notification to 'Debbie' content 'Spare Bedroom Right Shade Battery' Else - No Actions - (To add one, press 'Action')

@awysocki I just tried connecting an Eufy robot vacuum to eisy on 6.1.1. Similar experience to you. Sees the vacuum but fails with the 15 second commissioning timeout. Gary

Just did the upgrade (insteon, zwave, plugins). Everything went fine. No issues. Gary

@wmcneil Yes that works well. Here is what I do. I have 6 shades installed in my family room. I put them into a scene as shown below. Each shade has its "on" value set to a different integer variable in the scene. In programs, I set the values of the integer variables to various % levels as determined by the outdoor sunlight levels then the scene is run and that sets each shade to its proper opening value Gary

Not really sure what you are asking. In toggle mode (true) you get a chime whenever an assigned zone opens or closes. In false mode you never get a chime. Are you wanting to do something different?

I think I actually just deleted the blind from eisy then did the reset and repaired. I actually have 13 Zwave blinds...I miscounted before

@ImagineAir Yes, I have 6 of them connected to the eisy but I am using Zwave USB. I did have trouble pairing one of them. I think it got stuck part way through pairing for some reason. Excluding and/or repairing did not work for me. It seemed to be in a state of limbo. I ended up doing a full reset on the blink to clear the issue. The mechanism for this depends on the blind model but should be somewhere in the instruction manual. Unfortunately this also cleared all preset up/down limit positions which I had to redo. This reset then allowed me to redo the pairing. I don't believe I did an exclude before repairing; it just repaired.

I also have a ZSE70 installed on eisy 6.0.5 with the ZMatter board and it shows temperature

I also use the DSC polyglot plugin. I have 64 zones with many of them integrated as triggers in various ISY programs. I am extremely happy with the performance

So you can see the zones in eisy but not in EyezON? If so, do they change state properly in eisy when activated?

If you cannot see zones in EyezON, then I am guessing that is why it is not working with the plugin

My setup is not exactly like yours. I have a DSC panel with 64 zones and the EnvisaLInk 4 and it is working well with the plugin. Does not the Neo come with 8 zones? Just wondering why you needed the UNO4 expansion board to make EnvisaLInk work? Is the UNO4 (UNO 8?)board properly registered with the motherboard?

I assume the XXXXX are just to hide real values?

@jim_ I have a number of hardwired alarm PIR motion sensors throughout the house all connected to a DSC alarm panel. I use the DSC plugin to connect these to the eisy to control insteon lighting via a number of different programs depending on the locations needs. Once the PIR has detected motion (as indicated by the red LED illumination), the triggering of the lights is very quick. The only delay that I notice in this setup is with the PIR sensors. Sometimes they activate very quickly, sometimes slower. The PIRs have sensitivity adjustment and I could adjust those but so far any delays have not bothered me

Update from 6.0.4 to 6.0.5 went smoothly. No issues for me

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