apostolakisl

As I mentioned, it works like it has indexed all of the events contained in all of the programs. Should something in the index match a current event (not a condition, but an event, or trigger if you will) then it executes the program(s) that contain the item in question. ISY receives an event => Event is checked against the indexed list of events => matches point to program(s) containing event => program evaluates "if". EDIT: If you think of it as looping through all the programs, you are going to expect it to execute on the status of the conditions instead of only the "event" of the condition. "For sure . . " Not according to the people at Universal Devices when this was discussed many years ago. But in my experience, I have never seen a then/else clause not execute in order. But I have been told it is possible. Perhaps if the first line is computationally complex and the second line is not, the second line might finish before the first line. But I haven't seen it.

@Guy Lavoie I have done a good bit of PLC programming and a ton of ISY programming. The PLC works quite differently. PLC clearly loops through the code and executes based on the state of any given line. ISY does not loop through the "if" statements looking for conditions. It works on triggers. Again, I don't know how the actual engine works, but if you think of it this way, it will get your programs to work as expected. So, here is how I think of it: Consider that all of the if statements' conditions are indexed. For every event that ISY encounters (a node value is changed or the clock ticks to the next second), it goes to that index and sees if any program matches that event. If so, it executes the entirety of the program. If two(or more) programs match that event, there is no telling which it will execute first. Within a program, I have been told that ISY will not necessarily execute then/else clauses in order. Meaning if you have 2 or more lines in a then clause, it could execute them in any order. However, it has always been my experience that the lines in an then/else clause do execute in order. I have a number of programs that do math where order of operations matter and they always work correctly.

Yeah, I should have been more clear. No two "control switched x" can ever be true simultaneously, but the "if" clause can be true if you connect them with "or". And for anyone new to ISY, a little trick is to connect two opposites with control. In this fashion, one program will be able to do 2 things. In this way, both hitting the on paddle and hitting the off paddle are triggers. The on paddle goes true, the off paddle goes false. If control switched on or not control switched off then do something else do something else

I'm pretty sure a blank "if" clause evaluates as true during a "run at startup" and hence, you get execution of the "then" without any "else" clause needed.

Typically you disable the program rather than using lots of variables. Also, for flags, just use a PGM status rather than a 0/1 variable. Pgm1 If motion And PGM on vacation false Then Run then pgm2 Pgm2 disabled If blank Then Disable pgm1 Turn on pump Wait 15 minutes Enable pgm1 Turn off pump Only caveat is if you happen to reboot during the 15 minute wait, the program will be disabled at start and be stuck. So I use a single program that runs at startup to ensure that all of those programs are set to the correct state. As a side note, programs with blank if will run true if set to run at startup.

I didn't do an update. I put it in the same slot as the previous, but completely different Tesla node was. Then did a fresh install of the new one. I just drove the car and it currently shows good data. I will see what happens in a bit and send a log.

If I put it in a different location I will need to rewrite all of my programs. I just don't see why it would have a problem at one node location and not another. They all function the same using the same code and same hardware. And yes, unknown and not reported is what it says on the admin console until I hit the update button. Then after a period of time, maybe 10 or 15 minutes, it reverts to unknown/not reported

Not sure the context of "work as expected". But ISY is event driven, which is not like C. It is not driven by unchanging conditions, it only triggers on events. Your if clause must contain an item that has experienced an event or it will sit idle. Things that will make an if clause go include: 1) IF Status . . the status of the device must CHANGE 2) IF control . . . the specific control command must have happened. "control on" for example means the on paddle was pressed. Dimming up, switching off, etc do nothing. 3) Run at startup . . . startup of course is the trigger 4) A different program can cause the execution of an if clause with a "run if" command Once the "if" clause is triggered, then all of the conditions contained are tested for true/false status. Understand that instantaneous conditions like "control switched on" will always evaluate to false unless the trigger itself was that event. For example, a program that contained two "control switched . . " lines would never be true. And there would be no point in having a "run at startup" for a program that had a "control switched . . . " command since it would always be false (unless for some reason you wanted that program to run the else at startup). The above "repeat while" command will only be repeating if the then/else clause got started somehow. Either by the programs on "if" clause being triggered, or by some other program sending a "run then/run else/run if". Or of course a run at startup.

Did you try clicking on the "network" folder at the top of the tree on the left to bring up the itemized device lift in the right pain? You can sort by Insteon address and confirm that indeed the device isn't still there and just hiding from you in the regular tree on the left. I suspect you will find the device is there and thus you can delete it and then re-add. If the device truly isn't there, and you say it is in the links table, do you mean the links table on the PLM, or the links table that ISY believes is on the PLM? If it is only on the actual PLM and not the ISY link table, then you could restore the PLM.

This is what I get in if mobile

Everything seems to work. Then, after a few minutes, all the fields change to unknown or not reported and I have to hit the update status button. And after hitting update, it only updates the screen I'm on. The climate screen for example continues to say unknown after hitting update on the charge screen. Even though it reports the last update as 0 minutes ago.

I just went to update to what is apparently finally a working version of the node and it would seem that it is asking me to buy it again.

I third the solution of making it a slave switch in a 3-way scene.

Is anybody actually working on this? It has been like 9 months now.

The errors riebel is getting is not from the wireless tags, it is the PG3 node.

Turns out, at least in my case, I didn't. After about 10 minutes, it started working with the same key.

As is usual for these things, it is as clear as mud. I subscribed to the 3.0 version and gave them my cc info and they say it is active. But I still get all zeros. I am still using the same key and as far as I can tell, that is the key you use. I restarted the node a couple times and still all zeros. I will give it some time to activate perhaps.

I came back from vacation to find my openweather map reporting all zeros for everything. I restarted it, even uninstalled and reinstalled. I don't know what to try next.

Indeed, I just missed it. And curiously, on this computer, both of the water fountain icons above are blue. Computer at home, one is red and one is blue. This is curious. No matter, they are the correct color on UD mobile.

But advanced options is the only way to use a custom icon even if you don't want to map to any particular value. I ended up putting a node in there that is always off as a work around.

This one tile lacks several of the choices like advanced status config. Edit. Looks like you must have a display node to get advanced options. However also it is showing the wrong icon in upper left corner. That is supposed to be a light bulb. It does show a light bulb after a while.

For reasons that aren't clear, they now show up as blue and red despite doing nothing.

Never mind, deleted the node and started over and this time it "took"

PG3 console shows it as connected with 2 nodes. ISY shows disconnected and no nodes. The sign in to wireless tag went fine and it said it got authorized and indeed I have two devices. Tried a full reboot of Polisy and did not fix it.

I got it to work with two url's one for each color. But what is not clear is why they both show up as blue on this website and the one is red and the other blue on UD mobile. https://lh3.googleusercontent.com/d/1YggIgfB681Rp3bLwxBVPOA2wNQY6Gpgv https://lh3.googleusercontent.com/d/1iBEDJtkUlm3NYaSeevobRod6QGrtY558