apostolakisl

Well, yes, but also the ones with bad caps consistently fail right at 2 years. So, assuming you put it into service at the time you bought it, then this would be spot on for a cap failure. Should the version number be prior to the new design, that together with 2 years in service would confirm with very high probability that you have a dying plm. @Michaelv

As is the case regardless of how the PLM is connected, when you change out a plm, you have to do a "restore plm" from the ISY console. If you go back to the old one, then you once again have to do a "restore plm".

So the other question is if you do a soft reboot of ISY, does it affect the power on the internal header that you might be using to power your rpi?

@Michel Kohanim Can you comment on the pin out for the internal header socket? specifically, uart or rs232 pins that might be there? Also, would it overload the power supply if you had both a z-wave and a pi zero at its lowest baseline power draw (.4 watts per my google search).

I take it then that the header socket there on ISY does not have any RS232 or UART connectivity? I believe somewhere you mentioned that Michel gave you the pinout? Looked up Raspberry PI zero power. Without any accessory stuff on, (wifi, hdmi, etc) it only uses .4 watts.

Very nice work. Wondering, is there not somewhere that you can tap into the rs232 terminals on the ISY board instead of doing the U-Turn Cat6? Also you are tapping into that header. Does this not interfere if there is a z-wave board? EDIT: Trying to look at photos to figure out. The z-wave board goes into the bottom row of sockets and it looks like you tapped into the top row. Are the top row and bottom row sharing the same electrical contacts? I don't see enough pins soldered into the board for the top row and bottom row to be different and obviously the top row isn't just empty since you are using them. EDIT AGAIN: I also have to wonder if there isn't somewhere you can tap directly into ISY UART and avoid the RS232 entirely.

You may be right. It wouldn't make sense to list it as compatible with 50hz if it weren't compatible with 220/240v. There only a handful of obscure countries in the world that use 120v/50hz.

Options as I see it. 1) Get your hands on an Insteon PLM, use a voltage converter and see if it works. 2) Ditch Insteon and go with Z-wave along with ISY 3) Ditch ISY and stay with Insteon using some other non-plm interface. The HUB is listed as working with 50hz, however it only lists125v Personally, I suspect the PLM with a voltage adapter probably will work based on RF.

That sounds like what my assumption was. Transmit on zero cross, accept at any time.

@larryllix I was thinking about it and without the rf, there is just no way for the devices on the different 3 phase to be in sync. None of the 2 or 3 phase appliances (ie hot water heater) would be able to pass plc across since they won't share zero points. It has to be the rf. I suppose it could be that the rf transmission occurs on the zero cross, but receipt of the rf is independent of the AC zero point. I assume you could tune an rf receiver into the insteon frequency and plug that into an oscilloscope on one channel and on another channel watch the AC current for Insteon traffic.

Did not know that. With all the newer Insteon stuff being 50 or 60hz, something has to give here. Of note, I use Insteon on 3 phase building and that works just fine with various devices all out of sync with each other on zero crossing points. I even have two separate 3 phase buildings linked together with a single rf device. To simplify the description, imagine a 200 foot extension cord with a dual band device at the end. I is is plugged into building A, stretches across the yard and ends next to building B, where another dual band device is located next to it and plugged into building B. This works perfectly and keeps the two buildings electrical systems isolated.

Dual band would likely take care of that problem. All the other insteon stuff is designated as 50 or 60hz, so once it gets picked up by the first device it would go on the power line and rf even if the plm didn't. Just not positive if 120vac 50hz would be OK for the power supply in the PLM, assuming you used a 240 to 120 adapter.

The PLM is 120vac 60hz . . . if you can get one. They are not currently being produced. The official reason is chip shortages. Not sure what would happen if you used a voltage adapter

That is the sure fire way to do it. Or "hide" your plm. You could plug it into a signal blocker, Or use a UPS, unplug the UPS from the house and cover the PLM with a metal electrical box or some other metal enclosure to attenuate radio. Usually a UPS will block power line communications even if plugged in, but you might as well unplug it just to be sure. The radio attenuation is still going to be a question mark. Trouble with trying to just have your house be "quiet" by not using any insteon devices can be sabotaged by things like a program running or a motion detector. Possibly even a heartbeat from a battery device.

Any Insteon traffic while doing a PLM links check will mess it up. You almost have to take the PLM to a location that has no Insteon devices. At this point, your pre-check is almost certainly wrong, so any comparison now is impossible. More importantly, are you able to link the devices that you were having issues with before?

Might consider doing a factory reset on the PLM and then restore it. Reason being that orphan links are common. You could have dozens of them. I have done that to my PLM a couple times over the years.

Yes, I lost my favorites. I had to do them all over again. After it did sync, I clicked "test local network" and that was successful. I don't have time right now to mess with it anymore. EDIT: Also, I would suggest an option to have the app open into favorites directly.

@Javi None of the issues you speak of exist. I did not have a / at the end of the IP. I have not changed the firmware since the last sync. In fact, I changed nothing between something like 4 attempts to sync and then finally it sync'd.

@Javi after I added local network, it had to resync. Why? And now it is failing to sync saying I have an incomplete firmware upgrade. It syncs just fine using the portal. After several attempts, it finally finished the sync. But several times failed for various reasons.

You need to understand how ISY works. The items in an "if" clause are triggers as well as conditions. Whenever any of the items in an "if" clause happen, the program "triggers". At that point, if the program is currently running, it terminates where it is and starts over from scratch. It will then evaluate the entirety of the "if" clause and the result will either be true or false. ISY programs only are running at the instant of a trigger, or, should the "then/else" clause contain waits or repeats, it will continue running while those are valid. IF time is 8am . . . .8am will be a trigger and will be true only at that instant. This program can never be true except at that instant. If status is 25% . . . any changes in status will be a trigger, true if it is 25%, otherwise false If control is switched on . . . pushing the "on" side of a paddle is the trigger, no other action on the paddle does anything. Similar to "if time is 8am", it is an instantaneous event that is only true at the instant ISY "hears" from the switch that someone hit the on paddle. A program can contain lots of items, when any one of those items triggers, the entire "if" clause is evaluated as either true or false based on the entirety of the conditions. IF time is 8am . . . . trigger is 8am, it will only be true at that instant If time is from 8am to 10am. . . . two triggers, 8am and 10am, but, It will be true if any other trigger happens between 8 and 10 If time is 8am and control x is switched on . .. .never works both a single time event and a control event are "instantaneously" true. So they would never happen at the exact same time. Your original question seemed to say you had outside bounds that you wanted your lights to turn on. So, you can set those outside bounds by saying From x time to y time. Now the program will never be true outside of those times. Now add, in other conditions, understand, these other conditions will also be triggers. and time is from sunrise minus 20 minutes to y time. Now you have 3 triggers, x time, y time and sunrise minus 20. All 3 will trigger the program. x time and sunrise minus 20 are "true" conditions, and y time is a "false" condition. For a program to be true, all conditions must be true at time of the trigger. The program is not constantly running. Only runs at trigger events. From 8am to 10am does not mean the program is running from 8am to 10am, it only runs at 8am and 10am. Realize that if something else turns the light off after it has been turned on (like you manually turn it off), it will stay off. This program only runs at those 3 trigger times. Similarly, if you turn the light on outside of those conditions, it will stay on.

@Javi Enjoying the continued new features on UD Mobile. I am using the "command" function for favorites and very much like it. My concern is that it is easy to "butt dial" or "fat finger" a command. My suggestion would be to allow for "2 step" activation where you click once then it says "are you sure" and you click again. Perhaps this is an option when you set it up. I am also a bit confused on using this. To use a command favorite, I set up a regular favorite first, then add the command function. I am a little confused about this in that the original favorite and associated node doesn't seem to necessarily be tied to the ultimate command. Am I missing something?

If your PC has eventghost running on it, you can use an ISY network command to trigger a macro on eventghost and that can run a python script that executes a shutdown. I would suggest having the PC on the same LAN as ISY to avoid any port forwarding/security concerns.

@FarmerGeek It appears that your program doesn't work because the door that is violated is then restored prior to 10 minutes. This re-triggers the program and is now false and the "else" clause is empty. If you moved your "wait" and everything after it to the "else" clause it would probably work as you intend, though I'm not 100% sure on that since I don't fully understand the intent. It is easy to see what is happening by simply watching the status of the program in the program tree in ISY console while you violate and then restore the zone. You will see the program go from inactive (half red or half green . . . in your case half red), to solid green (running then) when the zone is violated. It will stay this way as long as the zone is violated or until 10 minutes expires (at which time it will turn half green if the zone is left violated). As soon as you restore the zone, the solid green (indicating the wait is running) will turn half red (indicating the program just evaluated to false and terminated. If you put the wait etc in the else, the wait won't start until you restore the zone, at which point it will turn solid red for 10 minutes and then half red (unless you violate the zone again prior to 10 minutes at which point the process starts over.

I have found that searching the forum is very difficult. I have on several occasions tried to find my own posts where I knew I answered a question and struggled to find it using the forum's own search function. I often have better luck doing a google search to find something on this forum as opposed to using the forum's own search function.

I agree you wouldn't want them all listed out on the home page. As it is, the home page is kind of long. A folder like structure where you drill down seems logical. Only "nodeservers" title would be listed, then you click on that to see all the individual nodeservers. Not sure why a forum needs to have every title listed on the home page.