larryllix

I have about 10 Insteon Leak Sensors that U have no need for any more. If interested PM me.

$iMotionCount =+ 1 Probably would be listed as $iMotionCount += 1

Yeah, It seems rather odd that the webpage alexa app will not allow so many things for setup, and yet under the devices you can individually disable/delete items and also discover new items...and without the silly verbal reminders and warning, so annoying. No I don't have a Hue Hub,..... and why only a reminder bout a Hue Hub over the other few hundred brands? Oh yeah a warning! If you delete all your ISY devices for longer than a few seconds you will need to re-define and re-enable all your Routines inside the mobile Alexa app again.

Alexa doesn't like when you cancel things in ISY Portal, and sometimes disables things it thinks do not exist anymore. AI (guessing) at it's finest.

It is intentional then and I didn't find a bug to report. Thanks. Mentally fixed here. Sent from my SM-G781W using Tapatalk

This must be new to me also. Did you mean IoP? I have never heard of logging in to polisy via ISY finder. My URL is http://192.168.0.165:3000/dashboard I never use https.

While on this subject, what is with the login via ISY Portal that takes you back to Polisy to login again, every time? I thought only one login was necessary last update. It seems the login process has gone haywire again.

@Michel Kohanim IoP error after TriggerLinc option close. IoP 5.4.4 Polyglot 3.1.10

Gotta' wonder if a bleach bath could make these work again for a few more years. It may make the plastic somewhat more brittle but it would be worth a shot. Hopefully the new Insteon could offer replacement parts for those. They don't contain any ICs so there should be no excuse there and it could be quick money for Insteon.

"Trigger" was Roy Roger's horse so.....

I would wait until Michel gets on this from your open ticket. I assume you meant to use the acronym IoP, as IoT has a different meaning typically, and may confuse some. Sent from my SM-G781W using Tapatalk

I don't think aartech.ca had one Insteon item in stock a few weeks ago when I last checked, so I would say Insteon is feeding our Canuck counterpart nicely.

I have always had to restart my whole polisy any update I have done. Some small quirk always seems to show up. Sent from my SM-G781W using Tapatalk

Yeah, It seems like it would be so easy to add another pulldown option in the menu, and add the same code without the "program Stop"

Just some observations Why not use vacation mode if a permanent hold is wanted? I am not sure Away climate will ever be Indefinite remotely, and may not be a possible combination . I have never used Away on my ecobees. This is my third, now. What is your internal schedule hold set to? This may be overriding any remote Hold. I gave up trying to have my ISY control my ecobee stats (they already contain very advanced logic) and went the other way around, finding that the ecobee stat firmwares were so much more stable and didn't rely on cloud and multi-processor mediums to operate. In the end, a much more reliable and easily settable way was for the ecobee Vacation schedule status to control my ISY vacation logic for the whole house. If the connection failed it was only some fancy HA stuff like humidifier, HRV, fan cycling, security lighting etc.. not my home heating. Of course my house (slab heat in Canadian winter) would only reheat about 1 degree per hour, at best, so when it failed, we slept with a lot of blankets the first night home and used the stove a lot, the next morning

Here is what I would like to see... Program 1 If condition = True Then deTrigger Program 1 <------ disable If section without stopping it do something wait 5 seconds do something else enable Program 1 <----- enable If section Else ----

I heard you were coming and moved. Here is a map of southern Ontario. See the braying elephant? I lived in a**hole.

He couldn't live up to the blonde image giving good advice like that. Sent from my SM-G781W using Tapatalk

Much better sound and visible people. I wonder how all the overpowering ambience got removed. Steve Lee was a bit better with curtain behind him to absorb much of the echo. Of course I am sure there are digital algorithm to remove some of it. My Amazon echo can only hear you if you are the furthest across the room you can get. The close ones hardly ever answer.

All looks promising for Insteon future! Sure glad Steve Lee is on that team. Hopefully this time he will be given a bigger stick.

I can see you are a man of experience. Not many would even realise these quirks without sweating through it themselves. Still have any hair left?

Yes. IIRC this is only event driven system I have worked with, that can have processes stopped and restarted. I would guess in the beginning UDI had to decide what to do when a new event happens that is the same as one already being processed. Continue like nothing happened and ignore the new event Continue like nothing happened and stack the new event for sequential operation Stop the current process and handle the new even like the previous process wasn't happening. The choice they made provides a lot of strange happenings in even processing and program writing. It definitely puts a hiccough in the logical thinking of experienced inline code writers. Now I would like UDI to add a program disable command that allows a program to finish what it started. Currently the Disable program command line also stops the affected program. "They just have no self-control..."

Yeah, Spaghetti code can't really exist in ISY event programming. Although you can make some very interdependent event driven code that can oscillate. Been there, done that. BTW: I use the Repeat While construct as an inline If/Then/Else construct. Since ISY doesn't offer much in the way of inline conditionals, it makes and avenue to get things done. I don't like it but the whole thing would be much better if I could change the names of the construct to suit better. Good inline commenting and labeling helps the confusion a lot. It can get complicated when you write ISY code to average multiple sensor inputs and discard outliers but it works well for analogue inputs to be reliable in the event of a sensor malfunction and I always like to not use sensor analogues directly from input devices. Passing them through a stats variable has allowed me to swap input devices, change scaling and otherwise massage data that would mean modifying many programs using that data. When I half moved my programs fro ISY to polisy it took one program to synchronise sensor data between devices. Some see that as too complicated and some see it as simplified at the cost of a few more bytes of code. At least ISY offers many ways to do things and we all have our druthers. This is about the 5th system style I have worked with that used event driven code. If you lived on VB, using their "objects", for a length of time, you would fall right into this style.

Nice! I use integer variables profusely for constants with labels and my only records are imbedded comments and ISY element names. eg. $cTRUE $cFALSE Element names are always positive logic and try not to be ambiguous. eg. Program: deviceName.batt.ok All just good programming practices from inline code habits learned the hard way. I avoid hidden and obscure things like using program state logic etc. Sent from my SM-G781W using Tapatalk

Scalping forum is just around the corner. Sent from my SM-G781W using Tapatalk