Guy Lavoie

See my edit above, about using the ip address

5.8.4 is getting a bit old. Have you verified if your operating system meets the minimum version for upgrades? Look at the current release requirements, indicated in the second post above. If the version is ok, then you'll need to upgrade using a ssh session and the commands indicated earlier. For IoX finder, add a new entry with the ip address in it, such as https://192.168.0.123:8443/desc and try that.

You're good to go. The best way is still probably by doing it through admin console. Just do your backups and upgrade.

I do appreciate that we're given ample transition time. But it's very different and getting used to the new format will take time.

Making fun of features!

I haven't tried any of these new ones. My first zwave dongle was the Zooz 700 series, then I got a ZMatter dongle, which I still use. Someone else on the forum did get one of the newly supported dongles above. They are automatically detected, so there is no need for setup.

They're listed here: AeoTec Z-Stick 10 Pro – Dual protocol Zigbee/Z-Wave [ link ] Sonoff Z-Wave 800 Dongle Plus [ link ] Zooz 800 Z-Wave USB Stick [ link ] Zigbee Requires an external dongle (not included): AeoTec Z-Stick 10 Pro – Dual protocol Zigbee/Z-Wave [ link ] Sonoff Zigbee 3.0 USB Dongle Plus [ link ]

You only really need the admin password.

Yes. So go ahead and do the update, from the comnand line as explained earlier.

Yes, hardcode the ip address of your controller instead. For example: https://192.168.0.123:8443/WEB/sysconfig.txt

Hah, though that will often turn out to be the same!

Click on the three little dots to the right of the "Node" heading (your mouse pointer needs to be over the heading to see them). Choose "sort by ASC" (ascii order).

Will do. Thanks!

It's model 43095, I had posted a picture of it on page 4 of this thread, plus a link to some other information. I also displayed the DH cluster line that shows energy consumption. This model seems to be discontinued. I also have a GE branded one that seems to be the same internally. I have 9 of these, including one that's brand new in it's box. I'd be willing to give you that one (I'd send it to you) in order to have it supported in a future IoX release. Would that work? Thanks.

Hah, I'm far from "knowledgable" on this stuff, but google has given me many answers!

Yes, the Beecon supports RTS and Zigbee, while the Switch does both of those plus a newer protocol called IO

Existing shade controllers shouldn't be affected. My URTSII or existing remotes weren't affected. The general idea with RTS is that you push a button on an existing controller or remote, so that the gateway listens to the signal to learn the RTS address of that shade. Somfy remotes learn the same way. Setting up a new shade (ie: with no paired remote yet) is a bit more work because as you say, you need to access a tiny button on the shade itself. I suppose you could delete the app once you're done, but why? Just keep it on your phone for testing, adding new shades, etc.

Yes, the Switch (or Beecon) needs the TaHoma app to add the shades to the gateway device. You also need the app to generate the unique key that will give local access to the gateway, and that you need to eneter as a parameter when configuring the Somfy plugin. For your second question, Somfy says "up to 65 feet in optimal conditions", so I'd position the gateway as high and centrally (to your shades) as possible. Mine is on top of a disk cabinet that's near the center of the house. There are also RTS repeaters available.

I get a sense that it might get incorporated into UDI's support, possibly as a self-help screening process if you want to open a ticket. Not that I'm against the idea. Just something that seems to be in the queue. It could be useful for some of the usual questions that can be hard to search on the forum, such as "What updates are still supported on the Polisy?" or "What is the proper procedure to replace a Insteon PLM?".

Zwave LR is now supported, but you'll need to update IoX to 6.1 2, by enabling the staging repository in eisy-ui and upgrading.

@Michel Kohanim Just getting back to this (following the updated Zigbee processing in 6.1.1). Is the "energy cluster" that was implemented referring to: 1794 (0z0702)? If so, then the format of the Jasco must have something that's slightly different, since it's not showing up in admin console, even though DH Clusters for the device is showing a detailed output, and the last field does show the demand in real time if I refresh it.

Have you tried simply rebooting your eisy?

Ah yes, in that case do A new buzzword is born: eisy-ai clever!

UDI did signal last January that support for the Polisy would be in a maintenance mode, meaning that updates would continue as long as they were feasable, but if any new eisy features aren't possible on the Polisy for whatever reason (such as the operating system version) then so be it. Some people are still using their isy994i, so the Polisy probably still has a lot of life left in it, unless you want the absolute latest in performance.

A Polisy won't upgrade from a menu. You need to do it from the command line, using ssh. sudo pkg upgrade udx isy eisyui pg3x This is explained earlier in this thread.