Guy Lavoie

It's asking for your IoX login. That's usually admin... Try admin for both user and password.

Well wait a sec...what's not working with yours? Most of us here are happiily using our controllers. Not everything is perfect, but it does what it does well.

You need to click on "Plugins" at the top, and select "Launch Polyglot V3". You then get a login menu. Log in there, and you'll get the dashboard. Click on "Plugins Store" and you should see the list of plugins you can get. If that works, it's accessing the internet ok.

Is your eisy able to access the web, in general? If you go into the plugins menu, are you able to view the plugin store?

I know the 700 series stick is supported, and someone on the forum said that the 800 series also works.

That's also the kind of hypothesis that comes up in my mind. That's why I asked if the MAC address stays the same (though that question wasn't really answered). I just can't see the eisy itself causing this kind of issue. DHCP addresses are given out as a "lease", which expires and needs to get renewed. If the renewal comes from a different server, this kind of thing could happen at regular intervals.

So far so good. Programmed shade commands happening as they should.

Have you tried reserving a different address than your usual one for the eisy? Those dhcpdecline messages might be a hint that things aren't the way you think they are.

Well, open a ticket?

Ok, added debug, and can now see any issued commands in the log file. I also created a test program to close the two rarely used shades slightly in the morning, and then open them fully at suppertime, and verified that I can find the time stamped commands in the log ("cmd Shade Close", etc). This will tell me that the plugin is doing it's thing, as well as any see any random commands.

If you're ok with doing a ssh session into it, here are some instructions to wipe things clean: --- factory reset Polisy or eisy --- -- Stop IoX and PG3 sudo service isy stop sudo service pg3 stop -- Remove the entire IoX configuration (devices, programs, Z-Wave/Insteon data, certs, etc.) sudo rm -rf /usr/local/isy -- Remove all Polyglot / node server data sudo rm -rf /var/polyglot -- Remove portal credentials and association sudo rm -rf /var/polyglot -- Reset network settings back to default DHCP sudo rm -f /etc/wpa_supplicant.conf sudo rm -f /etc/network/interfaces

I had one incident this morning which may or may not be related to the plugin. The timing is just curious. The logs (downloaded log package) don't show anything, no commands issued. First a bit of background on my set up: My home controller is a eisy and I use the Somfy plugin to control a Somfy URTSI-II (through a device server) to control 4 RTS blinds. This is about a year old and I have never had any issues. I only ever really send commands to two blinds on a regular basis. The other two haven't ever really been used. Three days ago I installed the Tahoma plugin on a test Polisy that I have to try it out. This sends RTS commands through the TaHoma Beecon device. I picked up a used Beecon last fall for a really great price so I installed it to try it out, and figured that maybe someday it would be supported through a plugin. 🙂 So I have two different, separate systems that can send RTS commands, as well as handheld remotes for the two blinds that I do use. Well this morning I was surprised to find that the two blinds that I never use had closed, likely overnight. Just a data point for science.

As I've mentioned elsewhere, Matter seems to be more finicky with 6.0.5 than the earlier release that first supported Matter (6.0.0). One frustration is that I have not been able to add one Matter device on one of my test Polisys. I'm waiting for the next release before redoing my experimentation.

The "best" current method is to use a TaHoma device (Switch or Beecon) which works with the Somfy app and now allows local connections from third party apps...like IoX plugins! The Tahoma plugin is so recent that the paint is still wet!

Did Alexa put on a worried, scared voice?

I have a URTSI-II. I connect to it using a Lantronix EPS1 print server. I set up the EPS1 for a raw TCP connection to it's serial port. In fact I'm also using a EPS1 to connect to my Elk M1 with the Elk plugin. Years ago I picked up a dozen of these on ebay for $5 apiece. Lots of them on ebay even now. The plugin allows you to specify a IP address and port for TCP connections. For a EPS1, the serial port is port 3001. You could also use any other device server that offers a raw TCP connection. Most do.

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.