TexMike

I think the repeat goes before the actions to be repeated. You can also look at the summary tab in programs to see when the last time a program ran. I think you're almost there, my suggestions in pseudo code since my program is a little different. You can also set a program to run at startup to make sure it's always running. It may also take a little while before the Query fails and the device becomes shows responding as false, so I added a wait. If Time is 5:15:00AM Then Repeat Every 15 minutes Set 'Outside / DeckLights' Query Wait 1 minute Run if DeckLightsResponding Else nothing Set DeckLightsResponding program to disabled so it will only run when called and will run every 15 minutes instead of only on state change as you have it now. Also when troubleshooting you can test your DeckLightsResponding program by tripping the GFCI and then right clicking on the program and selecting Run If. That way you know the notification program is working and can concentrate on the scheduling program.

I had to switch to my wife's Alexa account, could not get mine working again. Also had no luck w/ Amazon support even after they documented the issue and said they turned it over to the development team. On 7/8/2019 at 3:31 PM, TexMike said: I set up several Alexa speak routines and all were working fine for months until recently when I noticed I wasn't getting announcements. Started trouble shooting - When I change my Alexa speak variable in ISY the corresponding motion detector shows motion so ISY to Alexa communication is working and I can use Alexa spokens to change ISY devices. When I manually execute routines in the Alexa app the Echo announcements work. So I scratched my head for a while and on a whim I disabled a routine and reenabled it and it started working. I had to do this to all my Alexa speak routines although they were showing enabled. Any one else encounter this? Update: Worked for a while and now stopped again and nothing I try works, tried disabling/enabling ISY skill which seemed like a stretch because Alexa motion detectors are seeing motion when I change ISY variable. Seems routines are not running when motion status changes because I have a test routine when I say this, Alexa says that and it works fine. Ideas? Update2: Thought I would take Alexa speak out of the picture, so created a routine to turn on a light based on virtual motion detector and again virtual motion detector shows motion, but light doesn't turn on. Manually running the routine turns light on. I realize this is not an ISY problem since the portal is doing its job and turning on motion. Any ideas from the community? Since this thread hasn't seen activity in a while, tagging @bmercier Update3: In case anyone cares or encounters the same problem. Tried Amazon support since that is where the problem occurs, said they turned it over to development, but no solution yet. I decided to try my wife's Alexa account since she also has access to the ISY portal skill and it worked fine in her account. So for now I recreated my 20 or so Alexa speak routines in her account and Alexa is chatty again. Mike

After the query, make sure you literally check for responding status.

Query the device then check "responding" status of device. I have Z-Wave bulbs in my front porch and coach lights that are still controlled by a normal dumb switch. Each evening I check to make sure the porch light is responding before turning on the lights. If responding is false I send notifications and have Alexa say to turn the switch on. Normal members of the house are pretty much trained by now, but it does work great if the switch somehow gets turned off.

Thanks for confirming. Being able to expose a variable as temperature would be a nice future enhancement.

Thanks. I get the data in ISY just fine, but portlal doesn't support temperature or humidity so I have to fake it with brightness. It worked OK until we started getting above 100. The issue is being able to ask voice assistant for temperature when > 100. I was waiting for someone to suggest using Celsius, but then would have the opposite problem with freezing temps.

Implemented my workaround and heard driveway temperature is set to 5 percent brightness yesterday and the sensor is in the shade! @bmercier If possible, would be nice if portal supported temperature and humidity directly.

I have a Z-Wave multisensor at the driveway, I put temp and humidity in variables and expose in Portal as lights. I can ask voice assistant "what is driveway temperature" and get response "driveway temperature is set to (temp) brightness". Not optimal, but effective. Only problem is recently temps have exceeded 100 and brightness tops out at 100. Any way to get reports for temp >100? Only thing I can think of is to subtract 100 from temp if > 100, then it would report 2 if temp is 102. Any other ideas? Thanks, Mike

May have been my thread about iBlinds. My experience with Z-wave scenes for iBlinds, it works but since all Z-wave communication has to go through the controller, I can never get the blinds to act as one. I ended up going back to using a program with a 7 second delay between each blind opening/closing for a cascade effect that I find a lot more pleasing than the unpredictability of a scene.

Great solution suggested by @simplextech, but as usual a few kinks along the way. I thought of the use case where multiple open or close would be needed in a row, perhaps even days apart. If open was used last, then the program won't trigger open again. I decided to use separate fake geofences for open and close and reset after use. Turns out the old occupancy nodes cannot be controlled from the ISY, I could have used a network resource to do it, but didn't want to do that if it could be done locally. Found out the Occupancy 2.0 nodes can be controlled locally with ISY, so ended up setting up the fake geofences there and all is working as desired. Open program is below and close is similar, just less restrictions. GD Open Henry - [ID 00A4][Parent 0037] If 'GD Open / Henry' Occupied is True (fake geofence set true from phone) And 'GD Sensor' Status is Off (GD is closed) And 'Home / Henry' Occupied is True (real geofence) And From 6:00:00AM To 11:00:00PM (same day) Then Set 'GDO MIMO' On Wait 10 seconds Set 'GD Open / Henry' Off Else - No Actions - (To add one, press 'Action')

Bingo, that's the out of the box solution I was looking for. I already use the occupancy nodeserver via Locative on his phone, but I think I can set up another fake one for this purpose. Thanks! @jfai Yes, line of sight is preferred, but the GDO still has all the safety features, optical sensor and force reversal.

Issues with losing, no scheduling and remembering to take it make me steer away from that. You know teenagers, they always have their phone. Plus I can turn off the capability any time I want. I have the solution I want, except for the problem of how to set it up on his phone without exposing the portal credentials.

All good points, however I don't have an external keypad because I intended to install the Z-Wave module and considered it redundant. It also seems a risk that someone could see him enter the code. I did forget to mention limiting the schedule. So let's say I'm comfortable if it's within the allowed schedule, he's in the geofence and has his phone. How can I set up his phone to allow the opening w/o the portal credentials in clear text?

Installed MIMOlite on garage door opener a few days ago and it's working fine. I have a teenager who rides his bike a lot and I would like for him to be able to open/close the garage door from his phone, optimally only that. It's not that I don't trust him, it's just that good security practice dictates that a user should only have access to what they need and no more. I could set up a couple of bookmarked REST commands to run programs and that would work, but the portal credentials would need to be embedded in the URL's and I don't like that. I will be using programs because I also want to check to make sure he is in the home geofence for opening as another precaution and check the current status of the garage door i.e., skip open/close if it's already in the desired state. I also thought about using IFTTT as a way to sort of obfuscate the access, but it adds another layer and potential delay. Any ideas on the most secure way to accomplish this functionality?

I believe UDI Mobile was only targeted for Android, apparently worked for a while and then abandoned when Android updates killed it along with many other geofenceing apps. I did a lot of testing and could never get a reliable geofence on my phone. Later I realized I only tested on my mid-range phone maybe should have tested on my wife's Pixel 3XL. I moved on and changed the way I disarm and it works OK. The only thing I miss out on is a little HVAC recovery before arriving, so I gave up and moved on.

Glad you're on the right track. I just wish there was a reliable geofence for Android, power management seems to have hobbled all of them. I put in a request to Google for native geofence, I'm sure they'll get right on it?. I have resorted to just using WiFi connectivity for Android and hopefully some day Polisy will support presence detection and I won't have to support apps on all the phones.

When you set up a device in the portal it will give you URL's to set in/out. You can use any method of your choice to set in/out. I use Automagic for our Android phones and Locative for the kids iPhones.

Look through the forum links posted earlier. You can use Occupancy 2.0 with anything that allows you to issue an HTTP command. Locative works well for iPhones and Tasker and Automagic for Android.

I had not seen that, but found it in the Q&A after you pointed it out. Not sure what the 12.0V special charger is, the supplied charger is listed at 12.6V. I would expect the batteries to lose some life as they age, but with minimal discharge/charge cycles, I would hope for longer life.

@Jimbo Cable came in today and works fine. I powered ISY and Polisy with the ups unplugged for 15 minutes and the UPS battery indicator didn't move off full.

@Jimbo Not yet, supposed to get here Thurs. UPS also had a long lead time listed, but got here right away. This little cable is taking forever. Had another short power outage recently and ISY stayed up as expected. I ordered https://www.amazon.com/gp/product/B016BJGZ2U/ref=ppx_yo_dt_b_asin_title_o05_s00?ie=UTF8&psc=1 and will update when it gets here and I've tested.

UDI confirmed center pin on Polisy is 2.5 and ISY is 2.1 mm. Some cables will work on both, but the cables supplied with the UPS would not work on Polisy. I'll update when cable arrives. I don't anticipate any problem since the UPS port is rated for 2A. Next project is to keep internet up, which means modem, router in one location and an ethernet switch in the office where the ISY and Polisy are. Thinking ahead when the Polisy does everything, it should be able to fall back on WiFi which would be a little easier to implement.

Did you mean the DC plug or the antenna? I believe all Polisy's shipped with a female antenna adapter on one side, when it should have been male on both. It's difficult to notice since the antenna will screw on just fine, but won't actually make a connection. It's documented in other threads and UDI will ship out a proper adapter. I found out from UDI Polisy uses 2.5mm and some cables will work for 2.1 and 2.5, so I have one on order for the Polisy. Also UDI confirmed ISY is very tolerant and happy with anything from 5 to 30V.

Got it installed for the ISY w/o any issue. It's a little scary going from the UDI supplied 5V adapter to 12V, but all input in the forums said it was fine and new ISY's come with 12V. Polisy is another story, apparently the Polisy does not use a 5.5 mm X 2.1 mm plug. It looks very similar, but I think the center post is larger. I can't find it documented anywhere. Does anyone know? 12V plugs are rated at 2A, so it should be fine when I get the correct cable. I did take the opportunity to replace the antenna adapter on the Polisy while I had it out with the correct gendered adapter sent by UDI.

@Teken After predicting May 3rd, the little UPS arrived today. Static (no load) output voltage on a 12V plug is 11.25V on AC power and 11.0V using whatever charge the battery had when it arrived. So it is a little low. I've heard the ISY is very tolerant, but it might be a couple of days before I get it set up. I can't see my Polisy wall-wart and couldn't find any input power specs listed, so yet to see if it will also work on the Polisy. I'll update when I get it installed.