Guy Lavoie

I haven't experienced it myself, but the announcement for support of the new dongles said they were automatically detected.

That last step shouldn't be necessary. It was only to revert to the original Zooz dongle. The newer IoX versions are supposed to automatically detect the newer dongles.

Actually, Paul's post reminds me of an interesting thing that happened in one of my keypadlincs a number of months ago: it's backlight would blink in sync with any Insteon powerline signals. I posted about it a the time. A factory reset and device restore fixed it, and it's been fine ever since.

The Usual way is to go in admin console (not eisy-ui) ,click on Configuration, and see if there is a button offering you to migrate to the ZMatter dongle. If there is, then you're set up for zooz dongle. If not, the do the browser command I posted earlier, reboot, and check again.

If you can see the circuit trace it goes to.

Did you reboot your controller?

I'd do a restore device on it.

Maybe cut the push on connector and solder the wire to the board?

issue the following url with a browser, which should roll back the switch to ZMatter: http://<your_IP_address>:8080/rest/zmatter/zwave/deactivateZMatterZWave

Did you power off the eisy before replacing the PLM? It's important.

I don't know exactly which version I had but my first attempt at installing eisy-ai was also stuck at "starting", until I upgraded UDX to 5.2.0.

What version is your UDX at? If you upgraded it sometime yesterday (Friday) and it's at 5.3.0 or more, then that will need to be rolled back by UDI. Are your other plugins working? You're trying this on a eisy (not Polisy) right?

Well the main feature of 5.3.0 was updating the version of Python, something that UDI had been intending to do. There was also a minor update to the FreeBSD version. I imagine that they'll rework the Pythin update and submit it as another update soon.

There is discussion about eisy-ai within the focus group that was set up for the beta trial. The invitation to join was sent out a couple of months ago, you must have missed it. There is nothing wrong with starting a thread on it here too if you want. Tu run, you need to be running some releases from the staging repository, so it comes with risks. It looks very promising so far!

It's because there was a 5.3.0 that didn't work, and a 5.3.0_1 that attempted to fix it. Plugins wouldn't start. So rolled back.

Had you rebooted your controller before you noticed this. A reboot will sometimes cause this kind of thing.

No, with the version you're now at, upgrades from the menu in eisy-ui should work. Not sure why it's not working for you. You could try the ssh method anyway, maybe you'll see why it's failing.

That's right, if you don't upgrade that Polisy and leave it as it is, admin console will keep working as it always has.

That answers my own interrogation. Thanks.

I'm also not quite sure what you're looking for. An example of how an actual one is set up? I'm using an IOLinc for this, which I plan on replacing with a Shelly ZWave LR module (to avoid a door opening from a Insteon All On). I'm using the IOLinc's input to detect that the door is closed. I'll probably replace the input side with another Shelly input device. They have one with two inputs, which would allow a more reliable detection of both open and closed, instead of just closed/not closed. I had also created custom icons that I would have liked to include in UD Mobile if/when custom icons become possible. My whole garage door program folder has 14 programs, to account for staus update of keypadlinc buttons for when the door is operated manually.

Right click on the node name and select "Configuration". You'll find those settings there.

In fact I do have eisy-ai, and happen to have updated it to 2.2.3 just yesterday afternoon. So I tried the backup again this morning and it worked 🙂 Thanks for the heads up!

I noticed this error 500 a couple of days ago, with eisy=ui 1.4.8. I just upgraded to 1.4.9 this morning and it's still happening.

Anyone who knows my former life will remember my involvment with Applied Digital and the Ocelot/Leopard controllers. The controller is outdated, but the expansion modules and IR capabilities are still useful, and my Ocelot hasn't missed a beat in the 26 years I've had it. If you're still using it, chances are you're triggering routines with slow and unreliable X10 commands from your eisy. Well I've been working on a plugin for it, using eisy-ai and it's almost fully functional. If there is community interest in it, I'd polish it up and make it available as a plugin. It would be free. I also need to make sure I understand the code well enough to properly support it. So let me know!

I guess I've never noticed (or used) these options. I have 5 lamplincs and I'm seeing the same thing you are, with no Options button.