brians

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.

@macjeffdiscovered that IoX restarts/reboots if force close java app and many mobile apps. I am still experiencing it in 5.5.6 and just discovered this bug myself last night. I though I would mention this here since this is latest support thread and people may overlook in the older one. Since most do not use Macs they may not have noticed but it is reproduceable in Windows and mobile apps if force quit app. He is mentions that he is going to work with Michel today but just wondering if this affects more people than us two?

Add to this: UD mobile also crashes IoX if force quit app in iOS - ie swipe up. I actually had it crash in me last night on my iPad and noticed this and wondering what was going on. I just did now in iPhone and iox rebooted. I am on Polisy running v5.5.6 so not fixed in that version.

Ok, this explains why I was going crazy last night working on my Mac and making changes in Homebridge. I was also experimenting again with Homebridge isy Maker in hopes of making Zen32 relay show up in Homekit via that and a variable (binary switches don't seem to show up - do you by any chance have a solution?). I noticed the IoX kept restarting and I think had something to do with the isy maker plugin how it hooks in live to homebridge, so I disabled and no restarts over the night.

Copy program to clipboard and paste instead of the screenshot. Double tap should be is Fast On. It is also possible that during migration to EISY, your programs are missing things to display correct even though they are actually working. Make an entire new program with Fast On and temporarily disable this one and see if that works if you are scared of breaking things. Also usually clicking on something and hit save, or maybe making a comment and save may fix/rewrite the program properly in the system.

I go over this here the two methods for using Zen32 buttons... zwave basic association and programming. Although basic assoc works for on/off to control another zwave device, the button state will get out of sync if you turn on/off the actual zwave device manually and will have to press Zen32 button twice. I believe that programs are the best option if want to keep LEDs in sync, and also that way supports other devices to control like Insteon. @TRI0N it supports 2x press, select Fast On in the pulldown It is a carry-over nomenclature from Insteon, where a double-tap on an Insteon switch is called fast on or fast off.

Curious what the nodes look like and how it shows up in IoX to control it. I have a Zen17 for IoX control, and also a cheap $30 native HomeKit wired in parallel so I can use my iPhone/Apple Watch with Siri (was easier than trying to get it into HK other way).

Oh I got a response from Zooz, they basically told me that zwave scenes using basic association are not that common anymore and the way to do is how I did it in programs, even providing an argument that all zwave devices have to have same security to do basic assoc as a reason not to do this way (who cares, I can handle that). I am sure their engineers could still add the tweaks I suggested pretty easily, unless they are very constricted by memory for new code/routines... or maybe nobody there knows how to fix it anymore eg. original devs gone, maybe part was outsourced or some intern wrote the code years ago... who knows. Just baffles me that they can develop something this far, but not make it function like one would expect.

On my Polisy it did just that, but I noticed that PG3 was saying that was reporting older ISY v5.5.5 so usually restarting PG3 fixes, that is when it failed for me.

Don't use scenes, use program method instead. You are never able to query a state of the small buttons (only big button). Therefore, I don't worry at all what the state of buttons are on Zen32, and instead set the LEDs of the Zen32 buttons to how I want: to states of the lights etc. desired for each button. Look at the programs again above The last (3rd) program I set parameters to keep LEDs always on... the program is not needed and you can do all this manually but I find convenient to have in testing and makes sense hopefully when I look at it months from now. The first program turns button blue when any light status on, and white when all lights are status off, both using Parameter 7 for button 1 on Zen32 (see comments in that program which sets the parameters), and also sets a variable indicating if lights are on or off. The 2nd program turns the lights on or off from Zen32 button 1 depending on how that variable is set which makes it a toggle (which is why I put Toggle in the program name). Variable is used to track the light state because every time press a Zen32 button is pressed it sends an On command. I also use variable to track multiple lights being controlled by Zen32 but if were just using one light then can instead just check status of the one light instead of using variable. Note that you have to make these two programs for each button, and a variable, therefore 8 programs and four variables for one Zen32. I suggest you make a couple programs like above and experiment with them and you should figure it out when you see it working and compare to what I have done or maybe you will find a different way that works. There is really nothing else I can explain further.

I updated my Polisy. After the update Polisy did not reboot, PG3 was loading but showed incorrect version of ISY so I restarted PG3 and still does not start. I rebooted Polisy three times so far and still PG3 not working. I can get into AC and PG2. So what I did is ran the update from ssh.. /usr/local/etc/udx.d/static/udxops.sh upgrade.polisy Which fixed it, I notcied it downloaded pg3:3.1.17_1 The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pg3: 3.1.17 -> 3.1.17_1 [udi] Number of packages to be upgraded: 1 12 MiB to be downloaded. [1/1] Fetching pg3-3.1.17_1.pkg: .......... done Checking integrity... done (0 conflicting) [1/1] Upgrading pg3 from 3.1.17 to 3.1.17_1... And as I was monitoring its progress in shell and was done, I refreshed PG3 web page and is working now. Not sure why wasn't done/updated when pressing update packages. UD really needs to fix this update process.

To monitor my septic lift pump I used to use an old Insteon switch that had a sense line. I then plugged in a multi-plug adapter into the float switch and had this Insteon switch along with the pump itself. It would detect when the switch connected. Since that was old Insteon device single band and unreliable over time I looked for some other way. My pump runs for about 5-8 seconds also. I had tried a Zen 15 which advertises for sump pumps but it is not quick enough to detect current. I ended up using a Zen17 and one of these... https://www.amazon.ca/gp/product/B07PT5SC9M/ref=ppx_yo_dt_b_search_asin_image?ie=UTF8&psc=1 I have modified an extension cord that goes between the float switch and the pump plugin so the hot wire goes through this device. Once calibrated, it is near instantaneous with Zen17 reporting back to IoX when pump comes on it detects the current and the NO circuit becomes closed which are connected to Zen17 dry contact input sensor. I tried a Zen51 which has current sense and in my test it was very fast and responsive when detecting load, but for some reason the sensor did not work correctly when plugged into the float switch along with the pump so I staying with Zen17... need to clean it up a bit cuz I have excess of wire etc. I got it working in test and never bothered cleaning up (that green coiled extension cord can be shortened a bit LOL). I Benefit of Zen17 is since it has a second input, can hook up a float level sensor also on the 2nd input to detect if water level is too high... I have tested these but I haven't fully installed yet because I don't feel like taking apart the tank lid again... I have water leak sensor on surface and my water cop shuts off water main when detect leak so is good enough for now. https://www.amazon.ca/gp/product/B097ZCP3TC/ref=ppx_yo_dt_b_search_asin_image?ie=UTF8&psc=1

Note this fix was originally discovered by over in the support forum for 5.5.5 by @shbatm, was just passing on info I seen over here

maybe because you typed mongo-cdriver instead of mongo-c-driver ?

If buying today I prefer Zooz since they have more parameters and tweaks can do to them, and also GE don't seem to have 700 series yet available. Also mentioned before the GE take a second or two to update status to controller where Zooz are instant. My GE running downstairs has not had the problem my other one had so maybe it is a dud switch. I'll install somewhere later and test.

Are you saying that while double tapping, the scene picks up the first tap and turns on switch if switch is off? In this case I would not put the GE switch nodes in scenes as a controller and instead use programs exclusively to detect the button via control and run appropriate scenes... use on for scene on and fast on for double tap. I don't think GE do triple, 4x 5x etc.

I usually rename my nodes to something shorter and tuck away all the unused ones in a folder named ZWave extra nodes. Before I rename, I make a copy of original name and then place in notes so I can always look at what it was originally. Can't help but notice this is Zen32 you are showing, and how you are making separate programs for each on/off state keeping track of variable it seems. I can't see all what your programs do so not sure... but I do something similar and use two programs per button, but also keeps ZEN32 Button LED in sync even if load is turned on/off remotely.. see here, not the basic association method but program method.