larryllix

In the ISY installing a new SD card was so easy. IIRC You boot up with a new SD card inserted, it knows that and asks you where your image is. You browse to your last backup file and it downloads it, installs it, and you are up and running. PoC (cake involved)

Also... using a central variable allows one to use multiple logical inputs (complex logic) to derive the desired outcome. Program logic only allows one program. It keeps things modular, independent, simpler to understand, and less obscure. When you duplicate a program and modify it, and then delete the original program, any obscure dependency from another program will be lost unbeknownst to the programmer. When I was cruising in the Carribean and some of my logic didn't work properly, I found it was nearly impossible to run Then or Else for any program to corrects things, as I could never be sure exactly what they would do. However, my variables were easier to understand their functions and easy to understand what was happening in my system. Another negative for program logic is it will be incorrect after a power blink until a sensor reports a change. That may never happen. Variables have methods of keeping values through ISY rebooting. As a side note: I had a temperature variable based on three sensors and a program that determined if any sensor was not within limits of the previous average, and cut it out of the averaging equation....sort of "self-healing" logic, if you will. Now, I had a much more secure temperature reading to base downstream logic on.

I have been finding that dimmable bulbs seem to be disappearing off the face of the earth now. I have only ever bought dimmable bulbs in the past as I believe they have better power supplies in them to not be blinking so badly with every power glitch. Don't forget to count the A/C cost savings into those lower heat bulbs. You will likely save that much energy cost in one year.

If you like to use variables, I use state variables to operate most of my lights buy triggering programs scenarios with them. Here is an example of my occupancy detection system. Variabes can make it so simple to write ISY code. These programs run a timer during waking hours, warn me verbally if it is about to expire, and finally turn the lights of in my apartment. You may notice another usage of Integer variables for constants. In one program you may see a variable named $cFALSE. 'c' denotes a constant value that never changes, and the all caps is another standard used in many programming languages to denote a constant value. Occu.countdowner - [ID 0005][Parent 0004][Run At Startup] If // Run at Startup enabled $sHouse.occupied.timer > 0 And From 9:00:00AM To 11:00:00PM (same day) Then // self perpetuating loop Wait 1 minute $sHouse.occupied.timer -= 1 Else - No Actions - (To add one, press 'Action') Self retriggering timer. -If startup occurs outside wake timeframe, will self start at beginning of timeframe. -If timeframe commences while occupied.timer is 0, first new occupied.timer value will start again. Occu.timeout.warning - [ID 000E][Parent 0004] If $sHouse.occupied.timer is 7 Or $sHouse.occupied.timer is 1 Then $sSay.occupancyTimerExpiring = $cTRUE Else - No Actions - (To add one, press 'Action') Occu.flagger - [ID 0012][Parent 0004] If $sHouse.occupied.timer > 0 Then $sHouse.occupied = $cTRUE $sHouse.occupied Init To $sHouse.occupied Else $sHouse.occupied = $cFALSE $sHouse.occupied Init To $sHouse.occupied Power up resumes previous state! Shouldn't be long to correct. Program cannot be combined into "Occ countdowner" program as it's timeframe end would zero occupied.timer Occu.vacantLightsOff - [ID 006E][Parent 0004] If $sHouse.occupied is $cFALSE Then Run Program 'Lights.inside.onOff.initiate' (Else Path) Else - No Actions - (To add one, press 'Action')

ISY/eISY does not poll programs or variables. They are event driven logic. An event or device sends a signal and the input drivers get the interrupt and process it, changing a variable or status somewhere. In the main processing that event is then handled by the main processing engine to check every program and only those programs involved with that event or variable and then processes the program logic (IF) involved. As far as I understand it, the whole sequence is event driven from end to end, and no polling is ever done or required. Basically, is is an interrupt driven system using semaphores to communicate those interrupts from I/O drivers to the main processing engine via processing table lists that tell ISY what to do next. This is one of the reasons ISY can be so fast....as it is not running useless checking on static programs that may be sleeping for days or weeks at a time.

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?