kzboray

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.

@KConover It sounds to me like you are not properly configuring the scene. To do what you want you will need to properly configure a scene to change the ramp rate for all attached devices. Take a look at this, it should give you the information you need to create the kind of scene you want. https://forum.universal-devices.com/topic/41015-how-to-setup-automated-brightness-changes-by-time-of-day-with-manual-override-and-alexa-integration/

As @elvisimprsntr said early on in this tread. pfsense and an AP are pretty much your best bet for optimal performance without headaches. There is a learning curve to using pfsense, but plenty of help on the forums and a basic setup isn't much more difficult than an out of the box name brand router.

you might check out... https://www.smallnetbuilder.com/ I've found their reviews to be worthwhile reading.

@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.

This sounds like a communications issue due to line noise. I am making an assumption that this is a relatively new problem and not something you have had to contend with in the past. If that is true, then I would try to recall what devices you have recently added to the home. It could be something as innocuous as an AC charger. There are numerous posts on the forum about how to track down line noise, but here are the basics. INSTEON: Troubleshooting Communications Errors Communication Problems with INSTEON Devices The INSTEON protocol is a much more robust communication protocol than the older X10 protocol that it replaces. However, INSTEON users will sometimes find that while their INSTEON devices seem to communicate reliably between themselves, the ISY will report "Communication Errors" on their power line network. There are multiple reasons for this: The ISY communicates to the INSTEON devices on a power line network via the SmartHome PLM (PowerLinc Modem). The PLM can be less tolerant of weak INSTEON signals and power line "noise" (interference) than the actual INSTEON switch devices themselves. The PLM and ISY require reliable "acknowledgements" of their "requests" to the INSTEON devices. When these are not properly received for any reason, the ISY will display an error. Sometimes this will prevent the completion of an ISY function. Due to these characteristics, a power line network must be as free as possible from substantial interference or signal loss, in order for the ISY to provide error-free INSTEON device monitoring and control. The following tips may be helpful if communication problems are encountered: Move the PLM to a different outlet and one that's not shared with other transformers and power supplies Do not plug a PLM into a power strip that has any type of surge-suppression incorporated, as this can weaken the INSTEON signals. Likewise, certain models of GFCI outlets have also been reported to degrade INSTEON signals (this, however, is not true for all GFCIs). To provide for surge protection for the PLM, ISY, and all of your INSTEON devices, consider using a "whole house" surge suppressor. This can often be supplied and installed by your electric power utility for a minimal charge. If you have old SignaLincs and Access Points, remove them and instead use dual band devices The next points are probably some of the most important: Use power line filtering devices (such as the SmartHome Filterlinc) on all potential signal “sinks” and noise generating devices in your home. Devices such as computer power supplies, televisions, home theater systems, etc, can all act as “signal sinks” that degrade the INSTEON signals on your power line network. Conversely, devices such as low voltage halogen lighting, CFLs (compact fluorescent light bulbs), etc, can generate interference patterns on your power line network that can cause the PLM or even other INSTEON devices to miss INSTEON control signals, which get lost in the background noise on the power line. Even if you have previously installed some power line filters on your system, you may find that more may be required if problems still persist. Also, remember that the bottom outlet on the FilterLinc is the “filtered” outlet. For hard-wired halogen or fluorescent lighting, in-line noise suppressors can be used (such as the Levition Noise Block model 6287). Some CFLs are prone to producing much higher levels of power line noise than others. CFLs that are producing excessive line noise can be replaced with those that produce less interference.

Before you continue to do anything more, please make sure you have backups of both your IoX and PG3 setups. First read the following post and make sure you have followed all the recommended steps. It sounds like you have, but please double check. https://forum.universal-devices.com/topic/37257-polisy-update-process-use-admin-console-upgrade-packages-button/ If that isn't working you can use the front panel button to force an update. 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)

Have you tried resetting your password? See above.

To Access your UD devices PG server on Polisy / eisy open a web browser and enter https://YOUR DEVICES IP:3000/ If this is the first time logging into the Polisy / eisy you will told by your browser that the site is unsafe. Ignore this and continue by clicking on the small print usually saying something like, "Continue to web page" I'm going to cover both PG3 and PG3x, but I believe you have a Polisy running PG3 as you didn't give any product information I'll also cover PG3x on eisy, but most likely you need the Polisy sections. Once you open the web page you should see the following web page. It may say PG3 and not 3X, that is just fine. it's just a slightly different version of PG Now if you haven't set a password use the following login credentials: User: admin Password: admin If you have changed the password and cannot remember what it is you can follow the procedure below to reset the password. Polisy I don't believe Polisy can be updated from AC so you need to use the multi function button on the front panel. The small hole in the front. I use a paper clip to press it. 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. Reset Credentials Press and hold the button till the first LED (from the left) starts blinking then release. This action resets the following passwords to the default (admin/admin😞 SSH Polyglot v2 ISY on Polisy (IoP) Be sure to change the passwords for these sections after you log-in again. eisy simply use AC to change the password. Reset Credentials Starting with the eisy the password is managed through the Admin Console user/pass settings. Changing the admin password in Admin Console (via IoX Launcher) will update PG3x login and will keep the ISY on eisy in sync. It is no longer necessary to change the password in multiple places.

Just a quick follow up to leaving the ISY994 in place or some other device that supports remote access. Not everyone is tech savvy, bu those that are will want guaranties that you no longer have remote access. So you need to not only leave the ISY994 / eisy in place but you need to transfer accounts to their name. That includes any node servers / modules you might have purchased. The last person I did this for sued me for support after the fact. The home was sold as is and even included a stipulation in the contract that any future home automation support would be charged at a rate of $125 an hour (I didn't want the job). Instead they simply sued me and demanded on going support for free while also suing me for damages because I hadn't transferred the Elk module to a Node server on a newer device. All of this was explained to them in writing and in person and they still got pissed off a couple of months later when they couldn't access the alarm to make changes. Not my problem at that point, but I did end up spending money and time dealing with the suite. I recognize this is a worst case, but because I lived through it I am now a strong advocate for simply yanking the HA equipment and never looking back.