larryllix

Programs using State variables in the IF section can be self triggered for re-evaluation each time the value changes. Integer variables do not self trigger programs and must be manually run via another program (subroutine) or another trigger in the same If section. IOW they can be used as filters only. Sent from my SM-G781W using Tapatalk

I have been commenting all my disabled programs in the "IF" sections, when disabled permanently. I have been through this previously when all programs became enabled, and it took a few months to debug some of the programs enabled that shouldn't have been. It was also requested to have the disabled flag/checkbox displayed in each program many years ago. That may not have helped this situation though.

Can you tell me the difference between PG3 and PG3x please?

Are your MSes data traveling via Alexa to get into your ISY box, and... Are you not using pseudo variables to emulate pseudo MSes in the alexa app via the ISY portal? That is the way I have my data paths arranged so my comments may have been mute for your case.

My Alexa boxes will still report news information, they stole from the news networks. in Canada, yet. Try disabling and then re-enabling your Routines in Alexa. Amazon boxes seem to do this about once every two years and they will never admit they found a problem after it starts again. I went about 4-5 months once and they finally started to work again. At time a software or firmware update will diable all your routines. Another thing that happens is you disable all your devices in the Portal for more than a few seconds, Alexa app will delete or disable all your routine connections to devices that didn't exist at that time.

I saw that USB one and considered it, but price and physically sticking out the back was a deterrent, so far. I guess I could short USB flex cable it up and away from the concrete box (bhind the drywall) it is in, in an apartment. The internal polISY board was so compact. Another negative is, they went back to those expensive and extremely short lived AAA cells. For the size difference I don't now why any company would support that size, when they have about 1/4 or less the capacity of a much cheaper AA cell. My stock of AAA cells has been declining with my divorcing all the X10 MSs and other gadgets not using them much anymore. hmmmm... maybe I'll wait until I come across some ZigBee things that handle microUSB-C adapters. I have a bad taste in my mouth from replacing 30-50 batteries per year for X10 and Insteon HA devices over the past several decades. My current 3 MS IIs are on adapter power now. I like it much better than buying batteries in bulk. Right now I only have one Insteon door detector that eats a AA cell each week or two. I couldn't get a cord to it easily, anyway. Any indication of how long a pair of AAAs would last in these ZigBee MSes?

That might convince me to go to Zigbee MSes next. I am tired of Insteon being a remote control only supplier and Insteon MSes are all RF anyway. The MS IIs have logical bugs in them and I need more. The dozen MS Is would become totally redundant for me then. Trouble is, I have two PolISYs and I don't see the Z-Matter internal board available any more on UDI. Is it still available yet?

Did you put the MS into linking mode? Is the hardware jumper set to "soft" adjust parameters? Turn your brightness up to about 70 so you can see LED responses to motion. Turn your sensitivity up to 70 so it can see motion. Is your MS set to off mode? It will not return to normal for 495 minutes (you setting) then and you won't see any packets sent. If your MS times off it must see no motion for at least 30 seconds (your setting) to reset, or it will not send another On signal...EVER. (bug in design)

IIRC, there was a thread about how the On Level is a one way parameter that ISY can set and operate to but cannot read it from some Insteon lighting devices. I may be way out in left field here but it just rings a bell in the back of my memory cells from about 2-3 years back here.

That is not commenting out code lines for debug purposes. You are adding more complexity of conditional lines into code before any debugging is needed and not any solution for subject of this thread. How would you debug those conditional lines if you suspected one wasn't working or doing something it shouldn't? Surely you wouldn't have added more conditions into those programs to disable the conditional lines. That would be getting more ridiculous. The OP is wanting a way to debug existing programs not complicate them.

Wrong thread? I don't see the purpose or a related message in this thread. Did you know you can copy a program to the clipboard and paste it here in a more readable text format? Right click on any program title in the program tree, and select copy to clipboard.

LOL...OK. I didn't realise I was in some specialty hardware thread since forum titles are not shown with new posts. You would have to contact the node server programmer and ask for it to be added. Good elaboration for somebody that was lost here.

Read my post that you quoted. Other than that previous answer I have no idea what you are asking. I don't understand what "outside a programming UI" means. Again. Temperature is an analogue value bit a status. Please clarify more of what you want to know.

Here is what a "scene" using the software I mentioned looks like. It takes about 0.5 seconds to execute from the first bulb to the last, 8 bulbs. The scenes are created dynamically by ISY, as needed by the ISY programmer. LivRm.theme.dim - [ID 003A][Parent 0043] If $sTheme.livRm is $cMODE.DIM Then $NRb.cwLevel = 2 $NRb.wwLevel = 15 $NRb.rgbLevel = 0 $NRb.bulb1 = $cBULB.LR1 $NRb.bulb2 = $cBULB.LR2 $NRb.bulb3 = $cBULB.LR3 $NRb.bulb4 = $cBULB.LR4 $NRb.bulb5 = $cBULB.LR5 $NRb.bulb6 = $cBULB.LR6 $NRb.bulb7 = $cBULB.LR7 $NRb.bulb8 = $cBULB.LR8 $NRb.bulb9 = 0 Resource 'NRb.set' Else - No Actions - (To add one, press 'Action')

When did the setpoint on the thermostat change to 74F? Actually reading back (I missed a few posts) I think you are correct and may have found another bug in v5.xx. There are still many remaining bugs since v5.0.1

The program will self-run when the setpoint on the stat is changed. Try manually changing your setpoint on the thermostat and see what happens to your variable. Also note that all variable designations are prefixed with a '$'. It is also a de facto standard, and a good idea, to add a method of denoting a state variable, to avoid user confusion during programming and debugging. It could result in variables used in programs looking like this: $sCool_Setpoint = ..... State variables may cause programs to trigger while Integer types will not. Not being identifiable in programs may cost you a lot of time later sorting out variable function confusion.

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.