Guy Lavoie

Well in my case, they devices get automatically added, something that the UDI skill seems to do for me. He should first check that the device appears in the Alexa app. It must, because he wouldn't get a "not responding" reply if it didn't exist. Instead it would be about there being no such device.

Do you have any other Alexa devices set up as scenes? If yes, are they working? Post a picture of the Alexa scene device (as seen in the portal) here.

Let us know how it goes.

The Zwave backup option only appears if you're using the ZMatter dongle. It's not there if you have the Zooz stick. In that case it's "probably" included in the general IoX backup, but I cannot tell you that for a fact. If you're really paranoid (join my club!) about losing data or ending up with a blue brick, you can backup absolutely everything by doing a full unix backup to a USB stick, if you're comfortable with using ssh to log into your controller and keying in shell commands. I have detailed this in a forum thread that you can read below. Note that recovering with a eisy is somewhat easier because you can attach a keyboard and screen to it, and do a restore from a console screen, while if a Polisy loses network connectivity, you're quickly down to reflashing the SSD. Either way, you can then restore the full backup.

That's right, it's upgradeable from that version. Just be sure that if the upgrade runs into a fixable issue (at worse, needing to reflash the SDD) and that you need support, that you can live without the Polisy. Ie: don't do upgrades on a Friday night

Do you have IoX 6.0.0 running on it?

Just a straight url, like this: http://192.168.0.123

eisy-ui also works on the Polisy.

Have you tried a factory reset and device restore on these togglincs?

Both the Polisy and the eisy have the same capabilities. They both run the same versions of IoX and freeBSD. The eisy will be a little bit faster, and it's projected support will probably last a bit farther into the future.

Hmm, I just upgraded my test controller from 6.0.0 to 6.0.3. Admin console works and shows the new version, but now I can't log into polyglot or eisy-ui. Browser simply says no response. even after a couple of controller reboots.

I'm referring to the portal, not Admin Console. When you defined the Alexa spoken in the portal, what did you click on at the top? "Device" or "Scene"? You need to click on Scene, and then select the scene from the list (you'll see scene names instead of device names)

The Zooz 700 series stick is supported. Not sure if the 800 is.

One useful function of an energy monitoring plug would be to know if a toggle powered device (eg: a TV with no discrete on/off infrared commands) is on or off, as part of a series of macros to set it to a desired state. The usefulness of this will be diminished if power drawing status isn't quick to update. In the case of the Yolink device, would the local hub be able to make this much faster? Or might there be a possible workaround by configuring it to trigger another Yolink device directly, which can then be monitored faster?

Did you set up Alexa to control a scene (and select the scene name) in the portal?

I gotta say, this new/alternate login thing wasn't handled as well as it could have been. It's goal is laudable, but automatically changing the default method (especially when the previous one is still available and valid) seems to be causing some frustration, especially with those who just upgrade when prompted and don't go over the release notes. It would have been better if a pop up message had offered the new capability, and then asked "do you want to change it?" Just a thought.

To use your usual login (admin) create a new entry in IoX finder with the 8443 port number. Example: https://192.168.0.123:8443/desc Then click on save. Use that to log in now.

Has the non local version also been updated?

That's right, it's view only for now.

Did you "Save" the new IoX finder entries? I save them to a file, so that I can load them if needed. After a few times, they seem to stick.

Do you notice if it's always the same inside lights that turn on, off and then back on? Have the motion sensor batteries been replaced recently? Maybe something to try.

For me, yes. But I've only installed the plugin a few,weeks ago, and been trying this with 6.0.0, so no idea if it would be different with an older version.

That's very similar to the issue I have with the vibration sensor. The select list shows options, but doesn't apply some of the choices.

Yes you can. Just create a manual entry in IoX finder (click on Add) and create a url with the 8443 port number, ex: https://192.168.0.123:8443/desc

I have two KPL buttons set up for doing just the about the same thing: indicating that one or more lights are on in an area (one is for the ground floor, the other for the basement). As @apostolakisl suggested, looking for the control event instead of status allows the status indication from the backlight to be independent of what happens when you press a button. As he also suggested, using a scene instead of a program allows everything to happen immediately instead of sending individual commands to each device. If you want to do something different with a press on than press off, then looking for the control event with a program is just as valid. The only thing is a slight delay between pressing the button and seeing your commands or scene happening. I do this because I want to use two different scenes, where one "off" scene turns everything off, and a different "on" scene that only turns on specific lights. I call that split scenes.