MrBill

correct.

I heeded the warning on button groups screen that you provided a screen shot of and never used button groups, but i assume so. in the case of my front lights at least one scene is On at any given time, that may be a bad example. You could add multiple buttons as scene controller for the same scene (just answer no to the "___ is already a controller, do you want to add it as a responder" question, then set one of the buttons as Non-toggle on, and the other as non-toggle off.

Create scenes. For example, my outside lights operate using 4 scenes: Day, Evening, Late night, Bright Each scene contains the same devices, AND the KPL buttons for the other 3 scenes. The button to turn the scene ON is a controller, the other scene buttons are responders. Set the KPL buttons as "non-toggle On" When I press Bright for example the other 3 buttons will be turned off as the actual lighting devices are set for bright mode. ("day" is known as day and not known as off, because there's an outdoor outlet that turns on in the daytime.) Late night is a repeat of the above with the last node as the controller. (note: It's an admin console screenshot, just without the blue background.)

Here's a old reddit post on 2443 teardown that's been getting linked frequently the past month: https://www.reddit.com/r/HomeKit/comments/912rjm/insteon_hubpro_teardown/

open a ticket: support@universal-devices.com

honestly if @ctviggen1 just updated the ISY he probably went to a Polisy... nonetheless... I wouldn't spend money upgrading a 994's 300 series controller to a 500 so that you can use 700 series devices, that doesn't make sense at this point in the game. If someone want to start adding z-wave literally every piece should be 700 series. Save all your upgrade money and buy a Polisy if possible with a 700 series controller board.

There is an 8 button S in existence. You can also change faces from 6 to 8. (there's a short button pressing experience to switch the KP body for the alternate face.)

Check ebay for insteon. prices for items like 2477D are coming down due to the flooded market, some of the specialty items are still running high tho.

If you've previously had portal connected to this ISY use Help > Manage modules to get your portal tab back. If you've never had a portal subscription, Use help Purchase Modules. I think it's a $1 charge to add portal. Polisy comes with a 2 year subscription to the portal, but it must be manually redeemed. What you can do is use https://my.isy.io to start a free 30 day trial subscription. After that email support@universal-devices.com including your UUID number and tell then you have a new Polisy and need the 2 year subscription added. they will manually adjust the end date of your subscription.

@ARyder01 the reply by @DennisC just made me realize the problem here. Your My programs folder has a RED stripe. That tells me you have a FOLDER condition enabled on that folder. If a folder condition is False (yours is because it's RED, not GREEN) nothing below that in the tree will work. Even when run manually like @DennisC suggests. Folder conditions are unlike Program conditions in that anything below a false folder condition will never be seen, even if run manually or run by another program. I'd recommend staying away from folder conditions at the beginner and intermediate level, wait until you're really good at programming to use. They trip a lot of people up.

I didn't see this above, but it could be there because I just quickly scanned. The PLM must be powered up and connected before Polisy is booted or it will not be detected. Plug the PLM in wait at least 30 seconds for it to boot, make sure there is a solid green light... then start Polisy up.

Programs are always running. The IF statement will CONSTANTLY be evaluated to either True of False. The instant an IF statement becomes True it will begin to run the THEN statement, conversely the instant the IF statement becomes False it will begin to run the Else statement. Will and IF or then get interrupted while it's running? If it has a wait then yes it's possible the if statement will never complete. Consider this hypothetical program If Motion detector status is on Then Turn on light Wait 10 minutes Turn off light Else Nothing If the status of the motion detector becomes Off during the 10 minutes wait, the light never turns off, because the wait was interrupted. ------ If Motion detector status is on Then Turn on light Wait 10 minutes Turn off light Else Turn off light in this case we added turn off light to the else. If the motion detector turns off during the 10 minutes wait the iff will become false and the light will immediately turn off because of the else, or it will turn off after 10 minutes if motion is still on. -- The above is a bad example, because most of the motion sensors we use don't work exactly like that, and we'd use a different trigger called "Control" rather than "status" in a real motion sensor program. Control is a trigger, and senses the on or off state but doesn't reverse it's state. -- Programs such as schedules, are true during the scheduled period and false outside the scheduled period. If From Sunset to Sunrise (next day) then turn on porch light else turn off porch light --- There's also methods to ensure the program always completes even if the status of the if changes. Re-using the first example: Program ONE If Motion detector status is on Then Run Program TWO (then) Else (nothing) -- Program TWO if (blank) then disable Program ONE Turn on light Wait 10 minutes Turn off light enable Program ONE Else Nothing Using a method such as this allows the program to complete even if the status changes. So in summary, yes programs are always running and the IF is always being evaluated. If the program is paused by a wait statement, it's possible the program never completes.

Try deleting these temp files and see if that resolves your issue, probably just the 2nd and/or 3rd would do it, I usually just search udi_* in that Temp directory and nuke em all. find the following files in Java temp directory (on Windows: c:\Users\[Username]\AppData\Local\Temp) and delete them. Or, you can simply search the computer for udi_*.* file patterns: udi_tree.state udi_frame.state udi_pgm.state udi_finder.state udi_launcher.state

What is Catlight-Off Power Switch? Do you see it changing on the "Main" device tree as the state changes? You likely want "control" instead of "status", but status should work if the status is actually changing.

Open the Event Viewer window and set the dropdown to level 3. Also post the specific sensor you're dealing with, somone may have more info. You can sell them used on ebay for more than you paid at the moment.

@ISY4Me Disclaimer: I did quit reading a few posts ago, but if you have any 1011 icons to the left of any battery powered devices. Deal with that. It causes problems. @larryllix did mention it in his second reply. Unwritten instructions to battery devices reek havok on insteon communications, because the ISY keeps trying.

Probably copied from one of my examples. I like to restart the Then, so that if i don't deal with it today I'll get reminded tomorrow if the issue still exists. If it doesn't still exist (i.e. new heartbeat received) that resets the clock again and kills the nag. Some of my 2421's are horrible about dropping heartbeats.

Old threads are now closed on purpose. While that one is not too bad, the point is most of the information in threads over 1.5 years old is out of date. It's best to start new discussions, referencing old when appropriate. Are you a programmer/developer wanting to be pointed to the developers group and developer documentation, --or-- are you hinting that you hope someone will soon create a node server?

In that case you can simply delete that line from the program. It doesn't do anything.

For the most control use a program: If Motion 1 is switched on (use control not status) or Motion 2 is switched on Then Turn Scene on wait 10 minutes Turn Scene off The time will restart if more motion is seen during the delay, however battery powered motions don't trigger every single time motion is seen, they have a re-trigger delay to prevent the battery from being quickly drained, so that's another factor.

@oskrypuch Without testing I don't think this is doing what you want it to: Heartbeat Kitchen - [ID 021B][Parent 0135] If 'kitchen / LEAK - Kitchen-Heartbeat' is switched On Or 'kitchen / LEAK - Kitchen-Heartbeat' is switched Off Then Send Notification to 'xxxxxxxx - GMail' content '$my_alert' Wait 26 hours Send Notification to 'xxxxxx - Text' content 'LEAK Heartbeat MISSED' Run Program 'Heartbeat Kitchen' (If) (then) Else - No Actions - (To add one, press 'Action') Specifically I'd make the change in RED. When it run's If as you have it set, the if will be false. "is switched" is looking for the signal to come in, that only happens for less than 1 second each day. Therefor when you re-run (if) the If will be false and it will execute the empty else. If you change as indicated above you will get a repeat nag in 26 hours if the heartbeat sill hasn't arrived.

Click on the IF statement, Click the schedule button, the last dropdown in the TIme line defaults to "Time", change it to last run and you should be able to figure out the rest.

I agree with @Techman it's probably the power supply. I'll add three things tho, 1) there's a batch of power supplies that were shipped with 994's that tend to fail. 2) the blue light can still come on when the supply has failed (it doesn't take much power and is connected directly to the power input). 3) you can try a wide range of power supplies, from troubleshooting in the wiki:

A long time ago, I started writing a node server to log data to Google Sheets... I lost. ☹️ This is an area that's really lacking, it would be outstanding if we had a method to collect data for external analysis. I might be missing something, but why would you want to use state variables? If the variable needs to trigger an IF statement, i would understand the use of state variables, if its a just a counter/data collector why would a state variable be used? I'm sure it's less important on speedier Polisy but back in the day that I was using state variables for everything and had 200+, I ran into problems on the 994. State variables do use more processing power than integer variables due to the fact they are triggers.