Guy Lavoie

Yes, if you're referring to a sharing code. Matter devices usually come with QR and/or PIN codes. Currently the only way to add a Matter device to your eisy is with a QR code. Unfortunately, some sharing applications will only give you a PIN code. So use one that offers a QR code. The Hue app does this, as does the Google Home app. I can't remember if the Alexa app does too. The share code is created in the app and expires, sometimes as quickly as after just a couple of minutes. Another inconvenience is that the sharing QR code will often be displayed on your phone (almost everything today is managed with a phone app) and you also need to scan that QR code in UD Mobile...on your phone. So you either need two phones, or do what I did: use the phone's buttons to take a screen shot as a photo, email the picture to yourself, open the email on your PC screen, scan the QR code off the PC screen. All that before it expires!

The eisy isn't meant to be used with just UD Mobile. Some things need to be configured in IoX. In the Configuration settings (in IoX) you define the timezone you're in, and the controller will get the time automatically, from a time server. If you have no PC, then I figure you don't have a way of running IoX to set that up.

Well that nanoleaf bulbs use thread, and I've tested them successfully. Well Matter is over IPv6. Both ethernet and wifi are IP based so that isn't really a distinction, since the difference is at the physical and data link layers. The network layer is the same. Matter also implements IPv6 over Zigbee, which is what makes up the Thread communication option. This appears to be optimized for low power/battery device operation. The implementation of Matter for the UDI controllers seems to have somewhat stalled, or slowed down. It's still in Alpha testing. It looks like a few other projects (like Homekit implementation) might have been given a bit more priority for the time being. The current release of IoX is still 5.9.1_18, and has been since April. It would be nice to have an update from UDI.

The best way to do the actual flashing would be by putting all the lights you want to flash in a scene, and have the program turn the scene on and off. However be aware the communications will be busy after a scene command (at least with Insteon) due to the "cleanup" messages that follow between the PLM and the individual lights. I would start with a 3 second wait between scene on and off commands, and try to notice if the timing is reliable or not.

In the case of Insteon switches (and any other technology where the controller can track the status) you could create a program for each light to continually write it's status to a variable whenever the status changes. You would need to "And" the status change with a flag variable that would test false if the doorbell routine is triggered, in order to not memorize the status changes caused by the doorbell routine itself. Finally, a second program (per light) to set the light back to the last remembered status once the doorbell routine ends and the flag is cleared. Just a bunch of little programs.

Tried doing a restore from a backup?

I'm not sure the portal is needed for local network use of UD Mobile. I have a eisy with portal subscription and a Polisy without, and both devices are accessible when I'm at home, and only the eisy when I'm away.

Try factory reset as suggested by Paul. Also try manual linking, by going into (IoX): "Link Management" -> "Start Linking", then go press the link button on the device. Another thing: I've had that disappearing dialog box when trying to add a device. It turned out that...the device was already existing in my device list. it doesn't tell you that it already exists, the box just disappears.

What exactly do you mean by "local access"? IoX finder is not showing your controller? If so, try clicking on "Add" and writing the URL manually. For example, if your controller appears in your router's device list as 192.168.0.123, then the URL would likely be https:192.168.0.123:8443/desc

How about a simple test for the PLM: try manually linking a spare switch or module to the PLM, just using the link buttons on each device. Just to see if they can talk to each other, without the isy being involved.

He's logged in on the console (physical keyboard and hdmi monitor) so no network access is needed to log in and see this.

We love happy endings 😀 Good to know. So no automatic updates, but there were some unintended update errors caused by this.

Look at the file: /var/isy/FILES/WEB/sysconfig.txt Scroll down to the *****IoX******* heading and you'll see the version on the following line.

Since you can access it on the console, what happens if you try to reinitiate the acquisition of a ip address? Something like this: sudo dhclient -r re0 What error message do you get, if any?

What version of IoX were you running up until now? 5.9.1 or older? If older, any hints that an update might have happened? Tried just unplugging and reconnecting the network cable, or a different cable? Everything else in your local network is working as before?

Well, if the distance is too great for the technology desired (Insteon or zwave for example) but you have wifi or wired ethernet, you could set up a separate controller (like a ISY994i) and have your master controller, like a eisy, send commands to it using REST commands. That might be a useable solution if the number of devices to be controlled is small. Tracking status would be more difficult however.

If you can detect the double tap as an event in a program, then you could have two programs, something like this: If switch double-tap on event Then set motion detector parameter 1 to <enable> If switch double-tap off event Then set motion detector parameter 1 to <disable> I don't know these devices, so I can't tell you what is settable or not by program statements.

Which Insteon device has no link button?

The mystery here is that Insteon is working but not X10, and (seemingly) only X10 transmission with the eisy. It's as if the PLM was unable to transmit X10. Yet another PLM was tried with the same results. The hardware connections like the PLM cable seem ok since Insteon works. The next thing I'd try is moving the PLM to an outlet on a different circuit, and maybe on the alternate phase. It sounds like there is a X10 signal issue, at least in some area of the house. Alternately, try a X10 transmitting device (like a transceiver) in the same outlet as the PLM. Is that device now having trouble transmitting? Has anything been added that might be a "signal sucker"? We add and move so many electronic items nowadays that this might be hard to really be aware of.

Have you tested to see if your eisy can receive X10 signals? Do you have programs triggered, or variables set by received X10?

If I'm not mistaken, after a while it will also disappear on it's own.

It's in nostalgia mode. Have you tried highlighting the line and clicking on "delete"?

Yes, the X10 module was mostly a convenience, allowing you to add X10 devices to your device list. It would still be handy to a user who is looking to replace a defective unit and recover from a backup, without needing to edit all the programs.

If it doesn't already have the X10 module, you can't add it anymore. If you want to stick to a ISY994i, you'll need to find a used one that already has any modules you want.

Oh the (X10) memories! One thing I had acquired at the time was the Elk ESM1 signal meter. It turned out to be handy for this kind of thing. I sold off a bunch of X10 stuff but I hung on to that meter, because the bar graph shows signal strength of anything around the 120 kHz frequency, which is close enough to Insteon powerline signals. It helps me see any residual noise, as well as Insteon transmissions.