randyth

Nice!

This is a very interesting thread, and kudos to UDI for embracing those of us crazy enough to run multiple home automation systems. @Michel Kohanim Does this initial script install Home Assistant Supervised or Home Assistant Core?

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

For those of you using an Alexa with your home automation... Did you know that Amazon is tracking all the activity of the home automation devices you've exposed to Alexa whether or not it was Alexa that triggered that activity. This includes things like manually turning a light on or off, or having your ISY activate something on a schedule. To see your Alexa Smart Home History, try this link: https://www.amazon.com/alexa-privacy/apd/dsh?ref=activityHistory&locale=en-US If you click on Manage my smart home device history->Email history from that webpage, you can get a CSV file with the status and usage information Alexa has about smart home devices associated with your account. You will also receive access to a report with "helpful insights" about your use of smart home devices connected to Alexa. That's not creepy at all.

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.

@shbatm, thanks so much for starting work on this so quickly after I reported the issue.

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.

I'm a fan of the slightly spendy but very flexible Flic buttons. I have some that link directly with Alexa, some that call the ISY's REST API, and some that call my Shelly devices' REST API. They recognize press, double-press, triple-press, and long-press actions for four different operations per button. Again, very flexible. Here's a list of all the services they support out of the box: https://flic.io/all-functions Unlike Insteon's mini remote or Lutron's Pico, Flic buttons are just one single button.

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!