mapeter

Hi @Mr B, I will have to hook up the extender again and try overriding the port. Thanks for the tip!

Interesting that you bring this up. I purchased the same extender early February 2024 and it had been working without any issues. Then mid-day on New Year's Day, the eISY stopped communicating with Z-Wave devices. It started working again after a reboot, but only for a couple of hours. I had to plug the ZMatter dongle directly into the eISY for it to be stable again. Looking forward to hearing if others have any ideas.

I opened a ticket over the weekend about the script and Michel's response stated to wait for the next udx release (mid this week). It includes fully tested scripts so that all you have to do is to run couple of commands.

My ISY is back online, but not my eISY. I wonder if the portal stopped taking inbound connections last night and it is slowly resolving itself. Update: The eISY is online now. I did not have to reboot anything.

My ISY and eISY went offline with the portal at 3:29 AM CST today. My USW-Pro-24 switch did an update at 3:28 AM, but not my UDM-SE router. The UDM-SE router updated a couple of days ago with no issues. I have no problem logging into my.isy.io.

Great to hear. Appreciate the response.

Hi @mbking - How is the USB over Cat 5/6 extender working for you? I have a similar situation and thinking about using extenders as well.

Hi @Javi - I used UD Mobile (on iOS) to add Insteon to my new eISY. The PLM was successfully added, but the UD Mobile UI had a couple of issues. Appears to be a minor code copy-and-paste error. While the screen is "Insteon Hardware" screen, it references Z-Wave in the message body. (First screenshot.) While the app was waiting for the reboot to complete, the exception shown in the second screenshot was thrown.

Thanks for the responses. I was going to submit a ticket with the question and decided to bite the bullet and order an eISY instead. I figured it was time to get to the latest hardware platform.

Found an old post stating that PG2 should not be deleted due to UDX and Mongo dependancies. Is it now possible to remove PG2 and use ports 80 & 443 for IoX instead of ports 8080 & 8443?

Thanks the response @Michel Kohanim. Any ETA as to when the enclosures will be back in stock?

I purchased the ZMatter module to install into my Polisy. Now I am thinking I would be better served to install the module inside of the ZMatter USB Enclosure and hang off the end of a USB extension cable to get it away from some duct work as well a prepare for a future migration to eISY. Will an USB enabled ZMatter board work with Polisy, or only with the eISY?

As of last fall, there was not a migration path for node servers. Tagging @bpwwer to see if there are any updates. Here is a related post.

Hi @Javi - I think I found a similar issue with a Z-Wave dimmer. I cannot figure out how to set the INIT value, however. Screenshots below. I tapped on the three dots next to "On"...

I read the instructions to migrate from the 994 to Polisy. What I am not see is how to "repoint" the existing PG3 node servers from the 994 ISY to the Polisy IoP. I currently have both my 994 ISY and Polisy IoP configured as ISYs in PG3. I only have node servers installed for the 994 ISY, however. When the time comes to migrate, do I just delete the Polisy IoP from PG3 and then update entry for the 994 ISY with the local host IP and port 8080, so it points to the Polisy IoP? (After I restore the 994 ISY backup to the Polisy IoP.) Will the UUID shown in PG3 automatically update?

Hi @Geddy - I did submit a ticket and Michel took care of me -- even over the weekends. Ended up reflashing the SSD to get the Polisy updated and now the node server is installed and working well.

Appreciate the help. It is working now. Any thoughts as to why dimmers have the INIT prepopulated with Status but not on/off switches?

Hi @Javi - When creating Favorites on iOS, I have successfully created Switch Widgets for dimmers such as the 2477D, but it is not working for On/Off Switches (2477S and 2487S). As soon as I change the Favorite Type from "Default" to "Switch Widget", an error dialog appears. After dismissing the error, the "Display Status" changes to "REQUIRED!". Attempting to select "Status" for the "Display Status" does not work. The only remedy is to reset the "Favorite Type" to back to "Default". Screen shots are attached. Am I doing something wrong, or is this not working correctly?

Hi @Javi - When I finally migrate from my 994 to the IoP, am I going to have to rebuild all of these customizations in UD Mobile? Will there be a way to export and import on a device-by-device basis?

I think I am on a very old version of PG3. I do have :3000 in my URL. I have started the Update Packages again. Will give it time to run and see what happens. I appreciate everyone's help.

I am going to have to do some more research as my Polisy appears to be really messed up. From the AC I clicked on Upgrade Packages. There is no "Restart Polyglot 3" open in my version of the System menu in PG3. I have clicked on all the Reboot and and Restart menu options as well as clicked on the Reboot option in the AC. It does not appear to be restarting/rebooting. I attempted to SSH into the Polisy, but get the error kex_exchange_identification: Connection closed by remote host

I am finally setting up my first node server on PG3 (version 3.0.36). I "purchased" a trial WirelessTag license and when I attempt to install it into slot 2, the green "installing..." dialog appears. When it finishes up and I return to the dashboard, no node servers are showing up. Below is what I am seeing in the error log. Any thoughts on what is going wrong? 11/9/2022, 15:10:05 [pg3] debug: ########## {"docs":"https://github.com/UniversalDevicesInc-PG3/udi-wirelesstag-poly/blob/master/README.md","longPoll":"600","executable":"wirelesstags-poly.py","status":"active","oauth":"undefined","url":"http://pg3store.isy.io/v2/node servers/production/WirelessTag.zip","name":"WirelessTag","language":"python3","developer":"jimsearle@gmail.com","ip_added":"70.181.79.77","nsInfoPoll":"0","profile_version":"3.1.3","logLevel":"WARNING","ts_added":"1641350502","shortPoll":"60","author":"Jimbo.Automates","version":"3.1.7","discover":false,"prem":true,"nsdata":"{\n \"client_id\": \"REMOVED\",\n \"client_secret\": \"REMOVED\"\n}\n","desc":"CAO Gadgets Wireless Sensor Tags www.wirelesstag.net","authorize":false,"install":"install.sh","purchaseOptions":[{"isTrial":true,"recurringPeriod":"month","recurring":"1","price":0},{"price":20,"isPerpetual":true}],"branch":"","uuid":"REMOVED","ts_updated":"1664077839","price":20,"modified":"9/24/2022 22:50","profileNum":"2","nsid":"7ad25b20-1c13-45ca-9a94-85bd5063815d","expires":1670619543000} 11/9/2022, 15:10:05 [pg3] info: [00:0d:b9:53:dc:04_2] :: Creating Node server 'WirelessTag' 11/9/2022, 15:10:05 [pg3] warn: [00:0d:b9:53:dc:04-2] :: Node server folder exists, removing... /var/polyglot/pg3/ns/00:0d:b9:53:dc:04_2 11/9/2022, 15:10:08 [pg3] error: unhandledRejection REPORT THIS!: Error: Request failed with status code 404 at createError (/var/polyglot/node_modules/axios/lib/core/createError.js:16:15) at settle (/var/polyglot/node_modules/axios/lib/core/settle.js:17:12) at RedirectableRequest.handleResponse (/var/polyglot/node_modules/axios/lib/adapters/http.js:238:9) at RedirectableRequest.emit (node:events:390:28) at RedirectableRequest._processResponse (/var/polyglot/node_modules/follow-redirects/index.js:425:10) at ClientRequest.RedirectableRequest._onNativeResponse (/var/polyglot/node_modules/follow-redirects/index.js:57:10) at Object.onceWrapper (node:events:510:26) at ClientRequest.emit (node:events:390:28) at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:623:27) at HTTPParser.parserOnHeadersComplete (node:_http_common:128:17) at TLSSocket.socketOnData (node:_http_client:487:22) at TLSSocket.emit (node:events:390:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at TLSSocket.Readable.push (node:internal/streams/readable:234:10) at TLSWrap.onStreamRead (node:internal/stream_base_commons:199:23)

Hi @matapan - I did a little testing on this. It appears that a 404 error indicates that the parameter value is not valid for the device. You were attempting to query parameter #2. Try to query it in the admin console. I suspect you will get an error. As an example: Parameter 151 is valid for the device I tested: http://x.x.x.x/rest/zwave/node/ZW018_1/config/query/151 returns: <config paramNum="151" size="2" value="50"/> However, parameter 1 is not valid for teh device I tested: http://x.x.x.x/rest/zwave/node/ZW018_1/config/query/1 returns: <RestResponse succeeded="false"> <status>404</status> </RestResponse>

I purchased a Keene IR Anywhere a few years ago and wrote a proof of concept NodeJS program to fire REST commands to the ISY when it received certain IR commands. When I have some free time I think I am going to use the NodeJS Node Server template and see if I can come up with something that works.

Appreciate the responses and ideas.