Guy Lavoie

Opening a support ticket is your best next move. You already tried the cold reboot.

Well that's it. As my post started, I tried this just for kicks, because it was easy. If the "generic zigbee device" means that you could theoretically send standard zigbee on/off,etc commands (if there is such a thing) and that you "filtered out" all commands that didn't pertain to blinds, then that would explain the specific commands seen at the bottom of the node screen. If something simple like an optional parameter to allow all generic zigbee commands to appear could be added, then it might be worthwhile. If it's not that straigtforward and this takes you down a rabbit hole, then don't bother. The plugin does what it's meant to do very well!

Did you get it working with UDI support?

Just for kicks today, I added a Zigbee device to the Somfy app (a simple on/off appliance module) just to see what would happen. The app sees it as a on/off device, and I can control it from the app. Then I did a rediscover in the plugin. It added three nodes: two "ZIGBEE" nodes, and a third one with the name I gave to the device in the Somfy app: "Light". Looks like this: The three new devices have the same controls, which are more numerous than the RTS shades. Here is the one for the "Light" device: It seems to be assuming that the device is a Zigbee shade. Pressing the buttons don't actually control the device in any way. Maybe there is additionnal information that would allow the plugin to identify it as a non-shade device, and allow simple on/off control. It would make an alternative to the ZMatter dongle for simple Zigbee device control. But don't waste time on it, this is beyond the scope of the plugin. Just thought you'd find this interesting.

That's really odd. I have a eisy and a Polisy, both with ZMatter dongles, working fine on 6.0.5

To my knowledge there is only one Somfy app, supporting both the Beecon and the Switch (like UDM supporting both Polisy and eisy), so getting the token is the same procedure. You might want to add the Somfy app menu path and procedure to generate the token to your instructions. The one or two arrows thing seems standard for controls that have child nodes. Hue plugin does that too. There might be a way for UDMobile to improve that. I'll check which version I have tomorrow.

Well I had a bit of time so I installed the shiny new plugin on one of my test Polisys and set it up. Verdict: it works great with the Beecon! 🙂 I did have to configure the gateway-ip parameter, which took a bit of searching on my eero router device table. For those searching for it, it appears as "gateway-XXXX-XXXX-XXXX" (the unit's PIN number). The first tahoma-token I generated failed, the second one worked. Maybe the first one timed out between the time it was generated and when I used it. Restarting the nodeserver had it find my 4 RTS blinds, names and all. Restarting admin console made the controls appear. Resync UDMobile and I was in business. 🙂 Only minor quibble is that UDMobile shows the devices as a light bulb by default. I set a custom icon to be a roller shade. Cool!! The Tahoma app also supports generic Zigbee devices. In fact that's one of the differences beween the TaHoma Beecon and the Switch: the Beecon supports RTS and Zigbee, while the Switch also supports something called IO. The Beecon is sometimes also called the Smart Gateway. I might try adding a generic Zigbee bulb to it in the next few days and see how the Tahoma app sees it, and then the plugin. Thanks for creating this!

It sounds like this would be more of an issue with the router. Especially since you configured a reserved DHCP address. When you look in your router's connected devices, does the eisy's MAC address stay the same, even when the IP address changes?

The release notes advise against upgrading from below 5.9.1. I guess they make the upgrade process actually check that. You'll have to open a ticket for this.

Neat stuff! I actually have the previous TaHoma hub, the Beecon. I wonder if the software functionality is the same? I'll probably give it a try. I'm currently using a UTRSI-II with the Somfy plugin and it has been very reliable, so there is no urgency, but it's always interesting to try new things.

Did you just reboot the eisy or did you power it off and back on? If you didn't power cycle it, try that.

I have a keypadlinc that controls a ceiling fan (sends commands to a Fanlinc) that wasn't fully functional lately. But the funny thing, that prompted me to write this post, is that the backlight was blinking in sync with any Insteon signals being sent in the house! Literally, like a signal presence indicator. This afternoon I finally got around to fixing it, by doing a factory reset and then a device restore. That got it back to full functionality, and no more blinking. Anyone ever see this?

Wow, nice! First time I hear of a direct add. You're running IoX 6.0.5?

I also seemed to have more success when Matter support first came out in spring 2025. It's almost as if 6.0.5 somehow made it more capricious. Just a thought, not backed up by anything technical.

Yes, the Coffee Shop forum is where others list devices for sale.

I've also had mixed success with Matter (eisy is running 6.0.5). I've only been experimenting with Matter, not implementing anything for regular use. I bought a used Google home mini, and I first add the device to Google home, then share it to the eisy. I've currently set my experiments aside, waiting for the next IoX update before resuming tests. UDI is actively working on Matter implementation and it will take some time.

Ah there you go, if the creator is involved, then this should get figured out quickly enough.

Ah, I missed your mention that you had created a new, test program. I then thought I'd check out exactly what this plugin does and thought I'd test it, but it's the first time I see a plugin with no free trial period. In reading up on it, it seems to be doing several things that I've been doing myself as I learn plugin development, though mine is mostly about dates up until now. You might try contacting the developer directly.

Have you tried powering off the isy994i, taking out the SD card and cleaning the contacts, then try it again? There is a known issue with that which can sometimes help with reliability issues.

If you reinstalled the plugin from scratch (vs an upgrade) then nodes can get created with different references. Have you tried editing each program line by clicking on it and then re-selecting the same options from the select list? Do that for each program line referencing a value from the plugin, save it, and test it again.

If not, there is an alternate way of doing this using a couple of programs, without requiring a plugin.

Before deleting and adding back the modules (and redoing their references in programs), if you have spare modules of the same type, try this: add a spare device as a new temporary device. Then bring up your unresponsive device in admin console, and use the "replace with" function to replace it with the new spare device. This "holds" it's programming and references in the spare device. Now feel free to factory reset or whatever you want to do to the unresponsive device to get it working. If you succeed, then use the "replace with" function again to replace the spare device with the original, now working device.

A single bad device jamming an entire communication system is a rare, worst case scenario. It happens just once in every home automation enthusiast's lifetime to teach him that anything is possible and take nothing for granted. Hehe. Brings back some X10 memories.

Interesting. How did you determine that it was that one?

Rebooting the eisy will usually kill the linking process. You say you tried that, unsuccessfully. You'll likely have to wait for UDI support to respond.