MrBill

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.

so the programs are working? Or he refilled it?

Maybe you just got a bad out of box unit... even with the best manufacturing processes and quality control that can happen. that doesn't mean the entire product is garbage. UDI stood behind the product and gave you a refund. You would have a right to be the worked up if you lost money on the deal... YOU DIDN'T... UDI cheerfully refunded you-- something I've noted over the years is a routine practice at UDI for whatever reason.... they just refund... it's simple.

I agree, I liked the first post...

If you've been following along in Smarthome section of the forum you would know that Michel has submitted and offer for rights to produce PLM's and is in negotiations beyond that, but NDA prevents him from disclosing much. And yes UDI did design a super PLM, that never made it past prototypes because smarthome backed out of the deal.

I can tell you that in my experience 2421's are the worst of all the model for skipping heartbeats. Most of the time I just go test the sensor when a heartbeat misses, and it doesn't the next day.... if I get them two or three days in a row from the same sensor then either i remove the battery and reinsert it which will get the heartbeats going again,,, or if it's an older battery (day) and/or has high transmission counts.. then I'll just change the battery. It's never been stated, at least officially that I've come across, but my personal belief is that it's designed so that once heartbeats stop there's still enough battery left to send open/close transmissions for awhile. I also have an ISY program for each sensor, that I trigger manually from a Home Assistant Dashboard to reset the counters when the battery is changed: FrontDoor.reset - [ID 01A4][Parent 01B5] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Resource 'NotificationNS.DoorTrouble._resetCountersBegin' Wait 1 second Resource 'NotificationNS.DoorTrouble.FrontDoor' Wait 2 seconds $iDoor.FrontDoor.HBmissed = 0 $iDoor.FrontDoor.HBmissed Init To $iDoor.FrontDoor.HBmissed $iDoor.FrontDoor.BatteryDays = 1 $iDoor.FrontDoor.BatteryDays Init To $iDoor.FrontDoor.BatteryDays $iDoor.FrontDoor.TransCount = 1 $iDoor.FrontDoor.TransCount Init To $iDoor.FrontDoor.TransCount Wait 2 seconds Resource 'NotificationNS.DoorTrouble.FrontDoor' Wait 1 second Resource 'NotificationNS.DoorTrouble._resetCountersComplete' Run Program 'hb.FrontDoor' (Then Path) Else Resource 'NotificationNS.DoorTrouble.FrontDoor' The four notifications it send end up looking like this: (read from the bottom up) Sends 4 notifications, a start announcement, counters before the reset, counters that have been reset, and a complete announcement. The purpose is once or twice I've reset the wrong counter on accident-- this way I don't lose totals and can manually change the variables to put them back if i need to. In this case that sensor is a 2845 and sends low battery, that's why it was getting changed--given the day and transmission count I suspect that wasn't a fresh battery in the battery stash-- but the sensor did send low batt, so I changed it.

This one https://smartenit.com/shop/plm-serial-cable/ there's also a method to buy an RJ45 to BD9 adapter off amazon and use it with the cable you do have. Costs less but requires configuring via pinouts in another thread.

Just factory reset it per the instruntions in the 2413s manual... typical unplug, hold set button, plug in, wait for long beep to stop. You need the original cable that came with the PLM, not the cable that came with the ISY. One end has a DB9 serial connect, the other an 8Pin Ethernet style plug... The connection from 2413s to ISY is NOT eithernet... even tho Port A on a 994 might make you believe that.

Both of my Polisy's worked right out of the box, not sure what happened with yours. Both have been updated since Day 1, the first was in the second batch that were shipped. I don't think Polisy is junk, sorry that you do.

Java 8 (oracle) from https://www.java.com/en/ is the only officially supported java. While you've perhaps had good look running alternative Java's, the java runtime from https://www.java.com/en/ is the only version that UD support can/will support.

Are you restoring and ISY backup on Polisy? Check out the first post of this thread:

As @asbril said yes you can, just run Launcher again. You can't just right click in the existing finder window.

A couple of comments on heartbeats, with the style programing that you are using you should see a solid green folder in the program tree next to the program (assuming that you have "detailed" status icons turned on in the program tree: ) The solid green icon indicates that the THEN block is running, if the Icon isn't green then the program is not in that 25 hour wait state, which it should be 99.99999% of the time. Second, here is the heatbeat program I use for all insteon battery sensors: hb.FrontDoor - [ID 0066][Parent 0072] If 'Door Switches / Front Door / Front Door- Heartbeat' is switched On Or 'Door Switches / Front Door / Front Door- Heartbeat' is switched Off Then Wait 24 hours (wait 24 for 2845 Hidden door sensor, wait 25 for 2421 Surface Mount, or Water Detection) $iDoor.FrontDoor.HBmissed += 1 $iDoor.FrontDoor.HBmissed Init To $iDoor.FrontDoor.HBmissed Wait 2 seconds Resource 'NotificationNS.DoorTrouble.FrontDoor' Run Program 'hb.FrontDoor' (Then Path) Else - No Actions - (To add one, press 'Action') It's similar to yours but doesn't set a state variable for another program to deal with. I do increment a counter because especially 2421's it's common for a missed heartbeat occasionally. NOTE especially, the last line which RUNS the then block again, if the heartbeat is missed. You're current program lacks a re-trigger or repeat. If the heart beat fails yours just stops until another heartbeat is received. (perhaps whatever program deals with $sNorthGate = 2 has a nag feature.) The resource called sends a notification thru the Notification node server that looks like this: (this particular 2421 has the most trouble with heartbeats, but it never misses an open/close in normal use or tests after a failed heartbeat). the program that counts transmissions is: FrontDoor - [ID 005B][Parent 0033] If 'Door Switches / Front Door' is switched On Or 'Door Switches / Front Door' is switched Off Or 'Door Switches / Front Door / Front Door- Heartbeat' is switched On Or 'Door Switches / Front Door / Front Door- Heartbeat' is switched Off Or 'Door Switches / Front Door / Front Door- Low Bat' is switched On Or 'Door Switches / Front Door / Front Door- Low Bat' is switched Off Then $iDoor.FrontDoor.TransCount += 1 $iDoor.FrontDoor.TransCount Init To $iDoor.FrontDoor.TransCount Else - No Actions - (To add one, press 'Action') The battery counter is just +1 to each sensors integer variable at 12:12:12 am every morning. So for each sensor there are 3 integer variables: --- Don't have any input for your siren issue, I don't own one.

this isn’t really different that the hub, with the hub you also need to create a scene to link the switches. Since you’ve factory reset twice the links don’t exist. You need to create a scene. You need to add BOTH switches as CONTROLLERS (not Responders). Then either switch will work manually, and from the ISY or a program you control the scene.

And after you do as @Techman suggests then control the scene, not the switch.

follow these instructions to upgrade the OS to 13 https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Polisy_OS_Versions_Below_13 Edit to add: after the OS is up to date you'll also need to sudo pkg update sudo pkg upgrade sudo service pg3 restart once again.

What is the output fromif you type uname -a

Are you pulling the set button out, waiting 30 seconds and pushing it all the way in, AND HOLDING it all the way in until the long beep STOPS ? Edit to add: You do need to at least update to 4.9. I just caught that you're still on V4 after @Techman comment... I don't remember exactly what changed after 4.7.3 but something about time does stick in my mind. Version 4 upgrades all you have to do is click the upgrade button in the admin console.