randyth

Thanks @Diesel . Seems to have worked brilliantly. Cheers

I can definitely feel it "click" when I depress it. And, as stated in my original post, I went so far as to take the cover off to ensure I was truly pressing the button in. This did not work any better. I agree with you that it seems like the button is busted since the Polisy is otherwise working perfectly. I was not confident enough to probe the circuit board to try to short the switch pins myself. So, I still wonder... Is their any other way (via SSH, perhaps?) to clean my Polisy Pro of my credentials so it is "safe" to hand off to a stranger?

The LEDs do nothing (well, the left-most one simply stays on) no matter how long I hold the button. The Polisy also does not reboot when the button is double clicked.

I have a Polisy Pro with the latest firmware that I'd like to prep for possible resale or gifting. My instinct is to perform a factory reset before handing it off. However... No matter how many times I try, the Polisy Pro does not react to the "Multi Function Button" as described in the online user manual. I can hold the button in for minutes. Even just double-clicking the button to safely reboot the device does nothing (though I've had this work in the distant past). I also took the cover off to ensure I was truly pressing the button in . This did not work any better. Is their any other way (via SSH, perhaps?) to clean my Polisy Pro of my credentials so it is "safe" to hand off to a stranger? Thanks, -Randy

Virtual Buttons aren't really switches or "toggles" -- they are push buttons. Technically, Alexa sees them as Doorbell Buttons which trigger Alexa Routines when pushed. Currently, Amazon does not let you trigger Alexa Routines with switches. If they ever do allow such things, we would be happy to offer Virtual Switches that trigger Alexa Routines based on their on/off state. Personally, I'm hoping they simply add a "Toggle Action" to Routines. This way, for example, you could toggle a light on/off with one Virtual Button. Unfortunately, this is not a feature we can add for them.

To add detail to Javi's comment, here is an example of a program that turns on lights at 6am and then off at 8am: If From 6:00:00AM To 8:00:00AM (same day) Then Set 'Ambient Lights' On Else Set 'Ambient Lights' Off

Initially, I had the same results as @TUhl01 and @glarsen. Then on a whim I logged out of PG3x and am now having the same issue as @Techman.

Ditto. Caught this pest on my back deck recently:

Assuming you moved from an ISY994, I suspect your portal account is still trying to talk to this old hardware. If that is the issue, you should log into the portal, select the Add ISY button to add your Polisy, and then add all the devices you want exposed to Alexa to it (Polisy->Select tool->Connectivity->Amazon Echo). Better/more complete instructions can be found here: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Migrate_configurations_to_a_new_ISY

Just a guess, but I think this update is only available (or useful) for people with the new eisy device.

I suspect that program always sets the RainDelay variable to 0 because every time the Then statement decrements the value it re-triggers the program (it starts back at the If). I think you are going to have to change RainDelay to a regular (Integer) variable to prevent the If block from re-triggering.

Ditto. I did the same -- definitely easier for me this way.

The updated version of PG3 does not like to talk to ISY on any port other than 8080, so it fails to launch. You should probably open a ticket with UDI to get instructions on how to reset your ISY port settings. Or, if you are adventurous, you can try this... sudo rm /var/isy/FILES/CONF/0.UCF Be warned, however, that this will clear your ISY's credentials, time zone, and SMTP settings along with resetting the port.

Is this on Polisy and, if yes, did you change the port number of ISY on Polisy to be something other than 8080?

Ordered!