-
Posts
5341 -
Joined
-
Last visited
Everything posted by Techman
-
The $80 price is from a 3rd party reseller, Aeotec usually sells them on Amazon for about $62
-
The Aeotec Zwave Multisensor 6 works flawlessly with the ISY and has great tech support from Aeotec. They are scheduled to release the Multisensor 7 but are delayed due to parts shortages. Their link is below. MultiSensor 6 Z-Wave motion, light, temperature sensor (aeotec.com)
-
Support thread for: ISY on Polisy (IoP) v5.4.0 (Feb 28, 2022)
Techman replied to Geddy's topic in IoX Support
If you click on the TPM button it will ask you to create a strong password. You can either move forward with enabling TPM or cancel, your choice. -
Support thread for: ISY on Polisy (IoP) v5.4.0 (Feb 28, 2022)
Techman replied to Geddy's topic in IoX Support
Updated via SSH Polisy is now back to normal I was also able to update the pending (4) packages via the Polisy IP address -
The bugs are being addressed, see the link below.
-
Support thread for: ISY on Polisy (IoP) v5.4.0 (Feb 28, 2022)
Techman replied to Geddy's topic in IoX Support
I verified, via ssh, that the 5.4.0 update was successful but I'm unable to reboot polisy from the admin console or by logging in via it's address. Still no beeping from the Polisy and I now have a solid left led and a flashing middle led. When I log in via its IP address it shows 4 packages available for update but now the update command doesn't work -
Support thread for: ISY on Polisy (IoP) v5.4.0 (Feb 28, 2022)
Techman replied to Geddy's topic in IoX Support
Pushing the reset button 6 times cleared the flashing led issue. Previously I was also getting an error message when I tried to access the admin console via the cloud, that issue is also cleared up. I still am not getting any audio beeps when I reboot the Pol;isy I also just noticed that when I try to reboot the Polisy from the admin console nothing happens. -
Support thread for: ISY on Polisy (IoP) v5.4.0 (Feb 28, 2022)
Techman replied to Geddy's topic in IoX Support
I updated to 5.4.0 and now the left Polisy led is rapidly flashing. I tried soft and hard reboot to no avail. I'm able to access the Polisy via the admin console and it appears to be working as it should. Any thoughts? -
Based on your previous screenshot you don't have the pro version. It would show "PRO" after the ISY994i The standard ISY994i supports 255 nodes. The pro version supports 1024 nodes. Scenes, folders and device nodes all count towards the total number of nodes supported.
-
Is the Zwave box checked, and saved, in the Polisy configuration window? If so, the then do a reboot on the Polisy by pushing the reset button ONCE in the right front of the polisy using a paper clip,
-
I noticed that you don't have the ISY PRO upgrade. It's possible that you're low on resources. Click on TOOLS | DIAGNOSTICS | SYSTEM STATUS and take a look at your memory availability. Also do a PLM link count to see the PLM usage. Your, firmware and UI look OK
-
The garage door opener motor can create noise on the powerline which can interfere with the Insteon signal. I had to use a powerline filter between the opener and the powerline. Sometimes an additional dual band device close by will help, preferably a plug-in device which has an external antenna. To check your PLM, make sure the green led is on. Run a diagnostic PLM link count. If the count is unusually low then you could have a failing PLM. Best to do the count when the PLM is inactive as you'll get a more accurate link count. What's the hardware version and date code on your PLM. Older PLMs have had issues.
-
The 170001 is not an error, it's an informational message. Re: the time stamp, make sure your Polisy is displaying the correct time zone and time. SMTP servers that require an encrypted connection usually use port 587.
-
Try using port 587 In the test message make sure all the fields are populated
-
To factory reset: Insert the end of a paperclip into the little hole in the right front of the Polisy: Factory Reset Press and hold the button till all LEDs start blinking then release. This action resets the credentials, removes all configurations from Polyglot/Polisy, and resets networking.
-
What's the version and date codes of your old and the new PLMs The newer PLMs have an improved rs232 interface and improved power supply.
-
UDI does not recommend updating the Zooz Zwave dongle firmware at this time as their development is based on the firmware the dongle shipped with.
-
@btreinders Most likely either your link tables in the ISY were corrupted before you did the PLM restore, or the PLM restore got corrupted. What you can try rather than deleting and re-adding devices is to do a restore device on the devices in a scene. You can also try removing the device from a scene then adding it back. Both of these options are painless and shouldn't take a lot of time. Try this with one scene that isn't working to see if it cleans up your problem
-
Did you clear your Jave cache and applications then reload the ISY launcher after you went back to 4.9.0? It appears that you have a security issue between the door lock and the ISY, you may have to move to lock closer to the ISY to properly install it.
-
The PLM restore either didn't properly write the link tables to the new PLM or the old PLM was buggy and/or failing and when you did the restore it wrote the buggy links to the new PLM which is what most likely happened. It's best to go through each program and device to make sure it's working Do you have any battery-operated devices in your set up?
-
@btreinders Either the PLM restore to the new PLM didn't properly write the link tables or your programs may need a tweak. Take a look at the programs to make sure they're working. Are you able to control the devices in the scenes individually from the device tree, if not then the PLM restore may have not properly completed.
-
Help with keypadlinc turning itself off.
Techman replied to Illusion's topic in New user? Having trouble? Start here
@Illusion If the new KPL that you have coming reacts the same then it's possible that the ISY link tables for that device somehow became corrupted. Your only option would be to delete it from the ISY and then add it back as a new device. This assumes that you previously did a "Replace device"