jec6613

First I've heard of that on the dual band 2477's, I sent backlight levels around 6 times per day and it's been going strong for six years.

Store temperature in variables and compare the variables.

Did it this morning for PG3x update, also got 5.8.0... any changelog yet?

Have you updated the firmware to the latest yet? The Z-Wave 800 stuff is still early days, that'd be my first step. Second would be to enable the Z-Wave compatibility mode, if that doesn't work. ZEN32 Scene Controller Change Log - Zooz Support Center (getzooz.com)

Back in the old Insteon forum days (days of yore..) somebody took a poke at the deep documentation and determined that you can indeed sever the front keypad from the back control, including the fast on, creating an additional device in their ISY (so an 8 button keypad would have an xx.xx.xx.9 device added) to control the connected load. I don't recall that it was easy to do, and obviously the ISY doesn't have the built-in functionality, but it is technically possible. Most people just put a micro module behind their keypad for such requirements.

What worked for me was to right click on the device in the AC, go to Z-Wave, Compatibility Mode, then set Compatibility Mode On. It fixed the exact issue you describe. The user number shows up under the ZY000_306 "Access Control Alarm" node.

If you run out of addresses (255) it will wrap around and start using unused address spaces, but not before then. You can end up with actual phantom devices, which you can use the failed device procedure to remove. As a rule of thumb, keeping your zwave network under 100, or under 50 if possible, greatly reduces congestion.

I posted this in another thread, but what's always solved this for me is 1) restoring the device from the AC and 2) increasing the retries from the PLM. I also have an old power strip in the basement I keep my Christmas ones plugged into all year, and since doing that have experienced no issues.

I recommend against getting a, "Smart," valve. Residential water shutoff ball valves have lifespans of over a century, and fully automated ones will require replacement every 10 years or so once they go out of support, Ethernet or not. If you do choose to install one, you should either install a bypass around it using traditional valves, so that a plumber can replace it without having to call for the water to be shut off at your buffalo box, or just install it after a main manual shut off for the same reason. FWIW, I went with the Zooz, and since I'm on a well I also kill power to the well pump at the same time, keeping any damage pretty limited even if the Zooz fails.

.ota, as stated in the post. I know that .otz and .gbl are supported, just asking if .ota is on the radar to be added.

Is adding support for .ota files for updating Z-Wave device firmware in the to-do list? I have several Leviton devices that use this format for updates, currently IoX just gives me a friendly not supported error message.

Yes, every time the On is sent, it restarts the program.

For A19 this may be true, but certainly GU10, BR20, PAR20L and PAR38 are almost unobtainable.

*If you can find them... They seem to be discontinuing them in favor of pushing people to Hue, but yes they were the best dimmable bulbs using normal dimmers. If you like them, make sure you buy enough spares to last a while (like I did). The Warm Glow are so good because they have two sets of LEDs inside of them, one that's a low power warm set, and another that's a higher power closer to daylight set, and some electronics to activate them with different ramp rates - being effectively two different power light bulbs in one package they can dim lower by using the warm LEDs, giving them the excellent response to dimming. Despite all that, Hue still dim better, but require an always-on circuit (Lutron does sell a Zigbee remote switch that installs over a normal toggle, at least).

At least as of a couple of days ago, it didn't actually update the OS, just said it would.

Following, because I haven't installed my eisy yet for similar reasons. Also because Polisy is still actually really good hardware.

IKEA FYRTUR and TREDANSEN blinds (I believe these are functionally identical): https://www.ikea.com/us/en/p/fyrtur-black-out-roller-blind-smart-wireless-battery-operated-gray-50417464/ https://www.ikea.com/us/en/p/tredansen-black-out-cellular-blind-smart-wireless-battery-operated-white-50512437/ Controls of full up, full down, and set percent up/down; feedback of blind level when adjusted manually at the blind, and battery level. Basically: control like a dimmer.

If you're on WiFi the AVR-X1200W sleeps the telnet connection over WiFi and because of a firmware bug needs a connection on one of its HTTP ports to keep it open consistently.

Sort of? I've tried HA several times, their rollback doesn't work well unless you're in a VM template. pfSense, which runs on FreeBSD like eisy and Polisy, have some other rollback features. Either way though, an unexpected restart from an update is going to cause me problems.

There's a hardware TPM it's expecting, I don't recall that Proxmox handles that well. Some versions of Hyper-V can virtualize the TPM transparently, ESXi not so much. Further up the stack, you'll also need the drivers for things like NICs and other hardware you're passing through that aren't in the repo. And at the end of all of this, I'm not sure what you gain ... failover requires so much extra hardware to handle the TPM (at least two clusters) that you'd be better off with a recent backup and a cold standby eisy.

If you want to give it a shot trying to run it in a VM, why don't you just ask them for permission?

I have a 5 gallon expansion tank, and still just remove power to the well pump rather than attempt to drain the system. It's not enough to make much of a difference once a leak is detected.

I have three, unsure of firmware revisions but the two I've re-joined as S2 as well as my remaining S0 leftover don't send status updates at all, and I haven't tried setting user codes yet. Currently, they're extremely buggy ... fortunately I'm WFH and they still work as coded door locks so I'm alright for the moment. Working with support on all of this, obviously.

Contact support, they need to send you some updated code.

Why not just use one of the calendar node servers? It can provide day of the week, week number, and all sorts of other nodes you can trigger on. Want something to fire on the second Tuesday of the Month because you like Microsoft? Pretty easy to do when you have that as a node.