randyth

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!

I have a Smoke Bridge and successfully use the Status is On method. Smoke Alarm - [ID 0058][Parent 004A] If 'Alarms and Locks / Smoke Bridge-Smoke' Status is On Then Send Notification to 'myself' content 'Alarm Alert' Else - No Actions - (To add one, press 'Action') As you can see, I do not force a query because the alarm appears to clear itself after awhile (likely when the smoke alarm stops). @CPrince, have you verified that your Send Notification action is working by right clicking on the program in the AC and choosing Run Then?

Ah, good to know. It has been so long since I did this I couldn't remember the exact details. Glad you figured it out!

There is a way to "fix" this in the Administration Console: Right click on the node created by the Virtual NS and select Delete. Go to the menu Node Server->Virtual->Add Node and add the node back in. You should now be able to use ISY Portal->Connectivity->Amazon Echo to add this node to Alexa. NOTE: Step #2 can be tricky because you have to know the node's address and primary node address. To find this information, open PG3 and go to Dashboard->Virtual->Details->Nodes. There might be an easier way to do this, but not one I am aware of.

Those variables were set up as either Motion Sensors or Contact Sensors in the Portal. In any case, I'm sure Michel is correct that you just need to wait a while for the logjam to clear.

I've never found motion or door sensors a reliable way to trigger Alexa Routines. For this reason, I've relied on skills such as Voice Monkey or Virtual Buttons which use "doorbell" events to get Alexa to react.

Unsure. I got burned by that and the PGC Ring node server has never fully recovered for me since. I'm afraid you'll have to open a ticket with UDI to resolve this.

You might be interested in this thread: First thing to try is check to see if you set a "preferred ISY" in your Portal settings and, if so, make it point to your Polisy. If that doesn't do the trick, you'll have to enter a ticket to possibly get your Portal account reset.

In case anyone is wondering, it appears my issues were largely caused by deleting my old 994i ISY from the Portal without also going to the Portal's My Profile menu and changing the "My preferred ISY" option to specify the Polisy that took the 994i's place. (I had completely forgotten there was a "preferred ISY" option.) Doing the above made both PGC and the PGC Ring NS mad, even though the Ring NS was already pointing to and working with my Polisy (all node servers were removed from my 994i before I unplugged it). So now you know. Don't you feel better? I do.

Is Polyglot Cloud (PGC) still having problems? Trying to go to the PGC Dashboard results in a never-ending loading screen for me.

I vote do it in a program. I don't believe scenes were designed for such logic.

I think you are having trouble because you skipped the "SSL Error 'ee key too small'" step mentioned above. So, please try following these instructions and see if that helps: https://github.com/UniversalDevicesInc/polyglot-v2#ssl-error-ee-key-too-small

Yay! Glad I could help. @Michel Kohanim, perhaps someone could update the readme to include the fact that the latest RPi OS won't work with PG2?

If you use the Raspberry Pi Imager, choose Raspberry Pi OS (other) and then select Raspberry Pi OS Lite (Legacy). After installing PG2, follow these instructions to fix the “ee key too small” error. Then you should be all set.

Last I checked, the most recent Raspberry Pi OS doesn't support mongodb so you are unable to install PG2 on it. Update: I just verified that if you avoid the latest RPi OS and install the Raspberry Pi OS Lite (Legacy) port of Debian Buster instead instead, PG2 installs just fine (though you might have to follow these "SSL error" instructions to get it to start properly: https://github.com/UniversalDevicesInc/polyglot-v2#ssl-error-ee-key-too-small).