MexicanRadio

Thanks to all for the serial cable notes, however, I was using the proper serial cable. The Polisy had been installed and operating for a few years prior to this problem occurring.

As a followup, in case it can help anyone else that runs into a similar issue: It appears that the problem was with Polisy not talking to either of my serial PLMs. The PLM I was using when the problem first appeared was of the newer version, so I tried using an older (re-capped) PLM to see if the symptoms varied. They did not. Neither PLM would communicate with the Polisy. So the next step was to check the cable from the PLM to Polisy. There's little that can go wrong with the serial cable, and the cable passed continuity checking on all connected pins. Finally, I tried connecting each PLM to my old ISY-994, where each worked correctly. So... it would seem that the Polisy serial connection for the PLMs had failed. There is a very slim chance that some oddness with the serial cable I used (and had been using for months) could have some kind of glitch that a simple continuity check wouldn't have detected. I chose to replace the Polisy with Eisy, and also to purchase a new USB PLM. Everything now works.

Hi Techman, Thanks for the response. Here's more detail: Check all three boxes? No, because I'm on Fedora 40, not Windows. (Sorry, I forgot to mention that) There are some differences. Easiest cache clear on Fedora is to just nuke the cache. Yes, the new IOX Launcher was downloaded via start.jnlp Yes, the Replace PLM procedure was followed. Noted in last bullet point in my original post. I definitely appreciate the "sanity check"! It's always good to have someone else providing reminders. FYI, for what it's worth: my profile indicates "newbie" because I rarely post. But I've been using UDI ISY, then ISY994i, then Polisy since about 2012.

I could use a little help. Recently, my Polisy Pro went off-line. We have spokens via Google set up, and our first clue was that they quit working. I've dealt with loss of connection a few times in the past, and it's always been resolved by a simple restart of the IOX. When doing so I keep an eye on connection status on the ISY console at my.isy.io. On this occasion the result on the console was a series of error messages about PG3 not being authorized and failure to log in. Unfortunately, since I didn't expect a problem reconnecting, I did not capture the messages. I also discovered I had absolutely no connection to Insteon devices, PLM, or my.isy.io from Polisy, although it did respond to network pings. Troubleshooting revealed: Polisy does NOT seem to be communicating with either my existing PLM or with a backup PLM. Both of which were verified to be communicating normally and capable of adding and operating devices when tested with my old ISY-994. It reports / Not Connected Reloading Polisy from an image file after reformatting its drive resulted in re-establishing Internet connectivity and in Polisy upgrading to the current release. I cleared Java caches and got the latest JNLPs. I can reliably connect to Polisy locally, now. However, I can only intermittently connect to my.isy.io for a short period after a reboot of Polisy. Most attempts result in only a blank page at my.isy.io/index.htm. Attempting to do anything with PG3 results in nothing but a black page saying Loading... and nothing further. The serial cable between Polisy and the PLM seems to be good, I have continuity on the wired pins. Rebooting Polisy appears to happen correctly, if I simply pull power and plug it back in, but I cannot perform any operation via the little front panel button. Any attempt to recover via the replace PLM procedure seems to work, at first, and runs through the "Restore Devices" just fine. Then shows a message saying Reset PLM in the Administration Console's Event Viewer, at which point it starts looping through a System Busy display slowly reaching 100% over and over. Even left overnight it never again outputs a single message in the Event Viewer. So... Polisy Pro failure? Something else? I'm out of troubleshooting ideas. I might add that this same device suffered a power supply failure back on 6/11 with which Michel Kohanim kindly assisted me, but seemed to have performed just fine until last Friday at about 11PM. --Scott

Installed my Polisy today, after my wife brought it home from the USA late last week. Other than the problem with loose MSATA and Wireless cards inside that had to be rectified before startup, all went well. It didn't take long to find the device, as Ubiquiti's UniFi software controller promptly reported it. DHCP correctly got addressing from our network, which was a pleasant surprise as we run a fair-sized Ubiquiti network here with multiple subnets, and nothing in the 192.168.x.y ranges except our guest network. That said, Polisy is attempting to auto-connect to our guest SSID for its wireless connection. I assume that's because the SSID handling guests is open with no Internet access until authorized. So Polisy gets assigned a guest ip address and then does nothing, as far as wireless is concerned. Will there be a means of joining a specific wireless network? Updates via command line all went well, and it appears that I've got current everything that needs to be present. I expect I avoided a few issues because I'm later than many in installing. Some observations: Fit and finish on the case is excellent and the metallic blue color is great. Almost a shame it's gonna live in our utility room. There was no white label on the appropriate Ethernet port as stated in the Quick Setup Guide, not that that's a problem. There are no labels on the box whatsoever, other than the "Polisy" name and UD logo. No slots for wall mounting. I noticed somewhere in the earlier messages on this thread that the DB-9 is for possible use as a connection to the PLM. Will there be support for the USB version of the PLM? Also, am I correct that there's a slot for an SD card inside? If so, what's the intent? Ditto for the two USB 3 ports. I might well have missed discussion of those elsewhere since I haven't read many other threads on the Polisy box yet, so sorry if this is well-known already. And one last note: This device is installed in San Felipe, Baja, Mexico, and works just fine, for what that's worth. Just because we're retired expats doesn't mean we can't have our house as smart as we'd like.

I'd add a vote for Nucleus/ISY integration. We designed-in 4 Nucleus intercom units in our new home construction, just for the intercom capability. ISY and Insteon were already in the plan before we discovered the Nucleus, so being able to expand capabilities to use them together would be great!

Follow up: Many issues kept me from returning to this topic for far too long. Here's the revised code that does what I need: If From 9:00:00PM To 7:00:00Am (Next Day) And Status 'GarageSideDoor.1 - DoorSenso' is On Then Wait 2 minutes Send Notification to 'uh-oh_squad_cell' content 'SecuritySMS' Else -No Actions Now if only my cellular service would deliver SMS in a consistent, timely fashion... Thanks for all the assistance. It was instrumental in helping me figure out what I needed to do.

Thanks, Lee. I'll give that a try as soon as I get a little time free, again. You would think, having been a maintenance coder many, many years ago, that this sort of thing would come back to me much more quickly than it is.... but, nooo...

The event trace was made when no change in door position had occurred, just a change in the programming (see earlier messages in this thread). The door sensor is unmodified from as shipped, other than to set it to not waste battery operating the LED (which can't be seen when it is installed. I believe it ships as "single node".

Hi Lee, It's a Hidden Door Sensor. What normally happens is that someone in the family opens the door (causing the the hidden door sensor, correctly, to turn ON) and then forgets it. So the door stands open all day (as it has today) and does NOT get a change on the sensor after the initial opening. This has resulted in everyone going off to bed, on multiple occasions, and leaving the door open all night (which, for what I am sure are obvious reasons, I would like to have not happen). What I want to do is receive a notice that the door has been left open, after some period of time (currently set at 2 minutes for test purposes). Eventually I intend to have it notify me as part of putting the house to bed for the night, along with other notices I'd like to have then. I believe I've tried both control and status commands at this point, and both testing for "On" and for "not OFF" as well as "Off" and "not On", with no luck. When I was earlier looking for status instead of control, the program ran and notified me properly (using the "Then" clause) if I right clicked it and select "Run iF" but it ONLY ran correctly under that circumstance.

Note that I am not trying to detect a transition of state from door closed to door open, but rather to determine if it is staying/still open. The door has stayed open through the change. Later I'd like to add logic to only check during a certain time period, but first have to get the (I thought) simpler case working reliably. After Michel's suggested change, I believe this is the relevant portion of the Events log (Level 3): Fri 06/13/2014 15:46:06 : [iNST-SRX ] 02 50 2B.01.E7 00.00.04 C7 13 04 LTOFFRR(04) Fri 06/13/2014 15:46:06 : [std-Group ] 2B.01.E7-->Group=4, Max Hops=3, Hops Left=1 Fri 06/13/2014 15:46:06 : [D2D EVENT ] Event [2B 1 E7 4] [DOF] [4] uom=0 prec=-1 Fri 06/13/2014 15:46:06 : [ 2B 1 E7 4] DOF 4 Fri 06/13/2014 15:46:06 : [D2D EVENT ] Event [2B 1 E7 4] [sT] [0] uom=0 prec=-1 Fri 06/13/2014 15:46:06 : [ 2B 1 E7 4] ST 0 Fri 06/13/2014 15:46:07 : [MOD 5 5 1 16] 9810.000000 SmartMeter - Inst Demand = 0.9810kW-kWh Fri 06/13/2014 15:46:07 : [iNST-SRX ] 02 50 2B.01.E7 00.00.04 C7 13 04 LTOFFRR(04) Fri 06/13/2014 15:46:07 : [std-Group ] 2B.01.E7-->Group=4, Max Hops=3, Hops Left=1 Fri 06/13/2014 15:46:07 : [iNST-DUP ] Previous message ignored. Fri 06/13/2014 15:46:07 : [iNST-SRX ] 02 50 2B.01.E7 1C.FA.98 41 13 04 LTOFFRR(04) Fri 06/13/2014 15:46:07 : [std-Cleanup ] 2B.01.E7-->ISY/PLM Group=4, Max Hops=1, Hops Left=0 Fri 06/13/2014 15:46:07 : [iNST-DUP ] Previous message ignored. Fri 06/13/2014 15:46:07 : [iNST-SRX ] 02 50 2B.01.E7 13.01.04 C7 06 00 (00) Fri 06/13/2014 15:46:07 : [std-Group ] 2B.01.E7-->13.01.04, Max Hops=3, Hops Left=1 Fri 06/13/2014 15:46:07 : [iNST-INFO ] Previous message ignored. Fri 06/13/2014 15:46:08 : [iNST-SRX ] 02 50 2B.01.E7 13.01.04 C7 06 00 (00) Fri 06/13/2014 15:46:08 : [std-Group ] 2B.01.E7-->13.01.04, Max Hops=3, Hops Left=1 Fri 06/13/2014 15:46:08 : [iNST-INFO ] Previous message ignored.

Thanks Michel. I'm trying that now. The only line changed is the first, which now reads: If Control 'GarageSideDoor.1 - DoorSenso' is not switched Off I've just waited out the timeout and have received no notice.

Ok, I thought this was going to be simple. But it's not: If Status 'GarageSideDoor.1 - DoorSenso' is not Off Then Wait 2 minutes Send Notification to 'uh-oh_squad_cell' content 'SecuritySMS' Else No Actions Apparently, (as the topic title says) I have brain damage, because after trying multiple variations, I can't get this program to work correctly. If I right click the program and "Run If", it works. Beyond that it never triggers. I'm trying to make this a general alert that this door, which gets left open way to often around here, lets me know it's been left open. Program is enabled. ISY-994i, version 4.2.3 (recently upgraded to ZS) is on the ISY and the UI, cache was cleared after install. The sensor is a hidden door sensor, and it seems that it correctly indicates state (pushing the button results in on/off shown on the ISY as one would expect). What am I doing wrong?

OK, I get it, and that lets me know what I needed, that it's just a software issue, not a hardware problem. So, I'll just reinstall and then wait for an update, which I'm sure will be coming, given UDI's usual great support.

Yep, and thanks for your help! Unless that error indicates a device malfunction, I'm betting those are gonna be my only choices. I'll see if anyone else has any ideas over the next couple of days. Maybe I'll order an earlier version, not dual-band, to try for this particular location. Eventually I need more than one anyway.