This is just a boolean I made for on/off if the cats are outside. When you say toggling the relay do you mean hitting the button? If so, yes I am physically hitting the top big button when i let my cat out or bring him in. We mainly use it for the LED so we can visually see if hes out since it will be red. We have some automations when hes been out like 4hrs or more it pings us too.
But anyhow, before uysing this blueprint I used a very basic automation which didnt have an issue with the white led powering on. I am still thinking that maybe if I removed the āwhiteā led portion from the yaml it might work fine. And also 90% of the time it shows fine (without color). Every so often it will show white instead of blank tho. Unsure why at this point.
Hey @rwalker
Thank you, Thank you, Thank you!
I recently purchased a couple of Zen32ās (which are really great devices), but the missing link is your blueprint. I tried to implement this myself, but your blueprint is the secret sauce. I had the worst time with keeping the indicator lamps in sync with my own solution, but this has entirely been resolved with this blueprint.
The only additional quirk I encountered after loading the blueprint, was the fact Iām monitoring/affecting a very old Leviton switch (DZS15) that does not announce state on change, but has to be polled to know state. I implemented Z-Wave polling for that device and it works as well, just not realtime. Of course, this is not an issue of your blueprint - just an implementation detail.
Here is a link to that:Z-Wave Polling
Iāve searched and donāt see any mention of the Zen35. Do we think this should support all the features of the 35 including main button dimming and the 3way momentary switch, or is there an equivalent that supports it?
Iām my HA instance Iāve changed the filter in the blueprint yaml so that I can select any zooz device and chose my Zen35. Everything Iāve tried so far works, just curious if I missed a discussion where this blueprint has been previously tested with a 35.
Unfortunately itās not in the z wave database, but the descriptions on the Zooz website are very thorough.
Also, if youāre interested, I have a spare and would be happy to ship it to you if the cost is reasonable. The dimmer is a nice addition to the switch, I think.
I updated the blueprint to add support for ZEN35 and should work once the PR is merged and you update Z-Wave JS to that version. I did have to remove 2 Z-Wave parameters from the blueprint, set those on the device parameters.
Even after todayās Z-Wave update that specifically included a new profile for the ZEN35, I still canāt get the Blueprint to recognize it. It sees my ZEN32ās, but even after re-interviewing and, when that didnāt work, excluding and re-including it wonāt see the ZEN35. Worth noting is that in the Z-Wave JS UI it shows up as āZooz 0x7000 Unknown product 0xa018ā unlike the others which have their type and model number. Any ideas?
A question somewhat unrelated to the blueprint. Has anyone experienced the ZEN35 falling off the network? Iām experiencing a problem where zwave js ui regularly reports the node as being dead. The usual fix for dead node (pinging it) doesnāt work, so I have to resort to either hard-resetting the switch or pulling the power. Since thereās no air gap, pulling the power is a significant problem.
I contacted zooz and they suggested moving the ZEN35 to LR pairing instead of mesh inclusion. This improved stability a little bit, and even weirder, when it does die, pinging the switch does wake it back up again, so I at least donāt have to pull the power.
Ultimately, weāre going to try replacing the switch, so itās hopefully just a one-off problem. Just curious if anyone has run into anything similar.
One observation to add: could be coincidence or even my imagination, but prior to adding this blueprint, the switch didnāt have any problems. Could it be that the way I implemented the blueprint is overloading the onboard controller on the switch causing network dropoffs?
