brians

I never had this issue but I don't use Alexa. However I did some testing using AC to lock/unlock mine and was pretty fast response, but after about half dozen repeats the lock started appearing sluggish and similar to how you described and took forever to update its status. Restarting IoX resolved the issue. Try restarting IoX and see if that temporarily fixes.

I have mentioned this problem from beginning and is still not resolved. This is not really an issue with ISY, was rather an issue with Leviton not wanting to pay a patent royalty (which now is expired) to support instant status. Their workaround was to use Hail. Many other hubs do this behind the scenes for these switches. Therefore it is hidden to what is going on, which unfortunately gave a false impression that there is nothing really wrong with these switches. Moving to ISY it is easily discovered the trickery! I only have three of these Leviton switches - one is controlling an outdoor light which for some reason the builder placed switch in coat closet so it is just a responder style controlled by a keypad Linc, and never is turned on/off locally so I don't require instant status or hail. A 2nd is in closet in basement which I use a program that queries then once per minute which is better than nothing. The 3rd is sitting on my table last time I noticed. The other leviton devices like plug-in outlets never get turned on locally so instant status or hail is not needed. Hopefully UDI can fix hail, I was working with Chris on this while ago and sent info about the switch but I believe is low priority.

I think I may have found a bug in my program, I notice that after the fan schedule program runs, light still comes on sometimes. I can see down hallway while watching TV in family room. Since I have motion sensor set to 10 sec reset which is the quickest, these lines in the fan on program... Set 'Downstairs Bathroom / Downstairs Bathroom Fan' Off Wait 4 seconds Enable Program 'Downstairs Bathroom On' I should wait at least 10 seconds (probably bit longer just in case) prior to re-enabling the Downstairs Bathroom On in order for it to clear the motion sensor state if was accidentally triggered via RF interference when bathroom fan is turned off. I think that enabling the program with motion sensor on may make the if true, but not sure on this. Gonna make change anyways and see if fixes.

I am going to try it with Zen51 hanging out a bit further away from the GE motion light to see if interferes still. Putting in fan box would work, but there is also a humidistat control in hallway outside that is wired in parallel and turns fan on so based on humidity setting so not sure how that wiring would work at fan. I would have to change the Zen51 parameter from momentary back to toggle and I would also gain ability to tell when fan is on with humidistat... but I think it could get out of sync if turned on/off remotely and make humidistat be backwards. Maybe I can wire behind the humidistat instead. The downstairs bathroom does not have a humidistat so would be a more suitable location to test this. Ideally, should remote the humidistat and use something like ZSE40 to monitor humidity. Not sure why they put these humidistats in, think it is code, but I doubt that one fan can dehumidify the entire house considering I have three levels.

What if you got to change edit and save ? Is it the programs or notifications themselves ?

Update... I replaced the Zen71 with a Zen51 and a modified decora dumb switch so it is momentary. It has same interference issue... was thinking of putting a tin foil shield in between out of desperation of other things to try LOL. First time wiring up a Zen51 like this and works great, but considering the price difference it makes sense to just purchase something like Zen71 instead which is easier to install. Only use I can think is if want to control/add ceiling lights with no existing switch, or if your switch box has no neutral. Maybe I should throw an Insteon switchlinc in there instead It is a very common configuration to have a light and fan switch in same gang box in bathrooms.

I replaced it today with a Zen51 and a decora switch converted to momentary... still same issue as last two switches (Zen71 and a GE ZWave switch can't remember exact model). Ill update my thread with details but have a feeling I am talking to myself sometimes LOL.

EDIT... been a long time since I used Alexa routines but others have posted it is easy to do using portal. I personally like doing local control and not rely on cloud to for things like this. Those things look neat and I notice they support homekit so maybe they will support matter in future and could then work with zmatter board when it’ is upgraded.. Are you thinking of buying these or already have ? Curious how they work in reality. What insteon devices are you currently using ?

Here is PDF I had that lists all the parameters. Still had to experiment with it a bit to understand the meaning behind some of them and how it actually works in reality. Also a doc fix which may be simpler to follow. Jasco In-Wall Motion.pdf GE Jasco 26931 ZW4006 In-Wall Smart Motion Switch.docx

I have two of these and have same issue with the motion sensors triggering when adjacent switch is turned on/off, and same thing in two different locations. I personally don't like them and will eventually change them out if something new ever comes out. I have mitigated the issue somewhat with programs, disabling the motions sensor while turning fan on/off etc. but now and then I still see light turn on in bathroom randomly so something is still messed up in my programming. See this thread. I also list some parameters in programs may be interested in eg. parameter 13 set to 1 is motion sensitivity high.

Maybe there is a correlation between some ZSE29 working and some not based on firmware version.

I looked on zooz site and there are several hardware versions of zse29. Maybe some work while others do not? Unfortunately no firmware updates are available. What is your hardware version?

Add them and uncheck all the security no s2 etc.. See if works.

You can have one custom notification containing ${sys.program.#.name} which the calling program will be displayed. Not exactly what you are asking, but this way can minimize the amount notifications, however the notifications would be more generic but if just using for simple notification of heartbeats then probably fine. For example, if program is named "Laundry Room Leak Sensor", you then have this customization.. It has been over 26 hours since ${sys.program.#.name} detected a heartbeat. Then have a bunch of programs named matching the sensor name and each call this program if heartbeat missed. Can you show your HA program so can see how HA does it. I sorta wish IoX had more general scripting option. I think if IoX programs not really as full programs, but little subroutines and store them in a folder which I think of more as the full program. But to do basic things it is awkward sometimes because of the event driven and non-reentrant nature of how programs execute.

My Yale assure lock is now working correctly in 5.5.7.

Resolved IoX restart issue for me Will test my Yale Assure lock when home and follow-up.

I would wait for official announcement, don't want to give any instructions that will break it, but it is same as before basically with maybe a reboot

Michel told me was gonna be release today, got tired of waiting for offical announcement (cuz I'm impatient) so though I just did an update and got 5.5.7 which seems to fix this now... tested rebooting buncha things and AC stays up

Yes this was an issue that @macjeffreported and I realized I was having same issue. He worked lots with support to get resolved past few days and I believe is now resolved. 5.5.7 fixes (not announced yet). FYI, the reason for reboot is if any subscribed/connected app quits not gracefully it will restart AC. Programs like UD Mobile force quit, AC force quit, HomeBridge restart etc. all caused.

I managed to find a CT-101 for only $50 CAD, which I received and setup last night. It works fine except I do also notice that issue where it does not update the state instantly from idle... I am using on my gas fireplace so all I use is the W and RH. I didn't want to run it for long time last night to determine if it ever updates. However, it is going down to -20C tonight so will test and see if updates after a few min This CT-101 I bought is capable of running on battery without C wire, which works perfect for me because the thermostat I replaced was only 2 wires... surprisingly it updates and responds fairly instant off battery (except for the state issue). As long as it updates eventually I can probably live with that. I just wanted the ability to control/turn off fireplace remotely if accidentally left on, maybe make alexa routine, more complicated for wife LOL.

Regarding compatibility mode, how do we see the current state of a device if it is in compatibility mode or not?

@Chris Jahn Just noticed since 5.5.6 my Yale Assure Z-Wave lock no longer automatically updates status when manually locked either turning lock or by keypad....worked fine before. Updates status only when unlocked manually, unlocked by keypad, but not locked by keypad, or when turning the lock manually. A manual query gets correct status after lock. Edit: opened a ticket.

Just add the IP in manually into the IoX Finder... I find it unreliable at times.

My programs I linked to a few posts up solve the toggle problem for non-zwave lights... go check them out. I use to control/toggle a zwave light and insteon light from same button and Zen32 LED stays in sync no matter how the lights were turned on/off. For philips hue, I am thinking of getting a starter kit. Are you using the node server or network resources? Seems simple but could be a big time waster

Since you named it with "Basic Control" this hints at me that you are using the basic association nodes in your programs. Can you show the actual node address of that? My programs instead use the central scene button 1 ZYxxx_201N001 and you may be using ZYxxx_252N004 for basic association (eg. if button 1). which could explain this... for example both these nodes will respond to button 1 press. From my understanding how Zen32 buttons work, and if this is the way you are doing then you should not have to press it twice, unless it got out of sync by the light being turned on/off elsewhere.