larryllix

I don't cknow what your stat is called.. You must create a variable first to make use of one. Sent from my SM-G781W using Tapatalk

If therm.setpt <= 9999 Then set $variable = therm.setpt Else ---

It always appeared to be a bad interpretation of negative signed binary value. Been there since v4.xx Sent from my SM-G781W using Tapatalk

...and you installed the IP reservation into the new router's DHCP reservation table so it doesn't move around?

Vacation mode is not a Climate Type on the three ecobee stats I have owned. Away is a climate type. Vacation is a mode that supercedes any climate set. I was setting my vacation mode from ISY originally, but later changed my style and let the ecobee thermostat control my ISY programming. I can set vacation modes in my ecobee years ahead, program multiple vacation times easily, it is extremely reliable, and times can be installed, modified, and cancelled remotely from a simple ecobee app on my android phone. It is much simpler than attempting to customise programs inside ISY code and the vacation list can be viewed in the same app.. Then my ISY can control my remote humidifier levels and fake home lighting activities when instructed by my stat.

My favourite one is TV lights. I have a raft of ISY programs to dim the bulbs slightly each half hour and reduce the cold whites to zero while maintaining some warm white. It works and after a few weeks we go to bed before midnight. After experimenting with many calculated brightness levels based on the ISY clock, I have decided to just use time triggered programs to set my WW and CW level variables. When the individual bulb bank programs see the state variable change they update my bulb levels automatically. I use mostly MagicHome WiFi bulbs. They dim right down to 1% and have RGB as well as CW and WW and any combination of the above. They can also be controlled by apps and BT apps should my ISY brain go down or worse my router bite the dust. No cloud services required.

Insteon scenes are not designed to be dimmed. Just use several scenes and select one which suits your lighting mood at the time. I always control programs that operate Insteon scenes along with non-Insteon bulbs. Alexa...turn on bright lights Alexa...turn on T.V. lights (self ramps levels down as the night progresses) Alexa...turn on Christmas lights Alexa...turn on very dim lights Alexa...turn off inside lights

Yes, The built in O/S software. It is much faster, updated before the viruses come out, and virus attacks just seem to stop happening once you discard 3rd party anti-virus softwares. I haven't seen a virus on any system for probably over 20 years now, since I stopped downloading trojan horses with big-brand anti-virus software names on them. Norton (freebie) ended up crashing my whole system years ago. It couldn't be removed and I had to low-level format my complete HDD. It had installed portions into the initial bootup sector of the HDD and kept reloading it's demon packets off the cloud.

Those are the internal Eisy hardware clock updating the software copy of the time every 30 seconds. With no packet information included in each line, they cannot be from any devices. Insteon devices are not polled regularly and are 99% push technology. No action = no traffic.

What about the people that just purchased an ISY994 three years ago?

After you put the MS into linking mode you should be able to Query it for a few minutes before it times out. This was done to protect battery drain from constant queries.

$cTRUE is an Integer variable assigned a value to indicate what True is in my system. To permanently assign a value to any variable you put the value in the left column of the variable and each time the system boots up the value get copied into the value of the variable. You never change it then it is permanently assigned. It can be any value you would like and usually assigned 1 or some non zero value. All programs that use it will understand, no matter what value you use. It is for convenience and clarity of program understanding mostly. '$' is the prefix all variables get assigned by the ISY system 'c' is the prefix I have assigned to indicate is is a constant, I never change it 'TRUE' is the name I have assigned to the variable indicating it's usage. . . . .The caps also indicate it is a constant value, and a common method used in many programming languages, to indicate it is a constant value. Many programming languages have values like this permanently defined in the language. $sVacation is 1 <--would have been equivalent, in my case, but less clear what it's purpose is, to other readers.

You need to include a quote or a ping (like this) @Michel Kohanim to get his attention back. He is a busy man and doesn't read every post for entertainment purposes.

Do you mean they blink bright or dim temporarily, or they come on or off, and stay that way?

For now...and likely forever, ( Zwave, Matter, Insteon collapsing, xxx, YY, polyglot, polisy, eISY, and IoX launcher, have always dominated the progress over new features and small operational bugs, for the last 4-5 years) change the line to a comment and enter the same line's text into it. When you restore it you already have the placeholder and don't have to click it up a dozen times to get it into the right place again.

Zigbee is a basic level protocol and almost every brand uses a different high level protocol. You would need specific driver that understands Hue's protocol and likely a different driver for every brand of device.

MagicHome / LEDenet also tries to force that business model also. However, there are still other named apps out there that allow linking to an SSID without any cloud interaction. FluxNet app is one. None of my WiFi bulbs are cloud dependent.

This is the method I use but the MS II has a problem with the send OFF enabled. If you set the MS timeout shorter than the program Wait time, the MS OFF signal will interfere with the program timeout. If you set the MS timeout longer than the program Wait time, the MS will not reset to send another ON signal in time to reset the program WAIT time. The MS must have the OFF signal disabled and the timeout must be less than half the program Wait time to properly extend the program ON/True timer. If the MS ever times out internally, and it keeps seeing motion, it will never send another ON signal. The MS II needs a second internal timer, not use the same timer for both ON and OFF delays.

Exactly, but only when the time slicing executive can get a break. This is done during any Wait, or Repeat loop, in the ISY code. Those lines are a voluntary "let somebody else have a time slice" construct.

When I was in this process I set up a bank of state variables that were cloned in my polisy. I created a program triggered by any variable that changed and sent them allover to my polisy. With variable control over banks of lights in my home, it was so easy to setup and each program could be ported over to the new device without any interruption of any lighting controls or scenes. I was going to do the reciprocal to send any changes back to my ISY at which point I decided to commit and retire my ISY instead. It was a lot of fun synchronising the two boxes but it was time to walk away.

Then as per @oberkcpost above. The MS II has some design bugs in it. If you have the MS and lights linked directly, then you will want the timeout on the MS quite short (say 30 seconds?) and no Off signals sent from it (On only). This tries to avoid the Off lockout for the same length of time. As long as the MS II keeps seeing motion and never times out while in the OFF state, it will never reset to send another ON signal. Hopefully the new Insteon manufacturer can see the light on this one and fix this before producing them again. Without at least one working sensor, Insteon is not home automation anymore. It is only remote control and timers, like Alexa or GH boxes, but without a voice input or output.

Looks good to me but you can right click on the program name in the tree and select copy to clipboard. Then paste it into your post. Much easier to read with a HD screen. Do you have any of these devices linked to your PLM via Insteon links? If your MS times out it could turn the devices off in error. Is you MS set to fast time cycles? It could be continuously re-triggering your program to start over.

How would you switch devices between switches? How about two WiFi routers with cloned setups and both on Insteon On/Off modules, allowing ISY to switch them over? The hardwired Ethernet devices would require some manual switching.

Yes, There has always seemed to be a fear of writing too many programs with the usage of variable/flags. As an old coder it is hard for some to get over the concept of so many programs. At first is seems like you are complicating program things but after using them, it makes programming a larger system much simpler. I remember many negative arguments against variable usage. Even with my Alexa voice control (on/off only) I use this path style: Alexa vocal-->program-->variable-->program(s)-->device(s) All levels of lighting are based on a value in a variable and then a triggered program controls banks of lights, depending on the last value in that variable. Another side benefit is the ease of saving the levels of 15 bulbs into a single variable so that a flashing bulbs warning can be used temporarily, and then restored after, by using only one line of ISY code.

Definitely. I have programs that are 40 to 60 lines long and when I debug I have to delete a line to test and then rebuild it before moving the new line back up 45 clicks to save. Then there are the bad replacement errors that can creep in. One way is to copy the program and disable the original program. Then delete bypass lines to test. Once done, delete the test program and re-enable the original program. Sent from my SM-G781W using Tapatalk