larryllix

Looks like the amazon webpage access has been locked out to Canadian IP addresses again. It will not take a login anymore. The account name and password can be filled in but all buttons and options are dead and do not respond. hmmmmm.... Google Home is looking better all the time, exsecially with multiple Echoes and Dots responding simultaneously and just not answering at times. Yesterday we did a little experiment and found some Dots would add a certain item to our shopping list while the Echo and Dot across the room would not add it, or even respond when that particular phrase was used. When we removed the "Robin Hood" name from the item it worked flawlessly every time. This happened with one Echo and one Dot. The other two Dots had no problem with the same phrase it at all. Just ignoring and not even acknowledging the request is not a good response

Thanks Benoit! Your efforts and responsiveness are appreciated.

I detect my garage door with an IOLinc and flash a bulb in the corner while the door is open, the whole time. I use a corner lamp that is usually white and flash it red in a throbbing pattern look. If The Gathering Room lights are turned off and the bedroom lights turned on I flash the bedroom lap 100%. With normally only going on about 15% at night a 15 Watt LED bedroom bulb is hard to ignore. During the day if the car hasn't left (detected by a CAO Tag signal lost) I wait about 4 hours to send a notification to our cell phones and email. If the car is detected away I send the notification in about 5 minutes so I don't get too far away before turning back. Occasionally my wife will be out shopping with the car and I will have the garage door open to do yard chores and she gets a notification. I explained the logic and she is fine with that. Good descriptions in the text is paramount. So far I have both home and away situations covered fairly well but there is always room for more Jello!

I am not sure what your problem with this program is as the technique has rolled but... You can combine your programs into one with the ISY parenthesis and logic.' If ( Time is 10:30:00PM OR Time is 11:00:00PM OR Time is 11:30:00PM ) AND Status 'Outdoor Garage Door-Opened' is On Then Send Notification to 'DAD' Else - No Actions - (To add one, press 'Action') This is where it can get tricky if you are not a Boolean guy, but you will get there and be crazy like the rest of us. Watch your bracket placement.

My V2 is getting almost to the point of uselessness with delays. Alexa just goes away a lot and most of the correct responses take 20 to 30 seconds. At times devices are done their slow dimming before verbal responses. I previously deleted all my other skills as I can never remember the language syntax to operate any of them. Good for demo time but then mostly useless so they got deleted and that sped things up to like new speeds again. I have not intentionally added any skills to Alexa so I don't know why it is so slow again. The walk across the room to the light switch has become faster and more reliable lately. I saw a Google Home a few days ago and it is starting to look a lot better for smoothness of operation, understanding of vocals, intelligence, and much, much better sound than my muffled Echo and squawky Dots. It could be blasting out music and hear itself addressed by a quiet voice across the room with her back turned.

I agree. This doesn't sound possible. Program logic is only evaluated when a logic element is changed. Control /Swicthed detection is only ever True while that signal is live. No other signal event can ever true at the same time Time triggers use the same logic as above. Time frames from-to are different and true between the two times. In this logic If ....control device1 is switched on AND ...control device2 is switched on can never be logically true since ISY cannot evaluate two "control/switched" signals at one time. Timed event logic lines act the same. Status should be required with an AND and another control/switched signal to ever become True. Perhaps mazzaro can post his successful program? Right click on the program icon/copy to clipboard. Then paste into the <> initiated symbol text box that pops up.

I agree with the delay sentiments except where they are triggered by an MS. From a manual switch, the half second is insignificant. If it is important then walk to the switch sooner.

I was using a mini-remote but I find the range very short so the cell phone app does work better. I try to always put a long period time-out in any override program. Years back when all the kids lived with us, I found lights left on all the time. You can't confuse them with automatic lights everywhere and then leave a few manual ones and still expect people to remember what they turned on manually too.

KPLs are clumbsy to use, ugly and protocol troublesome. I only use one for a combination code keypad and a garage door indicator. A simple Echo can replace 10 KPLs for fan speed controls and no reading of the buttons or custom engraving is required. To each his own.

ecobee3 took me a while to get familiar with it. Like all smart stats I find it has some quirks and support (as all manufacturers) has no clue what their own terminology means but.... I found the "follow me" feature very poor, unworkable idea and support gave me complete BS using figures from my own stat that are arithmetically wrong. LOL Anyway, I find the ecobee3 the most advance and best performing stat of Nest, Venstar Colourtouch, Insteon, and Honeywell. As on all of them you can't go by the front temperature display but recording TAGs show the real performance. ecobee3 is the best I have seen / used for stability and accuracy. With the latest advance io_guy has put on the ecobees3 interface, if it works as I think it will, should eliminate about 30 programs in my ISY over the Colortouch. Fan cycling is awesome but takes some metal adjustment to realise how well it can work.

I got an ecobee3 and deleted many programs from my ISY as it has a very intelligent fan cycler built in. Using ISY, I synchronised my fan, separate humidifier, and HRV air exchanger with my HVAC cycles to save energy. This took a master clock created using a variable, synchronised to my HVAC fan calls for heat. Then all other device cycler programs were synchronised to that central clock. All devices started together and only when the HVAC fan stopped was the cycle resumed on it's own cycles again.

The If section logic should see the change and retrigger itself anyway. I think I was confused about PyISY. It is a different product than I was thinking of in NodeLink. My bad there. Thanks to @Jimbo for jumping in and fixing that mistake.

The previous technique was to use the Network Resource module to send a level value to the REST interface built in to the ISY, setting a variable. I don't know how you would get a variable back into the device brightness though. Perhaps a bank of programs to do it? You should really only need a binary log progression of settings anyway. 100%, 50%, 25%, 12%, 6% and slow ramps in the bulbs. I haven't used PyISY for a long time but I thought others have used it with V5.0.10 sucessfully. I only use NodeLink now and it contains all ISY io_guy's past bridging software now, I think.

LOL> Well that would be a ramp up and a quite quick one. Nicely done though! I am surprised you can see see anything until about 10-12% brightness though. I can on my LED strips but they are remotely controlled voltages like a SwitchLinc would do to a connected LED bulb. I can see you are going to be dangerous with an ISY in your hands!

Replace one bulb or add an incandescent bulb to the circuit somewhere. One dummy head with a 6W Christmas festive bulb in it.

With v5.0.10 it is built in and quite easy to save the level and restore it. Here is one light I do a slow fade for a sunset effect. Circadian rhythm colours are easy. Set your reds and yellows at a fixed level and fade the cold white mix down over time. White LEDs cannot really do proper colour mixes for this with their narrow band blue LEDs. With a percentage level drop your brighter bulbs will catch up with your lower level starting bulbs and changes looks more linear to the eye. The Wait 0 seconds line is because I have about 6 circuits involved in this dimming and they all have separate and different Wait X seconds line so there is no abrupt room level drop and the program load is spread out. (should never be a problem with ISY but maybe with Insteon protocol) Sunset.fade.chairs - [ID 0114][Parent 00C8] If $sGathRm.mode is $cMODE.SUNSET And 'Gathering Room / PotLights over Chairs' Status is not Off Then Wait 0 seconds $ChairPots.level = 'Gathering Room / PotLights over Chairs' Status Repeat While $ChairPots.level > 6 Wait 1 minute $ChairPots.level = 'Gathering Room / PotLights over Chairs' Status $ChairPots.level *= 0.95 Set 'Gathering Room / PotLights over Chairs' On '$ChairPots.level %' Repeat 1 times Set 'Gathering Room / PotLights over Chairs' Off Else - No Actions - (To add one, press 'Action')

What oberkc posted above. If there are any hiccoughs on the Insteon port protocol some signal buffer can get overwritten. I have two units that ISY complains cannot be communicated with (despite being disabled). Including them in a list of devices to be controlled, fails the control of any device controls following for the next 5-7 seconds, whie the Insteon signals go through so many retries, and echo of retries. What Techman said. Insteon protocol is supposed to play nice with other device signals and wait for completion of protocol. I think we have situations where Insteon isn't following it's own rules and clobbers previous signals before all the ACKs and echoes are done. This may be newer device's firmware, or a change in the Insteon PLM port driver logic. I don't remember ever havng trouble with this before the last year or so. (v5.0.10 here). Insteon protocol is tooted to avoid thisn problem. Add a few "Wait 1-2 second"s every couple of lines, especially after large scenes.

Look at your programs in the admin console and see which one is turning Red then green repeatedly. Right click it and then select Stop. As per Gary above....This is usually caused by the same device in the If section as you are controlling.

We may have bumped into the Canadian cross-border thing again with Alexa. In Canada the intercom feature, local weather, and many other features do not work, or do not work properly. I had to get a virgin tablet with no trace of google anything with ID on it, before amazon would even allow me to download the Alexa App. It seemed to scrape google ID out of it every time and refuse to allow access to the app, despite my location (and IP address) n the US. Now I believe amazon is allowing their app equivalent webpage to be used 'cross-border.

Nice. ...."I love it when a plan comes together!" See my edit on last post. You're too fast for me.

LOL. OK. That could save me some ISY program complexities then. Thanks!! I see you are not using v5.0.10 yet. There is no coding required to have it communicate with ISY, all decimals perfectly placed. Very nice. I am finding my batteries need changing again but one voltage does not do it for all. 2.78 volts my one inside the house unit starting acting crazy. The other units are working well below that voltage. I think the voltage limits may be temperature dependant. Colder seems to make the voltage drop but the Tag works fine.

OK. Is this in kumoapp coding, URLcalling or direct email notices or ....?

I have been graphing dewpoint in the app charting for about a year now but see no available function to get dewpoint sent with any available method???. Exactly where are you using the dewpoint function and what does the code look like?

Nothing mentioned in their help docs. It still says only RH% is available for use in coding. I don;t see any change in the URL calling options either. The app reporting and graphing implemented dewpoint about a year ago.

That's good and it's bad too. It could be an indicator of a failing PLM.