FloridaGary

Same here. Happy New Year all!

In the Admin Console, I have 4 “Customized Content” entries under the Customizations tab. Three (3) are for my Leak Detectors and One (1) for UD Mobile. I eliminated One (1) entry. Each customized content has an ID number, 1,2,3,4 and 5. When I removed #4 of 5 entries, should the last entry ID# change from #5 to #4 to continue working? Or, it doesn’t matter?

Received a message today about an update package available. After trying to download, the Polisy box continued a loop of one solid light followed by the following 2 blinking lights, 2 beeps and then back to one solid light and 5 beeps. I have tried: 1. Software Reboot - No change 2. Power-cycled the Polisy box - No change 3. Tried to Factory reset - No change The loop continues as stated above. Any thoughts or just submit a ticket to UD?

Slot 2 was just deleted and all should be good. As far as I can remember, when I installed the paid version last summer, it must have kept both running?

@Jimbo.Automates - Sorry for the incorrect sub-forum. This is the first time I’ve been back to this forum since the 3rd week of Oct 2023 when a health scare changed my world temporarily until this month. Now I’m catching up with life after 8+ months. I just found this post on 10/31 that may be the reason I’ve experienced this problem and after updating for the first time this year. https://forum.universal-devices.com/topic/42262-paid-plugin-node-server-not-starting/ I appreciate your assistance and will try to correct. (Admin-Feel free to move this to the appropriate sub-forum.)

IoX and PG3x are up to date. In the Admin Console, noo1 controller shows "Connected" and REST status "Running", while noo2 controller shows "Connected" and REST status "Not Running". I am a novice with Node Servers without any previous issues using them, but not sure how to resolve this. Any help is appreciated. Thanks!

Same here. Feit bulbs and no issues for years. Dimmed at 50% and no flicker.

Update: So far, none of my Insteon controlled devices have turned on as scheduled. This has never happened with any previous update. All can still be controlled manually and with Alexa. Update: Apparently I had to reboot more than once to fix above. Scheduled lighting is now working.

Just updated Polisy Pro from 5.6.4 to 5.7.0. No issues with the Admin Console, PG3X or Mobile. Running all Insteon devices.

@Techman Thanks for the link. I’ve had this issue since upgrading to 5.6.4.

Ok. I am able to access Polisy using either option, so thanks for clarifying.

@Javi Now that my mobile issue is resolved, I decided to update Polisy to 5.6.4. When opening the IOX Finder, Polisy shows up but then an error box appears that says “Not Found” although it is listed correctly. I click on OK and a 2nd Polisy shows up with the correct uuid, but with a local Polisy url. How do I delete it?

Thanks Javi. For some reason, my local network was showing under System Network Relations. I removed it and all is good. Thanks for the help.

Answers to your questions are listed above. It’s not accepting my user ID and/or Password. No issues connecting when disconnected from WiFi.

UD Mobile has been working fine all morning, but just suddenly received an error message. IP address is set. What am I missing? System: Home ERROR: No LOCAL IP ADDRESS is set for the system. System name: Home

I am experiencing the same.

Thanks @Javi

Same for me. Started today.

Hi All, Looking for feedback to make sure I am programming the Insteon Smoke Bridge correctly. The Smoke and CO seems straight forward, but wasn't sure about Low Battery Status and Malfunction Status which shows a current state of "On" after linking the Smoke Detector to the Insteon Smoke Bridge. Thanks, Gary Smoke Bridge - [ID 0034][Parent 0001] If 'Smoke Bridge / Smoke Bridge-Smoke' is switched On Or 'Smoke Bridge / Smoke Bridge-CO' is switched On Or 'Smoke Bridge / Smoke Bridge-Low Bat' Status is On Or 'Smoke Bridge / Smoke Bridge-Malfunction' Status is On Then Send Notification to 'Gary' content 'Smoke Detector' Send Notification to 'Laurie' content 'Smoke Detector' Else - No Actions - (To add one, press 'Action')

I did initially, but when https://Polisy:8443/desc did not work, I went back to the Polisy Guide and replaced "Polisy:8443/desc with the URL:8443/desc and that worked. Just another newb error. Thanks for responding @MrBill

When I open the ISY Launcher (start.jnlp), the ISY Finder window opens but does not find my Polisy. This happens occasionally and I just click on refresh and my Polisy populates in the window. This is the first time it has not. I have deleted the Java (version 8 ) files and rebooted Polisy. Should I power cycle the Polisy instead of rebooting?

This may help.

I received the same warning and was upgraded without issues. Make sure to have a recent back-up before upgrading your BIOS. Also, have a new password ready when you enable TPM and don't forget to keep a record of the new password. (See below info from Michel) TPM = Trusted Platform Module At the highest level, it's a cryptographic chip that does not depend on anything else. In our case, it serves two purposes: 1. We can have it check the OS being run and make sure the OS (our version of FreeBSD) is signed/verified by UD 2. A root key is stored on the chip itself. The root key creates and manages a master application key that is used to create as many application keys as necessary for encrypting things (including the whole file system if need be). The only way the root key can be decrypted is via the chip. The only way the application keys can be decrypted are via the root key. So, all keys are themselves stored encrypted so the likelihood that someone can get access to the root key and application keys are exponentially reduced So, when you enable TPM, the following takes place in the RAM (so no residue on the disk): 1. A root key is created and stored in the TPM 2. A master application key is encrypted by the root key and stored in the TPM 3. Both of the above are zipped up in a package and encrypted by your password and a very secure encryption algorithm. This file is stored in the conf directory of your IoP. So, BACK IT UP NOW If you ever have to restore your IoP to another device, you WILL NEEED YOUR PASSWORD to decrypt #3 and recreate the keys in the new chipset. If you lose your password, you will have to start from scratch.

Thank you @Techmanand @MrBillfor reviewing and confirming. Gary

Hi All, Yesterday around 1:30pm, I updated Polisy to 5.4.4 in addition to updating the BIOS. All went well without any issues. All programs executed as scheduled, but noticed 2 changes on the Leak Sensor Summary page (see attached) that may or may not mean anything. As some of you know, I am not a programmer, but I am trying to learn from reading the ISY wiki, forum posts and anything else I can get my hands on to better understand since migrating from the Insteon Hub to IoP. When the Leak Sensor program was first setup, the Heartbeat "status" always showed "True" followed by "Timeout" and "Wet" showing False. Since yesterday's update, the status of the Heartbeat program shows False. I am not sure this makes any difference since the Heartbeat program checked in within 24 hours as shown on my attached spreadsheet. If all looks good, then I am trying to understand the difference in the True/False status column. Thanks and have a great Memorial Day weekend! Gary Leak Sensor Summary.xlsx