Illusion

Updated to 3.0.26in a full package upgrade from ISY. Restarted PG3 (on Polisy) and my Weatherflow node server had all the forecast nodes (which I do not use, do not have in configuration and previously deleted from the poly) and it also had a node for my defective Tempest which was removed and replace with a new one. Not a big deal, but I did have to delete 11 nodes to clean up my ISY tree. Is this something that will have to be done with each update? Updated to 3.0.27 today via restart node server, and all the unused forecast node came back...

Upgrade to 5.5.4 corrected the issue.

Upgraded to 5.5.4. Added in the Synchrolinc. All still same failures. @Techman Would still love it if you dig a v1.15 out and try to add it some day...

@Techman Factory reset is working. If I check the link table after a factory reset it shows the expected table. And again, directly linking this device to a lamplinc or something will reliably turn that device on and off in response to load changes at the output of the v1.15 synchrolinc. That 3 line link table is the result of a restore device.

Thanks for the attempt at help guys! I thought the i1 comms was a good path to try. So I forced the ISY to i1 comms only and added a factory reset v1.15 to my system. That went extremely poorly with very long writes and an ever more terrible looking link table as a result. I deleted, factory reset, and tried using automatic and device reported. Back to the original bad link tables. Factory reset v1.15 and restore device yields same bad link table and no live status updates. Poor comms are not an issue in my system. I am a power line home automation guy from back in the X10 days, and I learned (was forced to learn) how to have a clean strong power line environment. (capacitive couplers- filter links on every noise make, line sucker - and lots of dual band Insteon devices on both legs.) @Techman Thanks for the zwave device suggestion. That alone will make me get zwave when my last functional synchrolinc fails! And yeah, in a few days, if you could try adding that spare I would appreciate it. I would not advise touching the one that is working in the system just in case I am not crazy. Event viewer of last attempted add attached if anyone is curious. This would have been an attempt at adding a factroy reset v1.15 with the ISY back in automatic comms selection using the 'start linking' and button press on the Synchrolinc method. adding synchrolinc.txt

Hey @Techman, I should leave it alone, but it is tough for me... Was that V1.15 added to the system on a much earlier ISY firmware? I was on 5.3.4 when I began trying to make this work. If it has been in your system from much older firmware, do you by chance have another synchrolinc v1.15 laying around that you could try to add using the current 5.3.4?

@Techman Thanks so much! I find it super weird that they work for me with manual linking to other devices, but have messed up link tables if the ISY touches them. But if yours work, it must be a me problem. Thanks for taking the time to respond. I guess I will leave this as one of those super weird home automation gremlins. I have been working on this since May of this year with the same poor results no matter what I do.

@neromir I have 15 Insteon switchlinc relay units in my system. I have used hardware and software versions of these switches dating back to 2006 and have never had a load side issue from a failing switch.

Oh no, the Synchrolincs work just fine if I link them with devices outside the ISY. It is only the ISY that has an issue with them. And they always respond correctly if I do a query. My bad link table is just like other users bad link table here: I doubt the ones that you had and worked flawlessly had a V1.15 sticker on them. I suspect they were just like the 6 of them I have that work great, all with V1.1 stickers on them. The out of business comment is related to my belief that something significant changed between v1.1 and v1.15 and UD was not able to get that info with the fall of Smarthome. Now that they are sorta revived, I was hoping that someone would update whatever needs to be changed to allow the v1.15 units to work with the ISY.

I had hoped that the reviving of Insteon and newer ISY firmware would allow me to add these synchrolincs I bought to my system, but alas still no joy. In the below pic, I have 3 Synchrolincs, all show as the same version, but only the one with the hardware sticker of V1.1 will add to the ISY correctly. The other two with hardware stickers of V1.15 are weird. V1.1 adds and functions fine: But V1.15 does not update status unless I query it and the link table is wrong after adding: And with the other V1.15 I decided to have the ISY restore the link table and I get: I detailed all this back in May here: I am keeping these things in the hopes that one day I will be able to add them to my ISY and use them to monitor that power states of devices around my home.

They do not.

Update: I am still on 5.4.4 and this issue still exists for me and is 100% repeatable. I remain very concerned that it is not something that anyone else experiences. UD is working with me through the ticket system and Remote sessions.

Still offline for me Edit: There she goes! Back online.

Have opened a ticket. Did advanced testing in advance of ticket response. Built two test scenes and put a spare switch in each scene, in one as a controller, in one as a responder. Verified scenes work and verified device link table. Replaced switch with another spare switch and new switch shows in the scenes, but without proper settings and link table of new device is empty. Something very wrong on my end.

@GeddyThanks for the new thread. I have been searching for other instances of this failure and am deeply concerned that I have not seen others with this issue. I have used the 'replace device' function 6-8 times a year for nearly a decade on the ISY 26, the ISY 99, the ISY 994I, and now IoP. I used the same steps and procedures as I have for nearly 100 times. I am not sure how a restore can help me as I seemed to have a similar issue with two devices. But this is going to be so much work, maybe I will try playing around with that. Maybe I need to open a ticket as this has not been reported elsewhere and is kinda catastrophic for my use of the ISY. I think I will just set up critical links to that switch and see what a ticket gets me.

Disaster! I just had to replace an 8 button Insteon KPL. 158 links in device. Replace went as normal and expected, but device behavior was totally off after swap out. I looked at the link tables and this is what I saw: The ISY knows it is supposed to be a member in all associated scenes, but no links! Going to have to manually rebuild. So unfortunate as this is one of the most compelling uses of the ISY system with Insteon. I have hours of work ahead of me...

Just replaced a Fanlinc that lost its high setting. Used the 'replace device' ISY function, and it lost all its ramp and intensity settings in scenes for the new replaced device. All scenes show "default" instead of the intensity and ramp rate. Link type also shows as 'default' instead of 'Insteon' Looks like I am going to have to manually adjust all connected scenes. Edit: Slogging through all the scenes, and all the controllers. I came to two scenes that had the correct intensity and ramp rates. These two scenes were created after my upgrade and switch over to IoP. So all the scenes that did not get updated were from the before times. Edit: Turns out that the two scenes that had the correct ramp rate and intensity listed did not have the link in the devices stored that way. While compare device links showed all good (identical), activating the scene did not turn the light on, but the ISY knew that it did not, even though it showed in the list that it should have: The screen shot above is taken after triggering the Wake Slow scene. It shows the bedroom fan-light as off even though the action shows it should have turned on slowly. I had to update the action to something other than what was set, and then change it back to get the outcome to be as expected.

Cloud Admin Console worked fine today. Maybe just a temporary issue.

My ISY launcher, now "IoX Launcher" does not allow Admin Console to download from the cloud. Option is there, but does not do anything when selected. LAN does work.

In IoP and PG3 there are multiple references to reboot and restart. Looking for clarification. In Admin Console Configuration there is : Polisy Systems Settings: Reboot There is also Restart IoP In PG3 Systems: Restart Polyglot 3 And Reboot ISY Questions: Is reboot the same as restart? If not, what is the difference? Does the Reboot Polisy restart the whole box like a power cycle and the others reboot or restart the individual programs on that box?

Well, my PG3 polyglots run. But I don’t understand how I could have the new bios. Unless it’s somehow automatically installed on first boot. Since @Michel Kohanim liked the suggestion to open a ticket I will do that. Sent from my iPhone using Tapatalk

Update Bios Question. I have a 2 year old Polisy. I did the new hard drive version of upgrading it. New hard drive came with IoP 5.4.4 and PG3. When I click the button for TPM it does bring up the password setting window. Elsewhere here it has been said that means I have the latest Bios. But the button is not greyed out and when I press it it does bring up the "are you crazy, you are going to brick your system" warning. I would assume I have old Bios, as that would reside on the Polisy hardware right? The new hard drive would not have that on it, right? But it seems like I am up to date because it looks like I can enable TPM? 1. Should I do the Bios update? I am scared. 2. Do I need to enable TPM? Why should I care about adding another layer of complexity?

Before I hit the update button I wanted to mention a thing I see with 3.1.11. I pulled power to my Polisy to install a 12v DC UPS. Power was off for 15m. On reboot, the uptime counter for the PG3 still showed 4 days of uptime, but the uptime counter for individual polys was from reboot after new UPS installed.

Yes. Solved Sent from my iPhone using Tapatalk

Okay, I take it all back. I have lost nothing by making the big switch to IoP and the ISY Portal. I retract my request for Apple Widgets. I can do everything using Webhooks. It is incredible. Make an ISY Portal event in connections. Just like your are going to do an IFTTT integration: https://wiki.universal-devices.com/index.php?title=ISY_Portal_IFTTT_Integration#Setup_Instructions_-_ISY_Portal Then make a Siri Shortcut. You can sorta follow the IFTTT instructions here: https://help.ifttt.com/hc/en-us/articles/360053753113-Use-Siri-to-Run-IFTTT-Applets But you only need three of the steps: 1. URL (put in the web locator from ISY Portal) For your convenience, in your list of events in portal, there is a small icon beside the red X, which will give you the full URL you can cut & paste here 2. Get Contents of URL. Method 'Post'. Request Body 'JSON' 3. Name your Siri Shortcut. And now you can have this shortcut that directly activates an event in the ISY Portal. You can trigger it with Siri voice. You can trigger it with Apple Widgets on the Today View: And you can even just put one button on your home screen like I was wanting and trigger it with a touch: So far my experience is that an event takes place in under 3s. Really actually close to 1s. So happy.