Xathros

Hi Jimbo- I have a few programs in my set up that do this sort of thing. Let me give you a few ideas. First, Program: Back Deck Timer Daytime If From Sunrise + 1 second To Sunset - 1 second (same day) And Status 'Back Porch / Back Porch Flood Light' is On Then Set Scene 'Back Porch / Back Porch' Off Else - No Actions - (To add one, press 'Action') No reason for the floodlight to be on during daylight hours. If a someone turns it on accidentally, turn it back off. If it was left on before sunrise, turn it off at sunrise. Second, Back Deck Timer Nighttime If From Sunset To Sunrise (next day) And Status 'Back Porch / Back Porch Flood Light' is On Then Wait 15 minutes Set Scene 'Back Porch / Back Porch' Off Else - No Actions - (To add one, press 'Action') 15 minute timer. Adjust delay as necessary to suit your needs. Next, Program: Back Deck Timer Disable If Control 'Back Porch / Back Porch Flood Light' is switched Fast On Then Disable Program 'Back Porch Timer Daytime' Disable Program 'Back Porch Timer Nighttime' Resource 'TIMER: Back Deck Timer Disabled' (Notify me if timer is disabled) Else - No Actions - (To add one, press 'Action') Disable the timer for those times when we are working out there and need the lights to stay on beyond the normal timeout. And finally, Program: Back Deck Timer Enable If Status 'Back Porch / Back Porch Flood Light' is Off Then Enable Program 'Back Porch Timer Nighttime' Enable Program 'Back Porch Timer Daytime' Else - No Actions - (To add one, press 'Action') Re-enable timer when light is turned off for any reason. (Self correcting system) I have a set of these for each of my outside lights. Works like a champ. I also have a midnight cleanup routine that will turn most things off at midnight if left on. I have one KPL button in my master bedroom that will override this and a number of other automations in the rare event we have a party or something running that late into the evening (NewYear's eve etc.) Hope this helps. -Xathros

We will likely need to stop referring to the beacon test as the 4 tap test as Insteon progresses into the new flow chart (I forget their name for it) method of configuring devices. Also, do you have the full manual for your dual band devices or the "Quick Start Guide" as the beacon test is usually not covered in the abbreviated quick start guides. -Xathros

Sounds like some missing link records or comm errors to me. Start the event viewer at level 3 and select restore device on the KPL from the ISY and see where that takes you. Post the event trace if the restore does not solve the problem. -Xathros

On the remote/client end, port forward port 443 through the router and point it at the ISY. Set up a DynDNS service to track the external IP of the router/modem. Then in your ISY Finder simply add the url pointing to https://DynDNSname:443 -Xathros

The beacon (4 tap test) only applies to dual band devices / access points / range extenders. Single band (power line only or RF only) are incapable of bridging the power line legs via RF. You will find no mention of the beacon test in any single band device manual. -Xathros

Blame it on the solar flares! -Xathros Sent from my iPhone using Tapatalk

Just put a wait 3 before the scene off command. -Xathros Sent from my iPhone using Tapatalk

OK. I'm out of ideas then. -Xathros

What platform are you on? Mac or Windows? @stusviews- I assume you are on Windows? May be a difference in the Java UI for Mac/Win. -Xathros

Eric- Anytime. Happy to help. -Xathros

Mine turn blue when I'm renaiming a folder: -Xathros

Eric- Why test the status of the button? Just test the other lights and set the button. If it's already right, no harms done. If ( Status 'Basement / Basement Devices / Basement Bookcase Lights' is On Or Status 'Basement / Basement Devices / Basement Steps' is On Or Status 'Basement / Basement Devices / Basement Main Lights New' is On ) Then Set Scene 'Basement / Basement Scenes / Basement KPL Monitor Hallway ' On Else Set Scene 'Basement / Basement Scenes / Basement KPL Monitor Hallway ' Off This should take care of the whole thing for you. If one or more of the lights is on, the button will be lit. Otherwise, it's off. -Xathros

Ahh. Sounds like it could be a valuable tool. There are a few things I would like to do but haven't due to the need to my user/pass to be sent in the clear. Started building some cgi scripts to get around that. -Xathros

Since the mid 90's -Xathros Sent from my iPhone using Tapatalk

Always happy to help when I can. I'm not sure what you're referring to with ISY Proxy. -Xathros Sent from my iPhone using Tapatalk

I haven't played with Hue yet. There are others here that have. I know there is an IFTTT channel for Hue that you might be able to trigger with an email. Once I do get my Hue, I will be attempting direct control over the LAN. I don't expect to be working on that for a few months yet. -Xathros Sent from my iPhone using Tapatalk

As always, happy to help. The /REST interface requires dropping leading 0's so yes, and Insteon address with a leading 0 will be affected. I believe that if you run the Topology report, all of the addresses will be listed without the leading 0's in the format that you use in a /REST call. I keep an electronic copy of a current topology report for copying addresses from when developing /REST calls. The speed will improve. Somebody at UBI central probably "spilled pixie dust on the server" again. I have seen this several times during UBI's beta process. It usually clears up in a day or two. -Xathros

I assume that the lights turning on and the UBI followup response are happening nearly simultaneously. -Xathros

This is entirely an UBI portal issue. It is the NLP routines in the portal taking for ever to process your voice request. This comes and goes. My normal response time when things are working is 2 seconds from request to action. When its bad, up to 30 seconds like you are seeing now. If I was home, I would try one of my commands to see the response time. I bet mine is slow today too. -Xathros

Also, if UBI is still not working on voice command, try: "OK UBI... Update" This will force UBI to update with the latest changes you have made in the portal just in case it missed something earlier. -Xathros

Good. Your on your way. Next, add a followup utterance to the UBI recipe after the url call that says "Turning on kitchen lights." This way you will know if UBI understood your request. Then another recipe to turn the lights off using: http://XXX:XXX@10.0.1.91:8181/rest/nodes/20 7D 6 1/cmd/DOF There is a helpful document called "ISY-WS-SDK-Manual" that will help you with all of this /rest stuff at: http://www.universal-devices.com/developers/wsdk/4.2.18/ISY-WSDK-4.2.18.zip Hope this helps. -Xathros

Drop leading 0's in the addresses: http://XXX:XXX@10.0.1.91:8181/rest/nodes/20 7D 6 1/cmd/DON -Xathros

OK. Copy the URL as used in the UBI and paste it into a browser. Does it work there? Paste your url here (with your user/pass obscured) -Xathros

1) Make sure that the request is coming from the UBI locally and not via the portal. 2) I find it helpful to follow the /REST call with an UBI Utterance "Turning On the kitchen lights." This way, I know that UBI understood my request. -Xathros

Because you restarted your MAC. Happens to me too. The Console preferences are stored in a temporary location that gets lost with a restart. As long as you only sleep/resume it will keep the stored addresses and other preferences like color scheme and window positions etc. -Xathros