Guy Lavoie

I'm running the latest release (5.9 1) and the hostname shows up fine on my router, a eero 6. But there was an issue with the early release of 5.9 1. If you upgraded it in February and are only bringing this up now, go in Configuration and click on Update Packages, followed by any recommended reboot.

That's the correct format, though you might need to add the port number too. I just tested this on my own eisy http://admin:<password>@192.168.0.145:8080/rest/vars/set/2/2/2 It correctly changed state variable id 2

Are you able to turn the devices on and off from the Admin Console? Sounds like something is getting corrupted, or a device is becoming intermittent.

I had X10 for 25 years. Worked pretty well for such an simple technology. It was groundbreaking at the time. But I certainly don't miss the slow response (especially when doing multiple address commands, like A/1, A/2, A/3, A/ON) and the almost total lack of status tracking. How quickly we forget!

Hah, that's the dark side of a highly customized setup, using a mix of technologies (like Insteon and Hue). You end up with lots of scenes and programs! But it allows you to do things that wouldn't otherwise be possible. I do that kind of thing a bit at a time, testing everything as I go.

The announcement in January mentioned adding the plumbing for Homekit. I wouldn't call that "being tested" just yet.

Yes, one scene for each keypadlinc button that you want to update, and one program for each Hue light that you want to track. Programs would look something like this: aaa hue - [ID 009F][Parent 0001] If 'Hue / Hue-Lazyboy' Status > 50.0000% Then Set 'Scn KPL button' On Else Set 'Scn KPL button' Off You could also add more logic to the program, such as Or statements if one button controls a group of lights for example.

You're using the Hue plugin, right? You would need to create a program that watches the status of the Hue light, and update the keypadlinc button's backlight. That's done by creating a scene with just the button as a responder, and have the program turn the scene on and off as needed. The Hue plugin does track the status of the light, even when it's controlled by the Hue app. There might be a slight delay but it does work.

Have you tried running the update from the Admin Console instead of from UDI Mobile?

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!