Guy Lavoie

Insteon works in strange and wonderful ways... No idea really, but the first thing I would have tried would have been to "Restore Device" on the affected switches. This rewrites the links to them, without losing the references in programs and scenes.

The various suggestions are all valid. The approach you use will be based on how practical it is. I have a 6 button keypadlinc near the door we always go out through. Two of the 4 center buttons indicate if any light on that floor is on, including lamps, etc. For those, I have a scene that has nothing but a single responder (the button light) and two programs, one that look for any light being on to turn on the backlight, the other that looks for all lights being off to turn off the backlight. Any additions or changes to the lights I want to monitor are then done in the programs. Easier than tracking many links. In other cases, it's conventional scenes linking back to the button backlights.

If you have spare Z-wave plug in modules, have you tried adding a few, to try and re-jig the network?

Rereading your post caught my eye at the above quote. Both Z-Wave and wifi thermostats aren't getting updated? Now that would appear to be more of a program execution issue. The fact that it started after an upgrade to 5.9.1 is also suspect. I'd add test code, such as incrementing a variable in the same program, just to see that it's going through the statements. One before and one after. Something like this: Then increment variable 1 Then set Z-wave termistat Then set wifi thermostat Then increment variable 2 And check it every day to keep track of the variable values (or write them down along with the date).

How long have you had the "relatively new" UPS's? Just one of those things that can create electrical noise issues. Have you tried eliminating them, for test purposes? If your problem occurs frequently enough, you should have a quick enough conclusion as to it they're a problem or not.

Interesting. setDim isn't mentioned anywhere in the wiki on the REST commands. Funny thing is that the "cmd/DON/128" format works fine with Insteon switches. I'll try that tomorrow, thanks!

Well it at least enables IPv6, because it's needed for Matter. But always has an IPv4 address too.

I love this plugin, very handy for several things. Now I'm trying to use it to set a touch lamp to one of 3 levels by program statements that look at a virtual dimmer level setting. Works great if I manually set the virtual dimmer level in admin console. But if I set the level through a REST command (eg: http://admin:<passwd>@192.168.0.xx:8080/rest/nodes/n006_90/cmd/DON/128) nothing happens. Turns on and off through REST ok, but setting level doesn't. Any ideas? Thanks!

A hub or border router is needed for Thread devices. No need if your device is wifi or wired ethernet. I'm confident that eisy will eventually be able to communicate with Thread devices using the ZMatter dongle (Thread uses Zigbee for it's physical layer). Not sure I understand your "Aidot only" sharing. The very idea of Matter is being able to share devices across platforms. You bluetooth error message seems to imply a communication problem with the device. You really need to unpair it from any other system (Aidot) if it's already commissioned there and you can't share it. A factory reset is often how you can do that.

Looks like it's ticket time.

Did an update occur? What version of IoX were you running yesterday? the first screen shows something about not starting "since we just upgraded". Have you tried the start button options? https://wiki.universal-devices.com/Eisy:User_Guide#Multi_Function_Button You could try the 4 time button press to reset networking. Whatever you do, don't do a factory reset, at least not before you've opened a ticket with UDI to try and recover it first.

Have you tried simple things, like reseating your network cable? A different port on your router? Or a different cable?

Does the Aidot app offer you Matter sharing codes? Otherwise, you'd need to try a different device. I only tried a GE Cync bulb with Matter over wifi.

Do you know for a fact if IPv6 is working on your network. It's the only other thing that comes to mind. Also, do you have Google Home? If so then try adding the plug to that, and then getting a sharing code from the Google Home app (and try scanning it in UD Mobile).

Nice, though doing a factory reset on a in-use controller is never fun. Welcome to Z-wave!

Also, you mention getting it in 2022 at the time when you got the Polisy. There is a thread in this forum section about an update from Zooz for that stick. Maybe that could make a difference.

And you're certain your Zooz stick is a 700 series?

Oops, I made a mistake in my post above. If you see an option button for "Migrate to ZMatter Z-wave" in the config screen like the one below, then you're set up to use the Zooz stick. If your config screen looks like the one in Techman's post, then you're set up to use the ZMatter dongle. If you are indeed set up for ZMatter and want to change it back for Zooz, then do this: From a browser, go to the following URL: http://<your_IP_address>:8080/rest/zmatter/zwave/deactivateZMatterZWave

I have the Zooz 700 stick on my eisy, running 5.9.1. Works fine. If your config screen is showing a check box to enable Zigbee, then you need to "roll back" the Zwave configuration from Zmatter in order to use the Zooz stick.

Well, this is an added functionality, so no real impact on existing systems. Add to that the fact that the eisy is very much a techie oriented device, and even more for forum participants. Several of us are more than happy to jump in and learn Matter at the same time.

That's a question that comes up now and then. I don't have an official answer but my theory on it is that yes, messages would be passed on. Contrary to Zwave and other networks where devices are "included" into the network, Insteon is based on direct links between devices that need to talk to each other. There are no required links to intermediate devices to create the mesh network. It is a well known practice to use lamplincs to help powerline only modules like the iolinc with reliability, even though you don't need to set up any links to the lamplinc itself. Even Insteon (the company) mentions doing that as a workaround in their recent webinar.

One little hiccup I've come across: yesterday the wifi bulb (Cync) stopped responding to commands from the Admin Console, but was still working ok from the Google Home app (from which I shared it). Same thing today. So I deleted it and redid the share from Google Home. Let's see if it lasts longer this time. The Matter sharing codes are only valid for a short period: 15 minutes with the Hue app, 15 minutes with Alexa app...and only 3 minutes with Google Home. Because I'm emailing myself a screenshot of the code to scan it, this is kind of tight. Google should loosen up a bit.

That problem comes up every now and then. It seems no one has created a zwave extender that could work over ethernet, or something similar. It would be handy as a distance bridge, with one module at each end that could convert zwave to ethernet and vice versa. Assuming you have wired ethernet across that gap, you'd need a eisy at each end, or even find an older isy994i that has a zwave board in it, that you could then control via REST commands from your in-house eisy.

You can't have two Zwave adapters or networks on a single eisy. What would be the advantage of having a separate Zwave network for the garage?