waffles

Mine is back up as of a few minutes ago.

Just came back online. So all good again.

I saw the post after I found my portal access/Alexa to be not working: However, from what I understand it should be working again. AC is accessible just fine via LAN. Is there anything I would need to do to bring it online again?

I seem to have run into the same issue with my Polisy. Sounds like the best way forward is to open a ticket, which I will do.

Thanks @Michel Kohanim for your reply. Sounds like you use it as a regular PC that also happens to run IoX on it. Am I overstating this? This gives me a good idea. Thanks.

I found this in the sticky: "Why should I buy one? Only you can answer this question. If you have a polisy, I'd say don't unless you simply want a new toy, have money burning a hole in your pocket, or simply to support UDI." This statement was made already some time ago. So I was wondering if this still holds true today. I have a relatively small system with less than 100 Insteon devices and limited amount of simple programs. Would I gain anything performance- or otherwise if I switched to a polisy?

Got it. Thanks!

This had been my MO for years as well, but it this time I apparently needed to do it the other way around. I had also tried several power cycles beforehand to no avail....

I have been trying to update v3.2.4, but thus far without success. I thought when I update my Polisy via the Upgrade Package command in the AC that Polyglot would also be updated along the way. This does not seem to be the case. What do I need to do here?

When did you upgrade yours? From what I understand (and I could be wrong - still awaiting confirmation) Polisy got temporarily pulled from the list of eligible products. EDIT: Finally I just got mine to upgrade also. I had not made the connection yet to clean the Java cache before making any upgrade attempts. Thanks for pointing me into the right direction!

How did you do this? I only keep getting 5 beeps and no update on mine. EDIT: Finally I just got mine to upgrade also. I had not made the connection yet to clean the Java cache before making any upgrade attempts.

I received the release announcement email last night so I just tried upgrading my polisy via the AC, but it did not work (got 5(?) beeps, but AC stayed 'alive', no logout, and still on same f/w as before: 5.6.4). When I browsed through the support thread here I found @Michel Kohanim post buried, indicating that the upgrade has been disabled. Not sure what 13.2 refers to though, so I wonder if my issue is related here or not. Any guidance would be appreciated. Thanks!

I worked through the instructions here:https://wiki.universal-devices.com/index.php?title=ISY-994i_Series_INSTEON:Networking#Web_Server_Module ....specifically the part about: Append to an Existing File I now can access it via Chrome (my go-to browser FF does not like that it is not a secure connection)

Thanks for the confirmations @kclenden I have setup a custom log and started collecting data. So far so good. I’d like to keep it running for a few days.

@Geddy at this point I do not trust my setup to accurately and promptly alert me if a leak occurs. Therefore I am currently in troubleshooting mode. With my latest effort I want to verify that the ISY actually receives a heartbeat signal every 24 hrs from each sensor. If that's the case, I can close this topic and shift my focus toward troubleshooting my programs. If the ISY does not receive the signals, my plan is to look closer into the communication between LS and ISY.

Let me see if I got this right: The LS sends a heartbeat Control message approx. every 24 hrs. In properly working setup I should not see any "Status" changes, because the heartbeat signal just keeps coming... Therefore for my montoring I will need to look for LS Heartbeat 'Control' messages, rather than "Status" changes. Problem is that the ISY log only captures the "Status" changes. If I want to monitor what happening on the "Control" side, I need to do this via a homemade custom log, e.g. via the Networking Module. Is my understanding so far correct? EDIT - never mind - I since figured that web server part out on my own. In the meantime I have set up a bunch of Pushover notifications - for each of the sensors on their program #2 - to alert me of any heartbeat "action". My expectation is that I should see every 24hrs a Pushover notification for each of my 10 sensors, if all works well.

Thanks, guys, I like your suggestions. I’ll also take a closer look at the network module option.

Update: Since my restart with the original, lean 25hrs program set I have had a few warnings from 2 of the 10 sensors about missed heartbeats ('2'). Right now all variables have gone back to '1', i.e. all clear. I checked the log for LS Heartbeat activities. Here is an example for one the LS (not one of the ones that had missed a heartbeat). I had expected to see an event for every day (approx 24hrs), but there are several gaps. That even though the IoX had been running the whole time with the exception of about 2 days after a bad f/w update. Any thoughts here?

Thanks All who have helped here for being so patient with me. I really appreciate it. Yes, $i are Integer Variables and the ones starting with $s are State Variables. In the meantime I have disabled the folder that contains the current sensor programs and built a set of programs based on the initial 2013 code; the way it is also included in the Handbook. It's a lot simpler than the version it had morphed into over the years, and which I have been using. So let's go back to the basics and see how well this goes! I'll keep you posted. Thanks!

Here is the clipboard version, limited to Sensor #10. I hope you find this easier to read. ----------------------------------------------------------------------------------- Leak Sensor #10 - Variable Control 1 - [ID 006C][Parent 001C] If 'Leak Sensors / LS#10-Basement-Workshop- Dry / LS#10-Basement-Workshop- Wet' Status is On Then $sLeak_10__workshop = 9 Else Wait 10 seconds $sLeak_10__workshop = 1 ----------------------------------------------------------------------------------- Leak Sensor #10 - Variable Control 2a-25 - [ID 0074][Parent 001C] If ( 'Leak Sensors / LS#10-Basement-Workshop- Dry / LS#10-Basement-Workshop- Hea' is switched On Or 'Leak Sensors / LS#10-Basement-Workshop- Dry / LS#10-Basement-Workshop- Hea' is switched Off ) And 'Leak Sensors / LS#10-Basement-Workshop- Dry / LS#10-Basement-Workshop- Wet' Status is not On Then $sLeak_10__workshop = 1 Wait 25 hours $sLeak_10__workshop = 2 Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Leak Sensor #10 - Variable Control 2b - [ID 0075][Parent 001C] If ( 'Leak Sensors / LS#10-Basement-Workshop- Dry / LS#10-Basement-Workshop- Hea' is switched On Or 'Leak Sensors / LS#10-Basement-Workshop- Dry / LS#10-Basement-Workshop- Hea' is switched Off ) And 'Leak Sensors / LS#10-Basement-Workshop- Dry / LS#10-Basement-Workshop- Wet' Status is On Then $sLeak_10__workshop = 1 Wait 25 hours $sLeak_10__workshop = 2 Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Leak Sensor #10 - Variable Control 3 - [ID 0076][Parent 001C] If ( $sLeak_10__workshop is 1 And Time is Last Run Time for 'Leak Sensor #10 - Variable Control 2a-25' + 26 hours ) Or ( $sLeak_10__workshop is 9 And Time is Last Run Time for 'Leak Sensor #10 - Variable Control 2b' + 26 hours ) Then Wait 5 seconds $sLeak_10__workshop = 3 Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Leak Sensor Activation - [ID 001D][Parent 001C] If $sLeak_00__sump_bottom is 9 Or $sLeak_01__laundry is 9 Or $sLeak_02__kitchen is 9 Or $sLeak_03__sump_top is 9 Or $sLeak_04__kitchen_ext is 9 Or $sLeak_05__basement_bathroom is 9 Or $sLeak_06__HVAC_drain is 9 Or $sLeak_07__above_tall_AV_rack is 9 Or $sLeak_08__above_short_AV_rack is 9 Or $sLeak_09__washer is 9 Or $sLeak_10__workshop is 9 Then Send Notification to 'GS' content 'Leak Sensor Activation' Resource 'Pushover-Leak-Sensor-Activation-Heartbeat missed' Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Leak Sensor Problem - [ID 0022][Parent 001C] If ( Time is 9:00:00AM Or Time is 6:00:00PM ) And $sLeak_00__sump_bottom is not 1 Or $sLeak_01__laundry is not 1 Or $sLeak_02__kitchen is not 1 Or $sLeak_03__sump_top is not 1 Or $sLeak_04__kitchen_ext is not 1 Or $sLeak_05__basement_bathroom is not 1 Or $sLeak_06__HVAC_drain is not 1 Or $sLeak_07__above_tall_AV_rack is not 1 Or $sLeak_08__above_short_AV_rack is not 1 Or $sLeak_09__washer is not 1 Or $sLeak_10__workshop is not 1 Then Send Notification to 'GS' content 'Leak Sensor Problem' Resource 'Pushover-Leak-Sensor-Program Problem' Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Leak Startup - [ID 001B][Parent 001C][Run At Startup] If $iStartUp is 0 Then Run Program 'Leak Sensor #00 - Variable Control 2a-25' (Then Path) Run Program 'Leak Sensor #01 - Variable Control 2a-25' (Then Path) Run Program 'Leak Sensor #02 - Variable Control 2a-25' (Then Path) Run Program 'Leak Sensor #03 - Variable Control 2a-25' (Then Path) Run Program 'Leak Sensor #04 - Variable Control 2a-25' (Then Path) Run Program 'Leak Sensor #05 - Variable Control 2a-25' (Then Path) Run Program 'Leak Sensor #06 - Variable Control 2a-25' (Then Path) Run Program 'Leak Sensor #07 - Variable Control 2a-25' (Then Path) Run Program 'Leak Sensor #08 - Variable Control 2a-25' (Then Path) Run Program 'Leak Sensor #09 - Variable Control 2a-25' (Then Path) Run Program 'Leak Sensor #10 - Variable Control 2a-25' (Then Path) Wait 5 seconds $iStartUp = 1 Else - No Actions - (To add one, press 'Action') Some background: When I set these programs up, my aim was to follow the original code from the 2013 post. Maybe I missed something here. The "And Wet Status is ..." modification was suggested later by the original poster, so I thought it would be a good idea to also implement this, in particular when I read that the behavior of the sensors had changed in later versions. I wanted to make my code as robust/current as possible.

hello @Geddy, thanks for chiming it. If I did not want any input, I would not post here The code is from @belias's modified version: top is from the original post - bottom is my implementation Sorry for the dumb question, but how would I do this "...to put all existing programs in a folder and make the folder conditions false so they don't run..." (As you may have seen in my earlier posts, I had tried to disable the programs individually by unchecking the "enabled' box, but this did not work.) Thanks!

In the meantime the first 2a has already stopped being "green". In my current understanding #04 is no longer being monitored, so I should get a notification within the next 20-some hours that its heartbeat got missed, correct?

For programs that should be running continuously (for me that's indicated by the GREEN icon), if those switch to a RED Icon. Example here would be the 2a ones that monitor the state of the sensors. Those also show a "Running Then" in the Summary tab Am I misunderstanding this?

Update after having run the original 25 hrs set only: Some of the 2a programs have stopped running again: Do you guys see anything that could have caused it? So above was without @DennisC's suggested daily jump start program. I have activated it now and reset the 'whole thing': Let's see how it does now....

So I just did the restart experiment as @tmorse305 suggested. Looks like disabling the start up program is not effective, as it launched and triggered the 2a's Since also the 49 hrs 'set' successfully launched, I now have somewhat competing sets of programs.... (In a second round, I also tested the opposite: disabled all 49 hrs, enabled 25. After restart BOTH sets were running again. So it seems the enabling/disabling does not work, at least not how I think how it should work.) My next step is to reinstate only the original 25 hrs set. I'll probably have to delete the other set. The sensors are all Insteon 2852-2222, a mix of v.41, 43 and 44. I had replaced the batteries a few months ago, in an effort to improve the overall signal robustness. I did not notice much change unfortunately, so I came up with 49 hrs flavor.