apostolakisl

Or use the motion sensor as the trigger in the if clause. A motion sensor triggers a "control" upon sensing motion. "Control" means the origin of the signal is that device, however it might detect the world. So a switch -> you pushed it, a motion sensor -> detected motion, a water sensor -> detected water, an iolinc -> had the "i" part detect a change, etc.

I had some issues with my polisy that are quite possibly falling into this same category, though they seem to have been fixed. I use Automation Shacks Nodelink program and per Michelle it was overwhelming Polisy with open sockets and causing ISY to reboot and then in a later firmware was causing it to freeze. Reboots were about once a day and were preferred to freezing. After sending a bunch of logs to Michelle and having him remote into my machine, it appears that a few ISY updates later the problem was solved. Nodelink I do not believe has had any changes in a long time, perhaps years, so at some point it would appear that a change in ISY was the source of the compatibility issue.

Try downloading the offline java uninstaller. Then run the offline java installer. Then download the start.jnlp file from this forum. Java (at least in the format supporting ISY) is just crappy. I regularly have to mess with it. Back in the day, using ctrl/alt/delete to end some non responsive program was a regular thing, but those days are long gong . . . except for Java. And not on just one computer, but all of my computers. And not just once a year or something, but like once every couple weeks. And I have had to do the offline uninstall/install now about 3 times as well.

You have to have the old switch in the root folder. So first right click and remove from folder, then go to its new location in the tree and right click and you will see the "replace with" command. The new switch will have to be the same switch or an updated version of the same switch or you won't be given the option to select it as the destination of the programming.

2476D are quite old, likely at least 10 years old. The 2477D is the current model and has been for a long time. Some of your switches may have simply failed. The older switches had some issues with longevity and also just didn't work as well because they lacked radio communication. The new switches use both power line communication (inserting data into the houses power wires) and simultaneously through radio communication. These are called "dual band" and are quite reliable (the 2477d and 2477s). If there is no led lit up at all, the switch is either not getting power, or has failed. Possibly it just needs a reboot. To reboot, use a butter knife to pull out the disconnect tab at the bottom of the switch (it can be stubborn). This pull out tab will completely cut power to the switch's electronics. You must properly pull it out to ensure you actually disconnected power. When properly pulled out, it will stick out a couple millimeters and stay there all by itself. Leave it out for about 10 seconds, then give it a tap so that it pops back in. After a few seconds the switch will reboot. If instead of just popping it back in, you push it in and hold it in (deeply) for about 15 seconds as the switch boots up, the switch will do a factory reset. I would not do this right off since it may have had programming in it that is useful (assuming the previous owner had put useful links on it). I have never seen an insteon switch whose led just cycled up and down and up and down all on its own endlessly. Sounds like some failure mode. Possibly a reboot will fix it. Switches that go up when you push the up button and down when you push the down button are behaving as expected from that point. You need to figure out what the switch is connected to. This may be nothing if it was used to control a scene and not directly connected to a load (light). Switches that blink red after using them would be a newer switch. If it blinks red, that means it had been linked to another switch and the other switch didn't respond when you used it. Or it could have been linked to a controller (like isy) and the controller didn't respond, possibly because it isn't there (the previous owner took it with them). Insteon switches all have the ability to directly control a load (like a light) or directly control nothing but rather indirectly control things through data links to other switches (a scene). If it directly controls a light, then by itself, it behaves the same as any "dumb" switch. The cool and useful thing about Insteon is how it links up with other switches and controllers (like ISY). When switches are linked together you have created a "scene". Programming a simple scene can be done directly with the switch (download instructions from the internet). But scenes can be made extremely fancy and complex if you employ the use of an ISY. If none of this interests you, then you should pull the switches and put "dumb" switches back in. It is very close to a 100% chance that the house was wired for dumb switches. If you are clueless on how these things are wired, you need to hire an electrician. If you do it yourself, you will no doubt discover that many switches in the house were wired for 3 way or 4 way and thus you will need to figure out which wires go between which switch boxes. A simple switch that directly controls one load with no other switches is pretty easy. Insteon switches have 3 wires (plus ground). A white (neutral), a black (hot), and red ( load to the fixture). White and black must be connected for the switch to work. The red might be capped if that switch does not directly control a fixture.

As @paulbates said. Sounds like the light fixture is electricly "noisy". Might need a filter or a light that has cleaner electronics. And unless you have circumstances to control "off" that are more than just waiting a few minutes after last motion, you would be better off letting the MS be in control and skipping the program.

are these all insteon devices? If so, link them directly and get rid of the program. Direct links work much faster and avoid unnecessary clutter in your program tree.

I had my programs disabled on _4 a while back. I upgraded to _5 at that time and have not had any issues since, including the switch back to standard time (CST). Sunrise and sunset also are correct. I also do not understand the "secret" _1,2,3 etc version. Getting all your programs disabled is kind of a big deal depending on what they were doing and then if you have a complicated setup with lots of programs and specific ones disabled sprinkled about, it is no fun correcting.

May I suggest then renaming some of them. For example, instead of "zone expander", name it "zone expander trouble". It would make it butt obvious then. Cause. . . who has time to read the instructions?

I was investigating using some of the values on this page. But see a number of things that make no sense. First off, my Elk is connected to ISY and correctly tracking the armed status and the zones and all the usual stuff. But on this page, it shows the node server as "disconnected", but it clearly is connected. It also says "false" on a bunch of things like having an output and input expander (which I have several of) and ethernet as "false" despite it clearly being connected. Also "dislplay message in keypad" is false, yet I have messages being displayed via ISY and this node server.

Probably overkill doing both is zero or is not zero since the odds of it being exactly at 0.0 and staying at 0.0 are slim to none, but whatever.

I don't really know what all of the names of your stuff is, but if it is loading real time weather data into a variable, you would presume that the data would change at least a little with every update, especially if it is reading to the tenths place. You could use that as a retrigger for your monitoring program instead of a heartbeat. As an example, I have wireless tags monitoring a walk in freezer and fridge at my church. I have a program that retriggers every time the temp changes. If it fails to retrigger after 45min, I get an alert. For that program to fail, both the wait clause would have to fail and the wireless tag connection would need to fail essentially simultaneously. As a precaution, I could add a few "if" items such as if time is 6am, 12noon, 6pm, and 12mn to ensure I don't go more than 6 hours without an alert in the failure event I mentioned. Freezer Online - [ID 009F][Parent 009D][Run At Startup] If 'Walk Ins / TGOC Walk-Ins / TGOC Freezer' Temperature is 0.0°F Or 'Walk Ins / TGOC Walk-Ins / TGOC Freezer' Temperature is not 0.0°F Or 'Walk Ins / TGOC Walk-Ins / TGOC Freezer' Humidity is not 0.0% Or 'Walk Ins / TGOC Walk-Ins / TGOC Freezer' Humidity is 0.0% Then Wait 45 minutes Repeat Every 1 hour Send Notification to 'Lou and Stuart' content 'Freezer Monitor Offline' Send Notification to 'Denis Phocas' content 'Freezer Monitor Offline' Else - No Actions - (To add one, press 'Action') To test your program you can right click on the program that is supposed to be running in a loop and hit "stop" and then see if your program alerts you.

It also occurred to me that you might be able to use the action of the program itself as the "heartbeat" depending on what that action is rather than having a variable that serves as the heartbeat. In other words, if the programming is expected to change the state of something, you can monitor that the state of that thing is changing rather than the state of the variable is changing. OH YEAH! The variable you use needs to be a state variable. I don't think I mentioned that. An integer variable will not work.

Some of the node servers have a heartbeat, one of the values just goes back and forth between 0 and 1 every 60 seconds. If (run at startup) status of node is 1 or status of node is 0 Then wait 5 minutes send notification The value changing every 60 seconds restarts the program so the 5 minutes never finishes unless the node goes offline. You could probably do something like that instead of what I wrote above If whatever you want Then repeat every 1 minutes whatever you want repeat 59 times set variable to 1 wait 1 minute set variable to 0 Now you would have a variable that is a heartbeat every 1 minute and you could just have a second program to send you a notification. But if you have a concern about it stopping at DST or whatever also add some hard start points for it If (run at startup) status of node is 1 or status of node is 0 or time is 8am or time is 8pm Then wait 5 minutes send notification

You could have your repeat set a variable to say 1. Then you could have another program that sets that variable to 0 on a schedule, like every morning at 8am, or you could have it run more often, but it needs to be a schedule, not a repeat. Finally, your last program would check periodically to see if that variable is one or zero. Depending on how often the program repeats and when your program resets the variable you would need to adjust the times for this stuff. For example: If whatever Then repeat every hour whatever you want set variable to 1 If time is 8am Then set varialbe to 0 If time is 9am and variable is 0 Then send me an email

The new rpi came. I stuck the sd card into it and it booted straight up. I moved it over to the same IP it had before and rebooted. The one and only node that didn't mysteriously get deleted populated as expected. All the others I needed to delete and re-add. I actually had 6 nodes on there, so 5 deleted. The one that didn't delete had nothing particularly different about it. It was neither my first nor last node that I created on PG2.

I'm not sure what the deal is, but I rebooted ISY and it blinked the two lights indicating no network. I changed the ethernet wire and the plug on the switch and rebooted again and it is fine. So, I guess that was a wire or switch issue. Hard to explain since it has been all the same for several years and no one was anywhere near any of this to bump into it or yank on anything. Also I made no changes to the network physically or setting wise in many months. For good measure I replaced the power supply and moved it to a UPS. I don't think any of this is related to the nodes disappearing. Upon further review, it appears 3 of the 4 nodes run by PG2 rpi got deleted from ISY. Then all the programs that had any mention of those nodes turned yellow and stopped running. My nodelink nodes are fine. New rpi came today, so we'll see what happens when it goes back online. Curiously, I also have Nodelink running on that rpi. I have CAI webcontrol, Sun Position, and ISY Data all running on nodelink. And some of the fields on those nodes populated even though nodelink is not there. Specifically, the hour and minute in ISY data are populating and the sun position is populating. I suppose those nodes are pulling some data from nodelink itself and some data from ISY. None of the fields for CAI webcontrol populated, which makes sense since ISY clearly has no internal knowledge of any of that, but ISY does have a clock and does track sun position.

Well now ISY went down. This is at my church so I'll have to stop and try to see why it is down. But I am able to access the network, so it is not a power outage or network outage. Anyway, I definitely did not accidentally delete the node doing any of those things. I am familiar with how to delete a node and promise you I didn't. But now that ISY has shut down for some reason I am wondering if ISY is having an issue.

This is a 994i and an rpi running PG2, but the PG3 forum is closest I guess. Anyway, my rpi died, I ordered a new one, but while waiting, ISY deleted half the nodes. I do not understand why it did this. This creates issues since any program that mentions those nodes becomes non-functional. If I fix those programs, then they will need to be fixed again when I get the new rpi installed. But why would ISY delete a node just because it isn't responding at the time? And why only some of the nodes? I would expect that ISY would just leave the nodes unpopulated, not delete them. I do not know for sure how long it took from the time the rpi went offline until the nodes were deleted. There have been several times that rpi went offline for a day or something in the past and this did not happen. This time it has been over a week and the new rpi is supposed to come tomorrow.

half red = last run was false half green = last run was true solid red = currently running false solid green = currently running true When I did "upgrade packages", I also didn't believe anything happened as it did not appear to reboot. However, it showed _5 as the version number and the correct time for having updated.

I have suffered the same issue. First off, there are some revisions of the current firmware that supposedly fix this bug. Go to https://polisy.local:8443/WEB/sysconfig.txt and find your current firmware. You will see a section that looks like this: isy-5.7.0_5 Name : isy Version : 5.7.0_5 Installed on : Thu Oct 26 20:04:26 2023 CDT Origin : misc/isy Architecture : FreeBSD:13:amd64 Prefix : /usr/local Categories : misc Licenses : Maintainer : michel@universal-devices.com WWW : UNKNOWN Comment : ISY Port to X (IoX) The latest version is 7..5.0_5 My system was on the _4 version when it spontaneously disabled all my programs. Please do an "update packages" to get the _5 version which I pray fixes the issue. I am going to assume you have programs that are supposed to be disabled and that you have lots of programs and that figuring out which ones are supposed to be disabled would be a major PITA. In that case, hopefully you have a recent backup so you can restore the programs to proper enabled/disabled status. If it is easy for you to know which programs are supposed to be disabled, just go to the program summary page, block highlight all the programs, right click, and click enable. Unfortunately, my backup was 6 months old and my system had changed. First I made a current backup of the system. Then I restored my 6 mo old backup, took screen shots of all the programs showing enabled/disabled, then loaded the current backup back onto the system. I block highlighted all the programs and enabled them, then went back and disabled the 30 or so that needed to be disabled using my screenshots. Then I made a new backup just in case _5 version hasn't actually fixed the issue.

I'm on Polisy and Nodelink is working. I am running DSC, CAI webcontrol, and ISY data on it.

@Geddy Update Packages did nothing. I waited well over an hour and nothing. Now today, it spontaneously disabled all of my programs (except 2 for some reason) and they aren't correcting after multiple reboots. I am very unhappy. Nothing is working and I have a huge number of programs and figuring out which need to be disabled will be impossible. My most recent backup is 6 months old, but perhaps I can restore it, take screenshots of the program summary page and then restore the current backup and set the programs. I can ssh into polisy but don't the proper commands to issue an upgrade. EDIT: I guess it did update even though I never had to log back into the admin console because I did the command above and it shows _5 now. Mind you, I did not do an update at the time of the programs being disabled. It just happened for some random reason at some random time.

yes

I don't know what S21 is. I just powered up the Sensibo, pointed the Friedrich remote at it and pushed power button. Immediately on the Sensibo app on my phone it showed configured and ready to go.