xlurkr

Yes. btw, I just excluded and readded, and there's no change. Except the Z-Wave device number incremented to 4, of course. -Tom And I have restarted IoX several times. I haven't power cycled yet, but I can't imagine that would help. -Tom

My Zen30 isn't working right. It was, before I migrated to ZMatter. It used to have controls on the "XXX.1 Binary Switch" node. Since I excluded it, migrated, and reincluded it, the controls are in the "XXX Binary Switch" node, as shown in the first image, and there are no controls in in the "XXX.1 Binary Switch" node, as shown in the second image. I wouldn't care, except the controls don't actually change the state of the switch - nor do they reflect any change made locally. Does anyone here have this device in a ZMatter setup so you could look at your nodes and see if they match mine? Any other advice would be appreciated, too. -Tom

Wow, I love this board. I just readded my lock, and the writing badge (icon) appeared and never went away. I also had no control. I did the three-step compatibility, validation, rewrite documented above and now I can control the lock, and the writing badge is gone. Thanks to @kandlg for the tip! Before, I had a lot of other nodes, but I still now only have the one. Am I to understand that I'm going to have less functionality now? More details: I just migrated from ZMatter to ZMatter. What does that mean? This Polisy originally had a Zooz dongle, and I switched to ZMatter (internal version) shortly after its release. Then I added the lock, for the first time. At the time, there was no "migration"; eventually, a "migrate to ZMatter" button showed up in the configuration. The guidance was that one would have to reestablish the Z-Wave network, but I now think that was only true if you were literally changing radios, as opposed to (in my case) just telling the system that the Z-Wave radio is a ZMatter one. Maybe I should have just migrated without excluding my devices. Regardless, I am where I am because I excluded the lock, migrated to ZMatter, and am now readding the lock. -Tom

Polisy is so....interesting. This morning, after letting it sit overnight doing an "upgrade" (no beeps, no AC disconnect, no flashing LEDs) I checked the status. Still 13.1. I rebooted, and when it came back I launched yet another upgrade attempt. This time, it worked. Beeped, AC disconnect, and LEDs started flashing. About 30 minutes later, it was done. 14.1. Why? I dunno. I've sincerely lost track of how many upgrade attempts, reboots, and power cycles I did. I'm left with the conclusion that with a Polisy, you may need to let it sit for a while, then reboot. Again. And again. Until you succeed. -Tom

I should add that I pulled this unit out of storage, and it was on 13.1. It "upgraded" to 13.2, or so it said, with beeps and LEDs and all, and then the next time I pushed the upgrade packages button, it said it was going to upgrade from 13001 to 13002. I thought that was odd, but went ahead with it anyway. It currently says it's at 13.1 - still. -Tom

I've been attempting to upgrade one of my Polisy units - the one not in active service - for a few hours now. I'm not making any progress, but I'm seeing similar symptoms described above. I've clicked the upgrade packages button, rebooted, power cycled, etc. I don't know how many times. It sometimes comes back with that bogus UUID but never gives me a message in the upgrade that it's going to install 14. anything - just a generic message about 4 beeps. No beeps, no flashing LEDs, and the AC does not subsequently disconnect. I guess it's ticket time, unless someone has advice for me. -Tom

Did you have a reservation in your router prior to the upgrade? If so, that's unexpected, and something I'll want to look out for when I upgrade soon. -Tom

To elaborate, one switch will control the load directly via its load line. If that switch is a dimmer you can dim. And in that case, any switch that's part of the N-way will also be able to dim the load, whether it is a dimmer version or not. -Tom

Have any of you Zen32 owners had a problem with the big button's actuation? Mine often gets stuck in a depressed state - whether it sticks, or bounces back out, depends on where you tap it, how hard, and how fast. It was so unpredictable that my SO made me remove it. I replaced it with an Insteon relay, which works, but I lost the scene buttons and the Z-Wave repeating the Zen32 had provided. -Tom

Both plugins and portal subscription can be transferred. I've done it. So rest eisy -Tom

Helps me. I have an Omnipro, which uses "When" in its automation rules, and an Elk, which uses "Whenever". Both styles help me remember that nothing gets executed unless an event happens. -Tom

Would this work? I thought controllers for scenes are always responders too. Wouldn't this plan make the single manually switched-off light turn off all the lights that are controllers in the scene, and not just the virtual light? -Tom

Hmm. I don't have this Z-Wave backup option in my menus either. And I have an internal ZMatter board in my Polisy. -Tom

Is there a comparable procedure for Polisy? I'm not currently having a problem, but I'd like to know anyway just in case. -Tom

I personally think there's something peculiar about this model of the ApplianceLinc, maybe in conjunction with the current generation of PLMs. I had some recent experience setting up a new Insteon network with a mix of old and new devices. These old ApplianceLincs were the only devices that gave me any problems. Even plugged into the same outlet as the PLM, I got numerous repeated "can't determine Insteon engine" errors. My recollection is that I finally got them to connect using the "put into linking mode" method, but it took multiple attempts. The only reason I kept trying was because I wanted to have the passthrough outlet, but I would have been better off using an outlet splitter and a newer dual band ApplianceLinc. -Tom