kzboray

@sjpbailey A small issue with updates not affecting functionality. In this case the NS is being flagged as out of date, but is actually running a more current version than what is being recommended. Not sure if this is a dev option or in the core so I thought I would post it for review.

I had not known that remote access for PG3 had been enabled, This is amazing! Thank you. I went ahead and tried to remotely connect to one of the Polisy's I manage and I must of missed a step. This is what came up, but no browser window opened, nor was I able to access the Polisy in an active PG3 browser session. It shows as connected, but I'm not sure how I actually interact with the PG3 web interface for the remotely connected Polisy. Can you point out where I went wrong? Thank you.

@zorax2 I'd try defaulting the 6-button keypad and do a restore device again. It's important to actually default the 6-button. Pull the air gap, and then wait a minute, finally press in the air gap and hold it until the switch beeps, about 5 seconds. If that doesn't clear it up, I'd default all the linked devices and redo the scene from scratch. I suspect you have a bit not set or incorrectly set and a clear should fix it.

@Ross, check out this NS from @sjpbailey. https://github.com/sjpbailey/Documentation/blob/main/Tuya Relay/README.md

AC update took less than minute. Rebooted via AC, about 2 minutes to accessibility. System/Reinstall all Node Servers via PG3x web interface took about 5 minutes for the 11 NS's I have installed. Manually restarted each of them and everything is once again operational. I also DL'ed the PG3x log and did a quick search for 3.0.60 which was not found so I'm unsure if the UDI interface was updated. Is there a way to check via SSH?

@cosyn , @sjpbailey just released a bunch of NS's one of them is exactly what you want. Here's the link to the documentation on the NS and HW. https://github.com/sjpbailey/Documentation/tree/main/Tuya Relay

So I opened a ticket on Saturday and as usual got an almost instant reply from Michel. That man never sleeps! We went back and forth a couple of times on more detail, but Michel came up with the answer. The Smartenit devices are not dual band and have to be on the same electrical leg to communicate with the PLM effectively. They are also very susceptible to line noise. I had moved my PLM a couple of weeks ago and this is what started my problem. As soon as I moved the Smartenit's to be on the same electrical leg as the PLM they were again able to be discovered by an Insteon device search via AC. FYI they are called; I had forgotten, not Smartenit but by their original name COMPACTA 2X4

@n_sievers great information, thank you! I'll follow up with Smartenit, but I want to wait and verify that the 2X4 is still supported due to it being removed from the supported devices list in IoX. If you Start Linking and try to manually add a Smartenit 2X4 it used to be in the list. It's not there anymore. If it is still a supported engine type and I missed it in the list. Then I would agree it's the 2X4 itself that has failed...bummer. I'll keep you posted on Smartenit support in IoX when I get a response to my ticket.

I just noticed that my Smartenit EZIO2X4—Model #5010D—2-Relay/4-Input Controller is no longer working. It has been working in the past and I suspect it stopped with the update to 5.6.2. I removed the device and was unable to re-add it back to the system. Insteon engine not recognized, and I wasn't able to locate any of the Smartenit devices in the supported list anymore. It would be wonderful if they could be added back in. Thank you!

Followed Michel's instructions on a Polisy running 3.1.33 / 3.1.35. Update took less than a minute, then a restart. Once the system was back up both AC and the Web interface reported a restart was required. Using AC configuration/restart I restarted the Polisy, once it was back up, both Web and AC still reported a restart was needed. I power cycled the Polisy and everything is working as expected with no more restart messages.

@scote This is how I have my garage door setup with UD Mobile. It's basically an I/O Linc.

If your premise is correct Insteon devices would be dropping dead annually in installation of over 10 dimmers. Yet they don't. So where is the fault? In your logic or somewhere else? In homes with over one hundred dimmers something would be failing weekly and yet they don't. They often last for decades and it's the caps that give out not the flash. Good read though. Well thought out and certainly something to consider, but the facts don't support the supposition.

I think this article is actually really bad advice. This person is rewriting the scenes in their Insteon devices multiple times per day. If you have a scene with multiple controllers in it, that is a lot of memory that is being rewritten in the onboard memory. If they didn't do wear loading with a good size flash chip, you could burn it out pretty quickly. Most flash chips only have about 100K writes per address While I accept your premise, I'm a bit fuzzy on the logic. Accepting your 100K maximum writes per chip which is very arbitrary and often much higher, and the program logic of the article being three changes per device per day, that's (100K/3)/365=91.32 years before I run into a problem. I think I can live with that. The caps will give out long before then. Also while you may not like the solution it is best practice for the IoX / Insteon devices, but if you find a better mouse trap please feel free to share.

Tried to update from 3.1.29 to 3.1.32 three times yesterday, no success. Even tried the one button update on the front panel of my PoliSy. The system says it's updating on AC and on the PG3x web page, beeps with five beeps as if it has updated, but nothing actually changes.

@saclarkdoc You had a previous thread going about a similar issue. So now I'm confused. Do you need to migrate your portal license or are you just looking to approve the portal in AC? For portal migration see the other thread. For portal approval open AC and to go Portal and click approve. Yours should say approve where mine says revoke.

@saclarkdoc login at https://my.isy.io/ and then select your old ISY and navigate to "Migrate to." Now you can select the migration from to and the things you want to migrate.

@John Vickers This article will walk you though how to do what you want.

@Techman I have the same issue as @TheA2Z in that my version dates are not the same for cloud access on a Polisy. It makes cloud access impossible to use from AC. Lan works fine. @DennisC I have not tried portal via the could, but with the mismatch in versions, I doubt it would work any better than local AC access.

@SHM If you have been unsuccessful in updating you Polisy via AC, you can try the front panel button. Keep in mind the update process can take quit a while if it's been a bit since your last update. During the update all three front panel lights will flash green. At the end of the update you will hear 5 beeps then a pause and finally a single beep. That last beep is the notification that the system has restarted. I generally wait another 5 minutes giving IoX time to update all it's link tables, but you can log onto PG3 to verify the update before you start AC. Here are the instructions for the front panel update process. Multi Function Button There's a little multi function button behind the very small hole on the front of the unit. This button has multiple purposes outlined below. Every click on the button will cause the unit to beep. If the button does not behave as described below, please update Polisy. Update and Upgrade All the Packages Click the button once. Please consult support before updating this route. See link below for suggested update/upgrade process. Please see this important update (July 2022)

If after a restart / reboot things still are not working... It is possible that you may have exceed the total number of calls allowed via the free API plan. Other than a configuration issue that is the only other reason I can think of that would preclude you from receiving data. As i recall you are limited to 1000 calls per day. So if you have the NS set to retrieve 7 days worth of data that is 135 calls. If you have hit restart a few times you may have exceeded the daily maximum. I would double check everything from the API key to the NS configuration, I doubt you have actually exceeded the daily limit since you can't seem to get any data, but I wanted to mention it. It's most likely a configuration issue. If it's the daily limit, then waiting 24 hours will resolve your problems.

@oamber I suspect you have not configured OpenWeatherMap. 1.) Create an account on https://openweathermap.org/ 2.) Create an API Key (Free) 3.) Update the OpenWeatherMap NodeSever configuration with your API Key and other info.

@Valveman Here is the link to the Java you should use with IoX. https://www.java.com/download/ie_manual.jsp You will need to first remove the existing Java 20 version for this to work properly.

Upgraded a Polisy from 5.6.0 to 5.6.2. At first all seemed good, but after about 10 minutes AC access became very slow and eventually failed with a jumbled screen. Hard reboot of the PoliSy and AC was still very very slow and quickly became unresponsive. Cleared Java cache and removed AC, reinstalled, rebooted and the problems remain. I'm still trying to sort things out, but wanted to give the community a heads up. This could be isolated to my system, but if you have similar issues please let us know.

I suspect this is an older portal geofence. If you open https://my.isy.io and navigate to Occupancy, I suspect the older entries are there. Deleting them should remove them from AC as well.

I have not tested this and it's just a gut feel. But as @MrBill said, all Insteon devices write links in all devices. Therefore doing what you want to do by simply deleting devices in AC and then restoring the remaining portion of your homes Insteon network would still contain links to the old PLM. A quick way to verify this would be to pick a Insteon device on the 3rd floor and factory default it, then factory default the new PLM on the eISY and then link the device and verify you have full control. While I know you can run multiple Insteon networks in a home; I do that myself with a test network and a production, I really don't think you can grab portions of one and simply restore it to another. There's just to much "contamination" of the old system in all associated devices. I know you are trying to avoid having to build the 3rd floor and basement from scratch, but I don't think you will be able to do it without having ghosts present that will give you fits and create inconsistencies. If there was a tool that allowed you to edit the link DB on each device you could probably edit the link tables, but the time to do that would I suspect be equal to or greater than just rebuilding the system onto the new PLM. Not to mention you would need to be intimately familiar with the Insteon protocol.