Michel Kohanim Posted December 6, 2021 Author Posted December 6, 2021 @MWareman, Thank you very much. I think we didn't increase the string memory enough. @gviliunas, Thank you very much for reporting back. With kind regards, Michel 1
DennisC Posted December 6, 2021 Posted December 6, 2021 I upgraded to v5.2.0 by using the automatic upgrade from within ISY on Polisy. After waiting and trying the Launcher, my Polisy was not found automatically and when adding the IP manually, using the correct port. I ssh in and ran sudo pkg update && sudo pkg upgrade followed by sudo service isy restart. I waited and tried the launcher and it found Polisy, but my UUID was all 0. I tried a reboot which had no impact. I tried sudo service isy restart again and this time my Polisy (and ISY) were found. Even though the version was listed as 5.2.0, when I logged in by selecting LAN, I received the following error: I tried both a reboot and sudo service isy restart, but still get the above message and after clicking ok, ISY on Polisy closes. I tried sudo service isy restart one more time and now I get two instances of Polisy in the Launcher window. Only one will allow me to log in through LAN, both will allow me to login by CLOUD. I tried deleting the entry that is not completely working, but Delete is greyed out. After going in via LAN on the working entry a few times, I find both entries are now working, but I still can not delete one.
mbking Posted December 6, 2021 Posted December 6, 2021 (edited) After upgrading ISY on Polisy from 5.2.0_56 to 5.2.0_58 this morning, I Iost all communications with my Insteon devices through the Admin Console. While doing the upgrade, I executed sudo service isy restart. I did not reboot Polisy this time. I regained communications by powering off Polisy, then the USB PLM, then re-powering the PLM and then Polisy. This corrected the problem and all seems back to normal. I haven't seen this happen on other updates, but then I usually reboot Polisy after an update. @Michel Kohanim, I'm not sure if I did something wrong, but I wanted to pass on the experience and solution in case someone else runs into the same problem. Note: I do have the Zooz S2 Stick 700 plugged into the other USB port on Polisy and have activated it, but have not linked it to any devices yet. Edited December 6, 2021 by mbking
Michel Kohanim Posted December 6, 2021 Author Posted December 6, 2021 Thank you very much for all the feedback. I think the issue stems from the fact that isy depends on udx service. It waits for about 20 seconds for udx to respond. I think, in some cases, udx might be too busy (especially after an upgrade). When isy cannot talk to udx, it will not know its UUID, nor does it know the date and available serial ports. If you look at /var/isy/FILES/LOG/debug.log, I am sure you see something like: couldn't communicate with udx ... With kind regards, Michel 1
mbking Posted December 6, 2021 Posted December 6, 2021 With the Zooz S2 Stick 700 installed and activated, I added a Aeotec Range Extender 7 and a Honeywell (Jasco) Smart Dimmer successfully. Both devices are working as expected. 1
DennisC Posted December 7, 2021 Posted December 7, 2021 After getting PG3 installed on Polisy and connecting it to ISY on Polisy, I installed a Nodeserver. Apparently, the Admin Console on Polisy is missing the ability to scroll down the page. If the Nodeserver is displaying more information than will fit in the window, you can not see the remaining items without making the Admin Console window larger.
sjenkins Posted December 8, 2021 Posted December 8, 2021 After the upgrade my Polisy ISY no longer shows as online in the ISY Portal. Have tried reboots and otherwise. Locally ISY and Node server both work just fine. Except it does not show the portal module any more. Does not seem to be a network issue as my 994 ISY shows up just fine. Thoughts for me to try?
kzboray Posted December 8, 2021 Posted December 8, 2021 @sjenkins You are not alone. I just checked the portal and sure enough the Polisy is listed, but not available. From the local Launcher LAN and Cloud both work fine.
sjenkins Posted December 8, 2021 Posted December 8, 2021 @sjenkins You are not alone. I just checked the portal and sure enough the Polisy is listed, but not available. From the local Launcher LAN and Cloud both work fine.Much appreciated. At least I’ll stop banging my head on it. So as this isn’t stopping me from my next step in transition; I haven’t really begun moving stuff over, I’m still playing to test stability. If a known issue would the team prefer a ticket or just wait a bit? Don’t want to cause undue noise to this excellent development team. SeJ
MWareman Posted December 9, 2021 Posted December 9, 2021 @Michel Kohanim Last Changed Timestamp appears wrong on variables (sometimes) Here is an example I've been able to pin down.. I have 24 programs - each set to trigger on the hour: 'trigger-hourly' is also run by my 'System Startup' grogram - that is set to run on ISY startup (so the minute counter starts on system boot)... The 'trigger-hourly' program does this: So - the 'trigger-minutely' program should run every 60 seconds - and update a variable: I rebooted PolISY at 6:22am - and the 'Last Changed' appears to be 6 hours off. Even though my time offset is 6 hours - it's in the other direction (Zulu is 12:30 at the time of this screenshot). Not sure if this is related to other timezone changes made in the system recently - but thought I'd report it. Here is a screenshot taken a few minutes later - shows the minute is advancing as expected - but the hour is 6 hours off: Michael.
mbking Posted December 9, 2021 Posted December 9, 2021 37 minutes ago, MWareman said: @Michel Kohanim Last Changed Timestamp appears wrong on variables (sometimes) Here is an example I've been able to pin down.. I have 24 programs - each set to trigger on the hour: 'trigger-hourly' is also run by my 'System Startup' grogram - that is set to run on ISY startup (so the minute counter starts on system boot)... The 'trigger-hourly' program does this: So - the 'trigger-minutely' program should run every 60 seconds - and update a variable: I rebooted PolISY at 6:22am - and the 'Last Changed' appears to be 6 hours off. Even though my time offset is 6 hours - it's in the other direction (Zulu is 12:30 at the time of this screenshot). Not sure if this is related to other timezone changes made in the system recently - but thought I'd report it. Here is a screenshot taken a few minutes later - shows the minute is advancing as expected - but the hour is 6 hours off: Michael. @MWareman, I'm having the same issue. The timestamp is correct on a reboot or when I manually change the value in the Variables screen of the Admin Console. They are 6 hours behind when the variables are changed by a program. I'm on Central time. Mark
Michel Kohanim Posted December 9, 2021 Author Posted December 9, 2021 @MWareman, Thank you very much for reporting. We'll take a look asap. With kind regards, Michel 1
larryllix Posted December 9, 2021 Posted December 9, 2021 @MWareman, Thank you very much for reporting. We'll take a look asap. With kind regards, MichelI noticed that also but thought it was related to the LA time zone problem.Sent from my SM-G781W using Tapatalk
MWareman Posted December 10, 2021 Posted December 10, 2021 10 hours ago, Michel Kohanim said: @MWareman, Thank you very much for reporting. We'll take a look asap. With kind regards, Michel Thank you! 1
dinostop Posted December 10, 2021 Posted December 10, 2021 I am going to start to do the transition from the old ISY to the Polisy. My plan is to do it little by little but will I be able to use Polisy as a node server for both the ISY and Polisy at the same time? I understand that for example I would not be able to run my Ecobee thermostats from both the ISY and the Polisy, however if I have that on the ISY on Polisy can I still use the the Polisy to run the node server for say my Bond lights.
bpwwer Posted December 10, 2021 Posted December 10, 2021 9 minutes ago, dinostop said: I am going to start to do the transition from the old ISY to the Polisy. My plan is to do it little by little but will I be able to use Polisy as a node server for both the ISY and Polisy at the same time? I understand that for example I would not be able to run my Ecobee thermostats from both the ISY and the Polisy, however if I have that on the ISY on Polisy can I still use the the Polisy to run the node server for say my Bond lights. Not with PG2. It can only connect to one ISY. You'd have to run an additional copy of Polyglot on something else like a RPi and have one connected to your old ISY and one connected to the ISY on Polisy. PG3 will be able to do this, but it's not production ready at this point.
mmb Posted December 10, 2021 Posted December 10, 2021 Seems I'm not able to upgrade to 5.2.0 from 5.1.1. I've tried the console and it rebooted but did nothing. I tried SSH commands outlined by Michel but no joy, they process but after the reboot I'm still stuck on 5.1.1. Are there any other tricks that I can use to upgrade? Thanks in advance.
rob.bushkaufer Posted December 10, 2021 Posted December 10, 2021 (edited) I tried to update and failed as well. After attempting a number of possible fixes, I ran sudo update -f and found that there is only 1 package listed in the udi repo, and it is the PKG utility. pkg update -f Updating FreeBSD-base repository catalogue... Fetching meta.conf: 100% 163 B 0.2kB/s 00:01 Fetching packagesite.pkg: 100% 10 KiB 10.0kB/s 00:01 Processing entries: 100% FreeBSD-base repository update completed. 113 packages processed. Updating udi repository catalogue... Fetching meta.conf: 100% 163 B 0.2kB/s 00:01 Fetching packagesite.pkg: 100% 1 KiB 1.1kB/s 00:01 Processing entries: 100% udi repository update completed. 1 packages processed. All repositories are up to date. pkg search -r udi -g \* pkg-1.17.5 Package manager Edited December 10, 2021 by rob.bushkaufer added command output
mmb Posted December 10, 2021 Posted December 10, 2021 (edited) On 12/10/2021 at 2:53 PM, rob.bushkaufer said: I tried to update and failed as well. Nice to have company I tried the same command and got the same result but still stuck on 5.1.1 Edit: also lost my PLM in the process. Update 1: Apparently the update process is quite slow, so leaving it overnight finally completed the update. Update 2: I took a wild *** shot in the dark and replaced the USB cable and that fixed it. I've never seen that before. PS: I did re-seat the original cable several times. Edited December 12, 2021 by mmb Update
bgrubb1 Posted December 11, 2021 Posted December 11, 2021 I added a second Ecolink motion sensor - same behavior device configures, but no motion ever detected. Out of curiosity i added I added a Fibaro FGPB-101 zwave button. Same includes, but doesn't see button presses ...Barry
DennisC Posted December 11, 2021 Posted December 11, 2021 18 hours ago, bpwwer said: Not with PG2. It can only connect to one ISY. You'd have to run an additional copy of Polyglot on something else like a RPi and have one connected to your old ISY and one connected to the ISY on Polisy. PG3 will be able to do this, but it's not production ready at this point. Bob, Out of curiosity, if PG3 is able to manage more than 1 ISY, would one of them be able to be at a remote location and connect using ddns address?
rob.bushkaufer Posted December 11, 2021 Posted December 11, 2021 @mmb I ran the below this morning, and the udi repo now shows 420 packages in it. The upgrade also ran successfully, and I appear to have a fully functional PolISY again. sudo pkg update && sudo pkg upgrade service udx restart service isy restart 1
bpwwer Posted December 11, 2021 Posted December 11, 2021 5 hours ago, DennisC said: Bob, Out of curiosity, if PG3 is able to manage more than 1 ISY, would one of them be able to be at a remote location and connect using ddns address? Yes, in theory. I believe it can do name resolution for the ISY IP but I haven't tried that. But the connection would have to work both ways. PG3 will connect to the ISY via an IP address/port number. As long as the IP/port is reachable, it will work. But the ISY also needs to communicate with PG3 (mainly to send commands back) so it needs to be to reach the http(s) IP and port that PG3 is using.
garybixler Posted December 11, 2021 Posted December 11, 2021 Hi, Just looking for some info. I just received my first Z-Wave device to experiment with on the Polisy ISY. The device is the ZooZ ZEN16. I have it linked to the ISY with no problem. Can't figure out what all the nodes are for. The ZW002.1 On-Off Power Switch node does in fact turn the relay 1 on and off but associated with that is ZW002.1 Basic Control 2 which has no status and seems to have no function. Also when trying to set configuration parameters for the ZEN16 I just get an error. Thanks for any insight. Gary
Techman Posted December 11, 2021 Posted December 11, 2021 1 minute ago, garybixler said: Hi, Just looking for some info. I just received my first Z-Wave device to experiment with on the Polisy ISY. The device is the ZooZ ZEN16. I have it linked to the ISY with no problem. Can't figure out what all the nodes are for. The ZW002.1 On-Off Power Switch node does in fact turn the relay 1 on and off but associated with that is ZW002.1 Basic Control 2 which has no status and seems to have no function. Also when trying to set configuration parameters for the ZEN16 I just get an error. Thanks for any insight. Gary Sometimes when installing Z-wave devices you'll end up with extra phantom nodes. I just create a folder and move those nodes to the folder and ignore them. Not sure exactly what your configuration issue is. You could be entering an incorrect value. When you do enter a value be sure to click in the "set configuration" button to the left 1
Recommended Posts