Everything posted by DennisC
-
All INSTEON Devices Not Reachable
It doesn't matter if it was working before or not. If you are sure at least one of the PLM's you have are working, then you need to troubleshoot the current problem. All things that stop working worked before, now its time to troubleshoot the existing problem. Are there any clues in the error log? Being that all Insteon stopped working, I am not totally convinced your problem is not a bad PLM. What does Tools - Diagnostics - PLM Info/Status show?
-
All INSTEON Devices Not Reachable
Take a look here: https://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors
-
All INSTEON Devices Not Reachable
Yes, it sounds like your original PLM died. When you change PLM's, you need to restore the PLM. Take a look here:
-
‘Updated packages’ and ‘different subscription (restart!)’ dialogs--NOT!
FYI If you haven't, see my post about 3 or 4 post above this one.
-
All INSTEON Devices Not Reachable
What is your firmware and UI version? If they are not both the same then you need to correct that. If you are running an ISY994, you should be on v5.3.4 if you have a 500 series ZWave board or v5.0.16 for a 300 board. If not, you need to upgrade packages and download a new Launcher. If you still have an issue: Try removing power from PLM and ISY. Plug in PLM, wait about 30 seconds after green light comes on, and then plug in ISY. Wait about 10 minutes before logging in to admin console. If you still have an issue, clear Java cache, including program's, and download anew copy of start.jnlp, which will install a fresh version of the Launcher on your desktop.
-
Migrate ISY994i (5.3.4) to Eisy (5.5.7) and start.win
After enabling Insteon support, did you reboot? You don't me tion it in your write up. Is it possible you missed a step when migrating? Review the latest procedure here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration If nothing else works, try upgrade packages followed by a reboot.
-
All INSTEON Devices Not Reachable
Try checking the PLM links and see how .any there are. I agree, it sounds like your PLM died. Is the green light on at the PLM?
-
Trying to open a support ticket
Try a different browser.
-
Trying to open a support ticket
I just checked and I see the check box just fine using Chrome browser. Are you on a computer or mobile/tablet device? If on mobile or tablet try clicking on Desktop Site in browser menu.
-
‘Updated packages’ and ‘different subscription (restart!)’ dialogs--NOT!
Yes, both the update packages and subscriptions notices are known issues. I know they found the issue with the subscription issue and it will be in the next release. I still get both of these.
-
Devices are not updating status.
What about the error log? Try right clicking on one of the devices in question and select restore device. It really sounds like you are having communication issues.
-
Sense node data comparison is clamped
Sounds like something you need to open a support ticket with UD for. Here is the link: Open UD Support Ticket
-
Devices are not updating status.
What kind of devices are we talking about - Insteon, ZWave? Have you looked in the error log? You might be having communication problems.
-
Random On Events not appearing in logs
Try right clicking on each device one at a time and selecting Diagnostics - Show device link tables. After the process runs, click on compare. This should tell you if any clinks have been mis-matched. If there is a mis-match or if you want to skip the first step, right clicking on each device involved and select restore device. That will re-write the data in the ISY's memory.
-
eIsy migration, Unable to login to Polyglot V3
Yes, you need to add eisy to the UD Portal and then you need to approve it in the eisy Configuration - Portal tab. Are you migrating from an existing ISY or Polisy, or setting eisy up as new or additional device? If migrating, did you migrate your portal? Determine which case you fit and follow the directions here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration
-
New Insteon devices and Isy
Yes, there is a migration procedure. https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration Note: If you are using Insteon and you do not have a USB PLM, you will also need the UD cable kit to convert your serial PLM to USB.
-
New Insteon devices and Isy
A few things will need to happen. First,the new Insteon team will need to share the design information with UD. In the past, this was a problem. As previously stated, ISY994 is at end of life and we have been told there will not be any further development. That being said, there is a small chance UD would release an update for new devices. If it is of interest to you, your best chance of being ready for it if Insteon releases the information would be to update to UD's new hardware, eisy.
-
PG3 Not Working On Mobile
@Javi I was having the same issue with UD Mobile crashing. I was finishing up migrating to eisy and didn't want to muddy the waters, so I set it aside. As a suggestion, maybe UD could consider setting up a known issues page across the product line?
-
Insteon Devices - Inconsistent/Unreliable Communication
Could it be your cable?
-
Connect to https resource with self signed cert (hue hub api v2)
That's good, what about the error log?
-
Eisy not responding to button commands etc.
Go ahead and create a ticket with the closest match. In the description, mention you are on eisy. If power cycling isn't getting you in, you will need UD support. You can ignore the popup for updating packages for now, it is a known bug. The latest version is 5.5.7.
-
Connect to https resource with self signed cert (hue hub api v2)
In the thread you posted, Michel replied: "DO NOT check the Verify button. You'll make things worse. Please make sure you are using TLS1.2 / Strength All, SNI checked and timeout 10000. If that does not work, something else is wrong." I don't see the settings you posted as matching Michel's recommendation. I would start there and then if it doesn't work, check the error message. Can't tell, are you using TLS1.2? You don't have SNI checked. Does it work from a browser?
-
Why do my programs stop after a day or so whenever I restart my IoX?
First, I think you did "copy" and not "copy to clipboard" which is at the bottom of the list after right clicking. I am bringing this up because on a long post it is hard to read and scroll to the right to see the entire program. When you use "copy to clipboard" the entire program is plainly visible without scrolling right. This will make future questions much easier to follow along. I'm only looking at what I think is your heartbeat program, do I have this correct? If so, to align your program with the example, I think it should be modified to be: Leak Sensor #10 - Variable Control 2a-25 - [ID 0074][Parent 001C] If 'Leak Sensors / LS#10-Basement-Workshop- Dry / LS#10-Basement-Workshop- Hea' is switched On Or 'Leak Sensors / LS#10-Basement-Workshop- Dry / LS#10-Basement-Workshop- Hea' is switched Off Then $sLeak_10__workshop = 1 Wait 25 hours $sLeak_10__workshop = 2 Else - No Actions - (To add one, press 'Action') Let's get the basics working before adding anything else to the program. After that, keep an eye on it and see if the variable updates. Also, can you confirm that the variables you have created starting with $i are Integer Variables and the ones starting with $s are State Variables?
-
Noob questions and advice
Take a look at these ZWave devices: https://www.getzooz.com/
-
Unable to connect 1.0.21 and 5.5.7
Thank you! All good now.