
pjjameso
Members-
Posts
338 -
Joined
-
Last visited
Everything posted by pjjameso
-
Well for some reason it decided to pair.... Looks like Im good to go at this point. Thanks to everyone for the help.
-
Tried deleting NS and adding back with the same results.... Just gotta find that special button! HueEmulator_4-23-2022_35727_PM.zip
-
Changed Hue port to 8081 and checked that listen was true. Same issue when trying to setup, harmony asks me to "Press the center button in the bridge to pair it with Harmony Hub". HueEmulator_4-23-2022_31719_PM.zip
-
Switched the HUE port to 80 to see if that makes any difference, Harmony finds the HUE but Im stuck at the point where Harmony asks me to pair with HUE by pressing the center button. Eventually fails the pairing process.
-
Just setting up Harmony Elite with the Node server. I am able to see my switches on the harmony remote and they are correctly indicating the status when switched on and off in the ISY. However they are not able to control the switches directly, almost like the command is not been sent. Is the Hue Port 8080 suppose to be the same as the ISY 8080? 2022-04-23 11:42:52,869 Thread-259 pyisy WARNING connection:request: Bad ISY Request: http://192.168.4.6:8080/rest/nodes/10972/cmd/DOF 404: retry #0 2022-04-23 11:42:53,923 Thread-259 pyisy WARNING connection:request: Bad ISY Request: http://192.168.4.6:8080/rest/nodes/10972/cmd/DOF 404: retry #1 2022-04-23 11:42:54,947 Thread-259 pyisy WARNING connection:request: Bad ISY Request: http://192.168.4.6:8080/rest/nodes/10972/cmd/DOF 404: retry #2 2022-04-23 11:42:55,972 Thread-259 pyisy WARNING connection:request: Bad ISY Request: http://192.168.4.6:8080/rest/nodes/10972/cmd/DOF 404: retry #3 2022-04-23 11:42:57,032 Thread-259 pyisy WARNING connection:request: Bad ISY Request: http://192.168.4.6:8080/rest/nodes/10972/cmd/DOF 404: retry #4 2022-04-23 11:42:58,057 Thread-259 pyisy WARNING connection:request: Bad ISY Request: http://192.168.4.6:8080/rest/nodes/10972/cmd/DOF 404: retry #5 2022-04-23 11:42:58,058 Thread-259 pyisy ERROR connection:request: Bad ISY Request: http://192.168.4.6:8080/rest/nodes/10972/cmd/DOF 404: Failed after 5 retries 2022-04-23 11:42:58,059 Thread-259 pyisy WARNING nodebase:send_cmd: ISY could not send off command to 10972. 2022-04-23 11:43:32,809 Thread-487 udi_interface WARNING Controller:longPoll: Listen Count = 4 Thoughts on what to try at this point?
-
Thank you for your response, i have sent eden a note asking if they have a public api.
-
Curious, I have an Eden bluetooth water timer where i can set frequency, time to water etc using an app on ios. How would one go about integrating this in Polisy? How would one create a Node server for this. Of course what i would want to do is combine with my ambient weather station to turn off watering when rains x amount in a week. Just curious but would pay for the Node server if anyone so inclined.
-
Thank you for the quick response. Query fixed the Node server Online question. I have resynced twice and restarted nodesever for good measure and still seeing the UOM Suffix is null. Any other thoughts?
-
When using the UD Mobile app when I inspect the ELK Controller the ELK M1EXP Connected shows True, yet the Node server Online shows Disconnected. Is this expected? When I inspect n003_area_1 (Area Node) it throws and error UOM Suffix is null. How do I fix this issue? Finally, understand arm/disarm is currently broken in the app but when it was working where would I find the button to push to arm or disarm. Just want to be on the lookout for the option when available. Thanks in advance.
-
So I thought i would try the zooz zen17 universal relay, good choice as everything is working as expected.
-
Solved the secure add issue my moving closer to zooz. Still having issue where the second relay and sensor are not showing in Polisy. Have updated Zooz to 7.17 removed and added ForentzZ several times with the same result (yes i realize thats the definition of insanity... expecting a different result). Attached is the log of the last attempt and the documentation for the FortenzZ which again was working perfectly on the 994i. The fail message in the log is Thu 04/14/2022 05:07:54 PM : [ZW-TX-FAILED] enc=Fail uid=12.0 cmd=0x8E.02 MULTI_CHANNEL_ASSOCIATION. Probably just my vision but appears while installing second relay and sensor its using the same name? Cursor highlight appears to be flipping back and forth in the node tree. Thanks for the assistance in advance.. ISY-Events-Log.v5.4.3__Thu 2022.04.14 05.09.15 PM.txt User+Manual+MIMO2++8May2017+removed+MI+address.pdf
-
I keep getting an unable to securely add device which limits me to one relay. This worked in 994i as im just trying to migrate to polisy. Any thoughts?
-
Figured it out, my error naturally, was pointed to ISY994 vs Polisy on dashboard
-
Just tried buying the version and same issue as unable to load uuid. Shows purchased but unable to install. P
-
New to Polisy and trying to install ELK in Polygot 3. When I try to install after purchasing TRIAL I am not able to populate the uuid hence I get a fail. Also when i go to the purchases tab it nothing shows in the tab... What am i doing incorrectly, first installed in poly 2 but have deleted that node.
-
Thanks everyone, Polisy is dead, Michael is sending boot chip. Must admit I should have been more careful instead of just just assuming rj45 from 994 would plug into ports on Polisy. Would have thought db9 ports long ago unused/deprecated and followed 994 mode. Dumb me… Appreciate the help on my journey form insteon to…. Well at least i have two spares of PLM’s and keypads!
-
Dang, missed that point... was using rj-45 port as done with 994. Now issue is it wont boot, just the right most light is lit. Next steps?
-
Elapsed 00:00:05.368 : Loading Variables Elapsed 00:00:05.710 : Loading Node Definitions Elapsed 00:00:06.441 : Loading Nodes Elapsed 00:00:06.540 : Creating Widgets Elapsed 00:00:07.717 : Creating Widgets Complete Mon 04/07/1952 04:17:55 PM : Starting Subscription Mon 04/07/1952 04:17:55 PM : Completing initialization Mon 04/07/1952 04:17:55 PM : Refreshing Status Mon 04/07/1952 04:17:55 PM : Refreshing Views Mon 04/07/1952 04:18:00 PM : [ZWAVE-SERIAL ] Using serial port [/dev/ttyU0] Mon 04/07/1952 04:18:01 PM : [ZW-SOFT-REBOOT] START - zwaveSoftReboot 0x7fffffffb950 Mon 04/07/1952 04:18:06 PM : Restarting the Z-Wave dongle Mon 04/07/1952 04:18:13 PM : [ZW-SOFT-REBOOT] FINISH - zwaveSoftReboot 0x7fffffffb950 Mon 04/07/1952 04:18:14 PM : [ZWAVE-FW ] Unrecognized Z-Wave firmware version/library [7.15] Mon 04/07/1952 04:18:15 PM : Z-Wave Node ID : 0x01 (1) Mon 04/07/1952 04:18:15 PM : Primary : true Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent Mon 04/07/1952 04:18:16 PM : [PLM ] PLM not initialized, command not sent
-
Sorry wrong nomenclature.... not db9 but rj-45. Have factory reset with PLM powered up and plugged into the Polisy. Triple checked that insteon and z wave are enabled after boot up. Still no communication with PLM; not connected 0.0.0.0. PLM connected to middle rj-45 jack.
-
Didnt make a difference booting up with PLM plugged into Polisy DB9. Are the lights on the db9 port suppose to indicate any activity on PLM, if so then Polisy must be the issue.
-
Does the PLM need to be plugged into the Polisy prior to the Polisy boot up? If thats the case I plugged in after the boot up. Will give that a try...
-
Just received my Polisy and having an issue setting up using previous 2413s PLM. I have insured that insteon and zwave are enabled and have rebooted ISY on Polisy. Restored my 994 backup, but keep receiving comm errors, with PLM 0.0.0.0 unconnected. Have factory reset Polisy, repeated the procedure to no avail. Reconnected my plm to the 994 and all works fine. Just cant get the Polisy to connect to the PLM. Have tried both db9 ports far left and middle with same results. Using same db9 cable that I was using with the 994 What am i doing wrong?
-
Thank you for pointing to the templates and instructions, will give it a go! Will most likely be back with more questions.
-
Thank you to all.....