SSamuels

Thanks everyone for the help. Recreating the program worked. Stew

When the alarm is trigged the program is Green. I will try deleting and recreating. Thanks

Level 3 log ISY-Events-Log.v6.0.4__Wed 2026.02.18 04.17.06 PM.txt The IOLinc's address is 42.4.E3

'12129Td/Alarm/ALARM - Intrucsion-Sensor' is switched On. BTW - This worked about a year ago. Recently the house alarm tripped and I realized the ALL Lights scene was not turning on.

An Insteon IOLinc v.41 is connected to my alarm relay outputs. When the Alarm is tripped, the relay output closes. The IOlink registers the closure of the circuit and Polisy recognizes the switching to 'closed'. I have verified that the AC console reports the IOLinc circuit closure when the alarm is tripped and reports the circuit opening when the alarm is cleared.

Program 'Alarm!!+’ not working: 'Alarm!!+' Program – Enabled is checked and program saved What is supposed to happen: If Insteon sensor switched ON, Set scene 'ALARM_All_Lights' = ON Polisy Log – Sensor is switched ON - see attached Scene ‘ALARM_All_Lights’ does not turn on when sensor is switched on If I manually execute the 'Alarm!!+' ‘Run Then’ the Scene turns on and notifications are sent Ghosts in the machine... What could be wrong? Thanks Stew Progam not working on sensor control - switched to ON 20260218.docx

I had a program that had in the THEN - Run Program <Not6. Specified> Likely I removed/modified the Program that the THEN refers to. By restoring a prior backup (Ver5) I was trying to identify the missing program. However when I attempted to restore a v6.0.0 backup, I received the error message as well. When I attempt to reboot my Polisy I get an Error 'Socket Timeout Error' I did a hard boot (powered down) HELP | ABOUT Both Firmware & UI are v6.0.0

I was able to do a backup of my current ioX The restore file was in the original zip format I attempted to restore both a v5.9.1 and a v6.0.0 - both returned the same error

Firmware: ioX v.6.0.0 (2025-09-19) UI ioX V.6.0.0. (2025-09-19) File --> Restore ioX Exit Malware Bytes Turn off Windows Defender YES to proceed Select backup .zip file Error Failed uploading configuration file [see Restore ioX error message .pdf file] Attempted a backup file created today with same error message. Rebooted Windows - same result Any thoughts are welcomed. Thanks Stew Restore iox error message 20251101.pdf Samuels Restore ioX problem20251101.pdf

Thanks for the response. The earlier install that is identified as 1.0.5 never worked - I suspect because I did not have a Google Device Project. I would like to use the 0.2.5 newer plugin as it does not require the G Device Project. Somehow, whatever I installed from the previous NestSDM is still present and when I delete the installed NestSDM from Polyglot and install the latest NestSDM from the store, it still reports as version 1.0.5 and I receive the authentication error - See video attached. Is the phantom 1.0.5 version somewhere in my Polyglot profile? If so can the admin completely delete and NestSDM from my Polyglot account? Thanks very much Stew update to 0.2.5 NestSDM 20250121.094401.mp4

Update Polyglot reported that NestSDM was ver 1.05 [Beta] Attempted to update to 0.2.5 - still could not authenticate Deleted existing NestSDM and installed ver 0.2.5 in another slot Polyglot verified that now NestSMD ver 0.2.5 was installed Authenticate worked - I Completed the authentication and gave ISY control of my Google account. When I attempted to DISCOVER - Polyglot reported that an attempt to discover was made before the connection to the Google SDM API was established. And, now the version of the NestSDM on Polyglot is once again reporting ver 1.0.5 [Beta] Is the prior version over-riding the 0.2.5 setup? How do I prevent this? Thanks

Polyglot reporting: Current version 1.0.5 [Beta] Status: Connected IoX Version: 5.8.4 Connected When Authenticate is clicked the response is: {"error":"Authentication Error"} Thanks for any help Stew Nest PlugIn authentication response 20250120.pdf

Hi- Thanks for the reply. I am fine sharing these items. I do not know how to located devlist, devfile or the debug.log. Can you help point me in the correct direction?

MQTT was working with Ratgdo (Garage Door Opener) · Updated MQTT to 0.0.39 [Beta] · Stop/Start MQTT · Now I get MQTT Notices o Start-up o Waiting on valid configuration MQTT Controller reports NodeServer Online = TRUE, is not communicating with Ratgdo. Any suggestions appreciated. Thanks

Thank you, everyone for the helpful information. Best Stew

Thank you

I am sure this has been asked & answered previously, but my forum searches have not found an answer. Why doesn't IoX provide the capability to have calendar conditions in IF statements of programs, e.g., IF Calendar Date between X & Y, If Calendar date greater than, If Calendar Date Less than then..... Thanks

Thanks (again) Geddy. SSH via PuTTY completed the udate to 5.5.2 Happy New Year

Here is what I have tried and the results: 1. Turned off Anti-Virus software on desktop and sign in to AC locally 2. AC --> Help --> ‘Automatically upgrade ISY Nodes to 5.5.2’ 3. AC closes 4. After 30 minutes – AC not available when launching ioX launcher 5. Polisy shows left light solid green, middle and right lights blinking green To get AC back I disconnect power from the Polisy. The Polisy reboots and AC is once again available from ioX launcher. Version shows 5.4.4 Any advice is appreciated.

Hi Geddy- My bad. I get confused on what is the the Node Server and the Portal. I will need to be clearer in the future. As far as the resolution goes, I tried a number of things, but am not sure what caused the resolution. Again, terminal confusion on my part. I just updated Java. Thanks again for your time and recommendations.

Larryllix & Geddy- My follow-up. I did not open a ticket as Polisy began communicating with the Node Server - and I don't know what I (or the universe) did to accomplish this. I won't argue with success. Christmas Ghosts In The Machine. Happy Holidays and Merry Christmas and thank you for the help.

Thanks. Have a Merry Christmas.

License Expiry Date 2024-04-21 so it should be good.

I did not answer larryllix's question: no, I was not updating anything when this occurred.

Thanks laryyllix & Geddy: After rebooting the Polisy & router - On the AD Config tab the Portal is shown as 'Online' and the AC was connected to the Node Server. After a couple of minutes, the AC prompts again for User Name & Password and then throws an error message: "Socket Open failed java.net. ConnectException: Connection refused: no further information". When this happens the Portal shows the ISY is Offline. Geddy: Thanks for the information on attached images vs. pdf. I don't know if this is relevant - my Java version is 1.8.0_333 and the runtime parameters are: -Xmx512m