Guy Lavoie

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.

Yes, that clunkly way is the workaround that comes to mind.

For that, I'd either create an icon that runs a program, or create a switch with the Virtual plugin, which then runs a program that then sends the desired commands to the alarm system.

That's a good idea, but a backup like the one we do in Admin Console would also be great to automate, something like do one automatically when logging into Admin Console if the previous one is more than so many days or weeks old.

So these are strictly internal changes, right?

90% of the answer is from the buyer. If it's a techie, they might be delighted. If they shun technology, it could be a support nightmare.

Join the ranks, we're recruiting!

Well if you know me well, I get everything used! Ebay, marketplace...UDI coffee shop 😆 etc. I originally got my URTSII literally for free, and the Tahoma Beecon for a low price. @sjenkins , did you update your docs to indicate that your plugin workes with both the Tahoma switch and the Beecon?

Yup, just installed the update. It's been working reliably, installed on one of my test Polisys. I have two shades that I lower partially during the day, every day, with this. My main (eisy) controller is still using the original Somfy plugin, which works with the URTSII device, for now. One handy feature of the Somfy plugin has is that you can define a travel time parameter (in PG3 configuration and/or as a program command) for each shade, which is the time it takes (in seconds) for a shade for a fully open or close. Then you can send commands to open or close by a certain percentage, which will activate it for the percentage of the time of a full travel. This could be a nice feature to add to the Tahoma plugin. If Time is Sunset - 45 minutes And $s_shade_close_early is not 1 Then Set 'Somfy Controller / Shade_02_Shade_bedroom' Set Travel Time 20 seconds Set 'Somfy Controller / Shade_02_Shade_bedroom' Open 15% $s_Shade_bedroom = -1 Else - No Actions - (To add one, press 'Action')

Well, there's still the ole workaround of wiring a dry contact unit like a IOlinc across the button contacts of a physical remote.

Technically, the ISY994i isn't supported anymore, but you could still try opening a ticket and just ask if they have a copy of the version you'd need for this. The worst that can happen is that they don't. Costs nothing to ask.

Ah yes, my mistake! I see ten zwave questions for one zigbee. Sorry, dementia must be setting in... Zigbee devices will usually have a factory reset procedure. Did you also try bringing it close to the dongle for adding it?

A Zwave exclude doesn't need to have the device existing on your controller. You go into the zwave menu -> exclude device and then press the button or whatever on your device (usually the same as adding a device). That clears any links it has to a controller. Then try the add process again.

Try doing an exclude on the new device, then adding it.

I'd like to add something else here, potentially useful in certain programming situations. My phrase "Integer variables won't do anything in If/And/Or statements" isn't quite true: integer variables can be tested in If/And/Or statements, but they won't trigger the program if they're what end up making the program true, They're useful as static conditions that you might want to be true for other triggering conditions that you want to test for. An example: you might want to test that an alarm system is in armed status to allow some triggering actions, like motion detection to trigger an action. But you might not want that action triggered if motion was already detected and you're now just arming the system. By setting the armed status into an integer variable, you can avoid that second condition from happening.