
Chris McKean
Members-
Posts
69 -
Joined
-
Last visited
Everything posted by Chris McKean
-
Just migrated from ISY994i ZW+ IR PRO to Polisy IoX with Zwave/Zmatter board yesterday. Everything is working fine except for one device. I have 6 or so Zwave devices that I had to manually install and was able to get all of them to work except for the Zooz Zen34. I am able to get it installed without a problem, but it won't control any devices. It has three options on the switch, Wall Controller, Wake Up, and Basic Control. The basic control, which I assume I would use to control other devices through scenes or programs doesn't have an option to turn it on or off via the ISY. It only has Query. I am able to install it in a scene with the Basic Control as the controller and my light as a responder, but it won't work. Also, if I create a program with IF as the Basic Control on and then the light, still doesn't work when I press the Zen34 switch. I have deleted all of the Zwave devices and reset the Z-wave dongle on the Polisy and reinstalled all devices once already. Any thoughts?
-
I am at v5.5.0, but have not clicked the button on the Polisy Pro (IoX) configuration page to move to Zmatter. I was told yesterday by UDI support that there were additional patches that needed to be applied before I should do that. All of my Zwave devices are currently on my ISY994i with integrated Zwave, but would eventually like to migrate everything over to my Polisy Pro or possibly get the eisy when it becomes available. Right now I'll just play with the Zmatter on the Polisy to learn how that works. But don't want to migrate until it is safe to do.
-
How do you then check and update z-wave device firmware?
-
PG3 backup - nothing happens after hitting download
Chris McKean replied to Chris McKean's topic in Polisy
I submitted a ticket. -
PG3 backup - nothing happens after hitting download
Chris McKean replied to Chris McKean's topic in Polisy
I have the following in the log file. Looks like it is getting an error. 10/21/2022, 18:34:26 [pg3] info: Starting Backup Creation 10/21/2022, 18:34:26 [pg3] error: Backup: TypeError [ERR_INVALID_CHAR]: Invalid character in header content ["content-disposition"] at ServerResponse.setHeader (node:_http_outgoing:606:3) at Object.set (/var/polyglot/node_modules/koa/lib/response.js:467:16) at /var/polyglot/node_modules/@universaldevices/pg3/lib/routes/frontend.js:130:18 at dispatch (/var/polyglot/node_modules/koa-compose/index.js:42:32) at /var/polyglot/node_modules/@koa/router/lib/router.js:372:16 at dispatch (/var/polyglot/node_modules/koa-compose/index.js:42:32) at /var/polyglot/node_modules/koa-compose/index.js:34:12 at dispatch (/var/polyglot/node_modules/@koa/router/lib/router.js:377:31) at dispatch (/var/polyglot/node_modules/koa-compose/index.js:42:32) at allowedMethods (/var/polyglot/node_modules/@koa/router/lib/router.js:433:12) at dispatch (/var/polyglot/node_modules/koa-compose/index.js:42:32) at dispatch (/var/polyglot/node_modules/@koa/router/lib/router.js:353:32) at dispatch (/var/polyglot/node_modules/koa-compose/index.js:42:32) at jwt (/var/polyglot/node_modules/koa-jwt/lib/index.js:73:16) at async /var/polyglot/node_modules/@universaldevices/pg3/lib/services/https.js:54:9 at async compressMiddleware (/var/polyglot/node_modules/koa-compress/lib/index.js:52:5) 10/21/2022, 18:35:12 [pg3] info: set to expire on 2023-07-10T11:58:24.000Z 10/21/2022, 18:35:12 [pg3] info: set to expire on 2023-07-10T11:58:24.000Z -
PG3 backup - nothing happens after hitting download
Chris McKean replied to Chris McKean's topic in Polisy
3.1.11, which I believe is the latest version. Yes, I have restarted PG3. Backup still doesn't work. -
PG3 backup - nothing happens after hitting download
Chris McKean replied to Chris McKean's topic in Polisy
Nothing in the downloaded folder. I click on the download button and nothing happens. -
PG3 backup - nothing happens after hitting download
Chris McKean replied to Chris McKean's topic in Polisy
That is what I expected, but I do not get that. -
On the screen When I click on Download, nothing happens. Does the backup default to a specific folder in Windows? I would expect it to ask me where I want the download to be placed.
-
upgrading PG3 did the trick. Thanks for your help
-
I am upgrading to the latest version of PG3 and will try to upgrade the bond node server then.
-
-
Version of PG3 is 3.0.63. Attached is the log file. Bond_10-19-2022_121418_PM.zip
-
The bond bridge firmware is at version 3.3.19, which is the latest version. I upgraded the bond bridge firmware yesterday, but it was running at 3.3.13 (I believe) before the update. Is it possible that the firmware update is causing this? This morning (per your suggestion), I deleted the bond node server from both the Polisy Pro ISY as well as my ISY 994i. I then went to the node server store and installed the Bond node server just on the Polisy Pro ISY. The node server store shows that the version in the store is 3.0.10, but when I look at the installed version on the Polisy Pro ISY, it shows the version to be 3.0.9. I then tried to discover the devices, got the error message that I needed to reboot the bond bridge. Did that, and then ran discovery again. It found the bond bridge, but none of the devices. I went to the Polisy Pro iSY admin console and the bond bridge is there, but no devices. I have the bond app on my ipad and all of my devices are showing there.
-
I did not delete any devices before I tried to upgrade the node server.
-
Here is the log package attached. I did a discovery and then restarted the Bond node server to see if it would upgrade to 3.0.10. Same as all the other times. Bond_10-19-2022_65642_AM.zip
-
When I logged into Polisy Pro today, it suggested upgrading the bond bridge node server to 3.0.10 by restarting the node server. I restarted and it temporarily shows 3.0.10, but then reverts to 3.0.9 after it restarts. I've done this mulitple times and it does this every time. I have 16 devices, but the only thing that gets discovered is the primary bond bridge. I've added the custom configuration parameters suggested in the 3.0.10 release notes, but still the only thing it finds is the bond bridge. I've powered down the bond bridge and then powered back up before running discovery, but the node server only finds the bond bridge. Any ideas? thanks,
-
Kasa devices disconnect randomly from ISY
Chris McKean replied to Chris McKean's topic in Kasa (TP-Link)
Correction to your question. The Kasa app in Polisy did show 3 devices on the dashboard when it wasn't working on the ISY. The controller and the two devices. I didn't click on the node details to see what was on that page. -
Kasa devices disconnect randomly from ISY
Chris McKean replied to Chris McKean's topic in Kasa (TP-Link)
Even though the app on Polisy detected the basement device via the new ip address, it was not working on the ISY. I did not check the Kasa app to see if the other device was available. Once I stopped then started the app, everything connected again. -
Kasa devices disconnect randomly from ISY
Chris McKean replied to Chris McKean's topic in Kasa (TP-Link)
Thanks! I've bound the current ip addresses for my two kasa devices to their MAC addresses on my router. I have a feeling that this might be the solution. Crossing fingers.... -
Kasa devices disconnect randomly from ISY
Chris McKean replied to Chris McKean's topic in Kasa (TP-Link)
My two Kasa light switches disconnected again today. We did have a power blip last night, but both the Polisy and ISY are both on Uninterruptable Power Supply. Of course, the light switches are not. I checked the Polisy and the Kasa node server is connected. On the ISY, the node server shows as connected. One of the switches shows as connected/true, then other shows connected/false. Neither one will respond via ISY when I try to turn the lights on. I stopped and restarted the node server on Polisy. The log file is attached. I logged back into the ISY and now both devices show as connected/true and they respond to on and off commands via ISY. Kasa_8-31-2022_114107_AM.zip -
I have the KASA node server 3.0.11 running on Polisy. My ISY has that node server with a couple of KASA devices connected. These disconnect randomly from my ISY and after checking the configuration on the Polisy, I am some how able to get them reconnected. Attached is the log file from Polisy. Is there something that I am doing wrong? I like these devices, but they are not reliable right now. Kasa_8-30-2022_71829_AM.zip
-
What do I need to do to get node servers to show up on IoP?
Chris McKean replied to Chris McKean's topic in IoX Support
That worked. I uninstalled the node servers, reinstalled them, ran discovery and they are now showing up in my IoP. thanks for your help. -
What do I need to do to get node servers to show up on IoP?
Chris McKean replied to Chris McKean's topic in IoX Support
I actually checked username password after sending my latest response. It turns out that the IoP was set up with admin/admin on the web interface, so I corrected that. However, it didn't make any difference. Should I remove all of the node servers and reinstall them on IoP? Since I only have three node servers on the IoP, I will give that a try and see if that fixes it. -
What do I need to do to get node servers to show up on IoP?
Chris McKean replied to Chris McKean's topic in IoX Support
When I click on "ISYs" on the web interface, I see both. The first is the IoP and the second one is the ISY994. When I select the first, I can see the node servers installed on the IoP and when I select the ISY994, I see the node servers installed for the ISY994. When I go into the admin console of the ISY994, I have all of the node servers, however, in the admin console of the IoP, none of the node servers are there. I have tried to manually configure one of the node servers on the IoP admin console, but it still doesn't show up. I've deleted nodes for that node server on the PG3 web interface pointing to the IoP, and rediscovered them, but still nothing on the admin console.