apostolakisl

I had a PC issue and had to redo the PC that was running nodelink. I never had any issues with nodelink and have 4 nodes on it and bunches of programs all integrated with those nodes. IOguy seems to have stopped supporting it. I copied my entire nodelink folder to a backup prior to reinstalling windows, but can't get it working after copying back to the redone pc. I was able to get a really old version of nodelink running but it is not linking to ISY properly. When I try to run the newer versions of nodelink I just get a flash of a cmd screen. I installed the latest .net from microsoft (.net 9.0 sdk). Anyone who could help me here with info on how to get this working I would much appreciate. I really don't want to go through the maze of programs and figure out how to redo it all and then debug it and so on. Below is what I get running the super old version of nodelink. It does link to the targets (DSC alarm panel, several webcontrol boards and the date program), but not to ISY. And I am using Polisy Thanks. 2025-01-12 14:30:45 - ISY NodeLink Server v0.9.34 started 2025-01-12 14:30:45 - OS: Microsoft Windows NT 10.0.19045.0 2025-01-12 14:30:45 - Web config server started (http://192.168.1.71:8090) 2025-01-12 14:30:47 - ISY Error: Web Error (FILE_NOT_FOUND) - Forbidden (profiles/family/10/profile/1/download/EDITOR/I_EDIT.XML) 2025-01-12 14:30:47 - ISY Error: Web Error (FILE_NOT_FOUND) - Forbidden (profiles/family/10/profile/1/download/NODEDEF/I_NDEFS.XML) 2025-01-12 14:30:47 - ISY Error: Web Error (FILE_NOT_FOUND) - Forbidden (profiles/family/10/profile/1/download/NLS/EN_US.TXT) 2025-01-12 14:30:47 - DSC: Repeater started on port 4025 [dsc1] 2025-01-12 14:30:47 - DSC: Connected to 192.168.2.141 [dsc1] 2025-01-12 14:30:47 - ISY Error: Web Error - NotFound (climate) 2025-01-12 14:30:47 - DSC: 5053CD[C][L] [dsc1] 2025-01-12 14:30:47 - DSC: 505 - Login Interaction (Password Requested) [dsc1] 2025-01-12 14:30:47 - DSC: EVL User Login - Password Sent [dsc1] 2025-01-12 14:30:47 - DSC: 5000052A[C][L]5051CB[C][L] [dsc1] 2025-01-12 14:30:47 - DSC: 500 - Command Acknowledge (005) [dsc1] 2025-01-12 14:30:47 - DSC: 505 - Login Interaction (Password Correct, Session Established) [dsc1] 2025-01-12 14:30:47 - DSC: Status Request Sent [dsc1] 2025-01-12 14:30:47 - DSC: Data Sent - 00191 [dsc1] 2025-01-12 14:30:47 - DSC TCP: Polling DSC [dsc1] 2025-01-12 14:30:47 - DSC: 50000126[C][L]61000128[C][L]60900231[C][L]6100032A[C][L]6100042B[C][L]6100052C[C][L]6100062D[C][L]60900736[C][L]6100082F[C][L]61000930[C][L]61001028[C][L]61001129[C][L]6100122A[C][L]6100132B[C][L]6100142C[C][L]6100152D[C][L]6100162E[C][L]6100172F[C][L]61001830[C][L]61001931[C][L]61002029[C][L]6100212A[C][L]6100222B[C][L]6100232C[C][L] [dsc1] 2025-01-12 14:30:47 - DSC: 500 - Command Acknowledge (001) [dsc1]

I have updated to the latest version and this still is not working. My car is currently charging and the phone app shows it as charging and currently 75%. This is what the node says. I assume "status" should be saying 75%. And of course the other info should be saying it is charging. If I click "honk horn", it does honk the horn. So clearly it is connected in some fashion. And the climate page shows 0 degrees c in the "node connected" field. That makes no sense. My phone app shows exterior temp as 81 and interior temp as 92. EDIT: After a bit, not sure how long, it did update to say it was charging, but still reporting 0% status.

I have used Java for other things without issue, but the admin console for ISY is very unstable and buggy. Lots of hidden windows that you can't find/close and it just hangs, refusing to shut down by anything other than a ctrl-alt-delete. Again, I regularly access ISY from 3 different computers and all 3 experience the same problems, so it isn't my PC. And then you have to keep re-installing the applet and updating it, and then I have had Java updates that don't install correctly requiring a complete wiping of Java from my system and starting from scratch. It would be so much nicer if EISY could host a local web page like so many others do.

Totally agree. UD mobile is great, but can never be an efficient place to do lots of editing.

Oh it would be so wonderful if the new version ditches the Java console. That thing stinks and has only gotten worse. Back in the old days, like 15 or 20 years ago, CTRL-ALT-Delete was something you just got used to doing to kill frozen apps. Skip to today, and CTRL-ALT-Delete is all but forgotten, but for the ISY Java console which, if left open for more than a few hours, requires a CTRL-ALT-Delete. You might say it is my computer, but then you would have to say it is all of my computers, like 5 of them that I commonly use for ISY. And it has gotten slower and slower. Trying to edit lots of programs just gets so painful waiting several seconds after every change to take affect and allow you to move on. Please let ISY have a snappy high quality browser based console!

In "From/To" programs, the "from" time and "to" time are both triggers. At those two times, the program will run. At the "from" time, when it runs, it will be true (and thus execute "then" clause), at the "to" time, it will be false (and thus execute the "else" clause. In between the from and and to time, the program will have a status of "true", and likewise, outside of those times, it will have a status of "false". Should the program be triggered from some other trigger besides the "From" and "to" times, it will execute the "then" or "else" accordingly. For example, you may have additional items in the "if" clause or you may have a separate program that calls the "if" clause on this program. However, without some 3rd party trigger, this program will do nothing except at those 2 times. So if the lights were somehow turned on at noon, this program would not try to turn them off until 11pm.

Re-entrant is correct terminology, however, around here we all call it "re-trigger". It looks like you have a handle on this and I am sure you will succeed in programming your ISY. There are lots of little tricks and best practices and unusual situations (like a reboot while a program is running) and the forum is a great resource to help you save time and avoid pitfalls.

I am doing essentially that exact same thing. It requires 2 programs so that it does not re-trigger and end the wait. Doing it this way avoids using variables. "All off" is the name of a scene that includes basically every light switch in my house. I use it to turn everything off with a single button press, but it also works great to have all the switches in the house beep. I also have a program that disables the program for an hour that I manually activate if I want to. Driveway Entry - [ID 0173][Parent 0172] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Disable Program 'Driveway Entry Trigger' Set 'All Off' Beep Set 'All Off' Beep Set 'All Off' Beep Wait 5 minutes Enable Program 'Driveway Entry Trigger' Else - No Actions - (To add one, press 'Action') Action run by driveway trigger. Seperated to allow for a 5 minute time out between entries. Driveway Entry Trigger - [ID 00AA][Parent 0172] If 'Blue Iris / Front Entry' Triggered is True Then Run Program 'Driveway Entry' (Then Path) Else - No Actions - (To add one, press 'Action')

At one time PLM's were not available. So fixing it was of course your best option. Since you can just buy a new one, I would do that. They don't cost much more than sending an old one off for repair, and then you have a new one. If you have a soldering station and easy access to the correct capacitors then fix it. In summary, I would buy a new one to have as a spare and put this one someplace as a just-in-case unit that if worse came to worse, you could fix.

Here is an IFTTT webhook I use for reference. This is not to send a text, but how it is configured would be the same, you would just call a different webhook.

wow, way back in 2011, man am I getting old. LeeG hasn't been around in a long time, but that guy new ISY better than anyone. I don't think he was an official full time UD employee, but I do believe he was contracted or in some way privy to the ISY internal code. Whenever he said something, it was always correct. Michel would regularly defer to him.

The discussion i recall.was like 10 years ago and involved UD people. Certainly response time would affect observed order. But the issue was doing math where order of operations matter. A long time ago before node servers, I wrote a bunch of programs using variables and math to allow for wild card date programs. Order of operations mattered. But I still use those programs and they have never not worked.

status is always a trigger when the status changes.

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.