
DennisC
Members-
Posts
2786 -
Joined
-
Last visited
Everything posted by DennisC
-
First, try deleting your state files. Instructions are in the wiki. If that doesn't work, try reading this thread:
-
"Upgrade Status Upgrade Complete!" on every re-boot
DennisC replied to x046866x's topic in IoX Support
You don't mention which device you are using and your firmware version? Try power cycling your unit. -
That is used for a factory reset which would return the device to out of the box condition, erasing all programs. If you are back in, make a backup of your device. If you are going to upgrade, and you probably should, you will need to update your firmware to a version that supports migration. Be best to read through information supplied by @Geddy.
-
Let's tag the person who know the correct answer: @bpwwer can you assist?
-
Point of a ticket was to first confirm that was the issue. While UD offers paid support, you are tempting fate with the age of the unit. If it is important to you, it might be time to upgrade to eisy.
-
Isn't there a Delete button on the dashboard? If they apear in any of your ISY devices, delete there from the Nodeserver menu at the top, delete in PG3x, then restart PG3x.
-
I don't think UD is supporting the certificate for this device any longer. You should ask via a support ticket
-
Since moving to eisy, you are now on PG3 version of Polyglot. Prior versions are no longer supported. To get full functionality with plugins on eisy, you will need to delete prior plugins and install using PG3. If you can still sign in to PG version Polisy was using, you might be able to migrate your plugins. You don't say what version of Polyglot you were using, so you will need to read through these to see what fits: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migrating_Node_Servers_to_PG3x
-
Switch from Insteon Hub to UD Polisy
DennisC replied to bpalansky1's topic in New user? Having trouble? Start here
Start here: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide And use this for a programing guide once you are up and running: https://www.universal-devices.com/docs/production/The+ISY994+Home+Automation+Cookbook.pdf -
Does the nodes show up in the admin console? You shouldn't need to be in that window. If there are no nodes in the admin console and you completed the configuration correctly, then the plugin didn't install correctly. Check the plugin log for errors and if nothing shows up reinstall the plugin in the same slot from the Purchases tab of PG3. I haven't used this plugin so I don't know the particular's of the configuration screen, but everything must be correct there.
-
Go to the configuration tab in the plugin and follow the directions for entering configuration info. Make sure admin console is closed, restart plugin, then start admin console.
-
That shouldn't be disconnected. Try rebooting or power cycling Polisy.
-
New problems after replacing PLM
DennisC replied to rick.curl's topic in INSTEON Communications Issues
It is possible there is some noise interfering with the Insteon signal. First step would be to try placing the PLM on a different circuit. Next try turning breakers off one at a time and check if things get better. There are details in the wiki. -
New problems after replacing PLM
DennisC replied to rick.curl's topic in INSTEON Communications Issues
And you changed it why? It doesn't hurt to try a new circuit, just in case something new was added and is interfering, or there is a power supply somewhere going bad. You can use a long cat 5 cable for testing. -
New problems after replacing PLM
DennisC replied to rick.curl's topic in INSTEON Communications Issues
I doubt this will work, but try a restore PLM. You can also try moving the PLM to another circuit. If that doesn't work, the PLM is most likely no good. -
New problems after replacing PLM
DennisC replied to rick.curl's topic in INSTEON Communications Issues
Check the link count for the PLM and check to make sure the PLM shows as connected. How to is in the wiki. -
Take a look at YoLink, I just started using their devices and I have been impressed. They use their own network with a range up to 1/4 mile.
-
When in the admin console, right click on the device and select restore device.
-
red exclamation point next to the telegram service device in Admin console
DennisC replied to baabm's topic in Notification
Did you properly configure the service in PG3 under the Configuration tab for the plugin? The instructions are also on that page. -
It also depends on what features you are looking for. If you only need to be able to open and close, the simplest way is to add a $11 wall pushbutton ((for example Liftmaster: https://www.amazon.com/883LMW-LiftMaster-Button-Control-Security/dp/B07W5RMN56/ref=sr_1_1?crid=2XERV68MZQNDI&keywords=Liftmaster+pushbutton&qid=1701308098&sprefix=liftmaster+push+button+%2Caps%2C102&sr=8-1 ) and a relay (for example, a Zwave relay or Insteon I/O Module). You wire the push button to the GDO and instead of actually pushing the button, you wire the switch closure contact of the relay, to the Liftmaster pushbutton contact. Locate the pushbutton in an out of the way location. Then use ISY to add the Zwave relay or Insteon module. If you want to see position of the GDO you would need to add a door contact sensor. Of cause, if you have an Elk M1, it becomes even easier, use an Elk relay.
-
No worries, hope you are feeling better.
-
I believe the migration documentation does address using a new PLM. "If you are using Insteon Go to the Admin Console configuration tab and make sure INSTEON Support is enabled (default username/pwd = admin/admin) If you are using a new PLM, Restore the PLM." Here is a link to the full migration instructions: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration
-
I'm still having issues, as late as this afternoon. This was after installing another Python Interface update this morning. @bmercier is aware of this and has been working on a solution. I sent him additional log information this afternoon.
-
Don't be surprised if you continue to have this issue after reinstalling the plugin. There is still an issue UD is working on correcting.