Guy Lavoie

Ok, let me try that and a few more things. Thanks!

Mine are Enbrighten (Jasco) ZB4103 (as indicated in the Zigbee thread). They are the ones that generated the cluster information I sent you in March. I also have a GE branded one (ZB4101) that seems to also be a rebranded Jasco.

Yes, and also tried adding two other modules that had never been added before. Same result.

Hmm, it's not. I only get on/off control.

So it won't work with the ZMatter dongle?

Speaking of Zigbee libraries, that reminds me of something I brought up a back in March. I have some Zigbee modules that measure power consumption. You had me capture cluster information, and you had ordered a module with the same functionality, for the purposes of implementing the retrieval of the power consumption value. It's a standard cluster in Zigbee 3.0. So I just gave that a try, first doing a re-interview of the module, then an actual delete and add. There is no new information appearing for the module, though it turns on and off just fine. Should this be working? I'm doing this with the ZMatter module.

Or better yet, not have it overlap the program area when it opens by default. Another minor quibble: When adding or editing a line with a variable, the default radio button selects integer variables. Could that default be changed to state variables instead? I think most of us program using state variables much more often than integer. Another thing is the variable name list being centered: it would be easier to read if it was left justified.

Another minor obervation: the release announcement mentions backup and restore of zwave dongles. Just for fun I looked this up on my upgraded test Polisy that has a Zooz 700 series dongle. The dongle works, but the zwave menu hasn't added backup and restore options. Maybe it's a limitation of the dongle itself. If anyone reading this has a 800 series dongle on a 6.1.1 system, have backup and restore options appeared?

Yes, the black background isn't pleasant. Having color settings would be nice.

Bingo, exactly what I needed to know! Added to my (ever growing) notes!

@Michel Kohanim Thanks. That brings up another question: if an update did in fact really mess things up and it's bad enough that eisy-ui can't be accessed, how could we manually switch to the inactive boot environment from the command line (by hooking up a screen and keyboard)?

Ok, but is the general idea that after you confirm that the new one has working fine for a while, you can delete the inactive one? Will a new update further down the line then made the current one an inactive one, offering a recovery path again? It's a great feature, making updates less do or die.

@xlurkr Try the manual update, as suggested by @Michel Kohanim himself (a couple of posts up). Worked for me. Join the geriatric Polisy club 😄

Well hey, I just tried exactly that, and it upgraded fine! Thanks for the honest reply. Yes, it's a bit slower but as a testing device, that's small price to pay for the versatility I get from having these test units. I'm quite active on the forum and many of my posts begin with "I tried this on one of my test Polisys..." It both helps the community, and pushes me to try and learn new things. I have three Polisys that I obtained as used units for a very low cost or free. For sure, a test eisy would be nice, but it's prohibitively expensive here in Canada. I even got my own eisy as a used unit, and used eisys come up rather rarely. A slower but otherwise functional Polisy makes for a good compromise and a handy test device. Thanks for the workaround. 😊

That does not appear to be supported yet.

Oops its: uname -a

The raw method is to ssh into it and do: umame -a Otherwise it should appear in the sysconfig.txt file that is accessible as shown in the release announcement

That program editor is going to take some getting used to...

you ssh into it and watch the log file as it grows: tail -f /var/udx/logs/debug.log This is handy for observing the progress of upgrades as they happen.

Looks like the Polisy won't getting this update. I just thought I'd try it on one of my test units and the upgrade log file says: Upgrade failed: field upgrading of non-eisy devices no longer available ...

Basically, don't do this from any type of remote access. Do the upgrade from Admin Console, on a computer that's in the same physical location and on the local network, such that you can restart the eisy by power cycling if necessary. This avoids any issues that could be dependant on remote access authentication, etc.

Paranoia is an asset in software development 😄

That release announcement sure caught my attention! Let's discuss it, and indicate how our own upgrades went. I haven't taken the plunge yet myself. Looks like this is the version where eisy-ui becomes fully functional. The release notes raise several questions that come to mind: It starts with "We're happy to announce the availability of OS14.4, IoX 6.1.1, UDX 5.0, and eisy-ui 1.2.0 for eisy (only)". Does this mean that the whole upgrade is for the eisy only, or just eisy-ui? Farther down it does mention that you need to be local to your eisy/Polisy, so I'm wondering if the Polisy is supporting this upgrade. There is a link showing the supported Zwave and Zigbee dongles. The ZMatter dongle isn't listed, but I'm hoping that's just an omission. Similarly, is the Zooz 700 series dongle still supported?

I just added a feature suggestion: https://forum.universal-devices.com/topic/46913-suggested-ud-mobile-feature-numeric-keypad/

As another poster was looking for, a handy feature would be a generic numeric keypad. Digits 0 to 9, Clear and Enter. This could then be associated to a selected variable, and with configurable low and high limit values. The variable could then be used in programs as a pin, temperature setting, etc. Anything you like.