JTsao

What would be the best process to get from Polisy/PG2/Zooz/PLM1 to eISY/PG3/ZMatter/PLM2? I think know the 1st step and have done this - 1: upgrade all node servers from PG2 to PG3 while still on Polisy/Zooz/PLM1. So, now from Polisy/PG3/Zooz/PLM1 what is the best process to get to the end point? 2: backup IoX from Polisy 3: backup PG3 from Polisy 4: power down Polisy 5: move Zooz USB dongle and PLM1 from Polisy to eISY 6: power on eISY, update eISY by pressing button in IoX and reboot 7: restore IoX to eISY 8: restore PG3 to eISY (and reboot?) 9: transfer PG3 node server licenses? (Not sure about how this works) - change ISY Portal connections to new eISY 10: now at eISY/PG3/Zooz/PLM1, test everything to make sure it is working and fix if not... 11: wait for UD to debug migration tool 12: run migration tool to go from eISY/PG3/Zooz/PLM1 to eISY/PG3/ZMatter/PLM1 13: run replace PLM procedure to get to eISY/PG3/ZMatter/PLM2? (Note: PLM1 = 2448A7, PLM2 = USB PLM) I think it would be useful to have a step by step process for this worst case scenario of updating everything - obviously some users would not have to do all steps. Is the "migration tool" that is referenced in the forums only for updating the Zooz USB stick to ZMatter? Would it be better to migrate to ZMatter while on the Polisy? Is there any way to overlap both the Polisy and eISY during any of this process to reduce risk?

Wow, that sounds like a nightmare - I do have the ZMatter board and am waiting on the USB enclosure - as such, I wanted to try and push things to get the best performance possible out of the ZST10 before switching, but obviously I don't want to break anything to the point where nothing works... also, I wanted to wait until the migration capability exists so I don't have to re-enroll all of my z-wave devices and fix all of the programs Someone earlier in this thread mentioned that he thought 7.17 was necessary - sometimes it's difficult to have to read through these forums to get the information that you need or want

I downloaded the latest Simplicity Studio and firmware version 7.18 and followed the processes described here in this thread to update the ZST10 - this was my first update since buying the ZST10 almost 1 year ago. I am not 100% sure yet, but I believe I may be seeing some improved performance with 7.18 - some devices that were problematic seem to be communicating better to the IoP. Also, some new nodes have shown up for some of the devices. I have approximately 30 Zwave devices all of type 500 or 700 including 3 battery powered locks (2 U-Tec and 1 Schlage). Has anyone else tried 7.18?

Will the advanced zwave features be available if you use the Polisy+ZMatter? Will the migration tool allow Zooz -> ZMatter migration on the Polisy, without having to purchase the eISY? Since the Polisy is supposed to be supported until 2025, I am considering just running it for as long as possible instead of purchasing the eISY. (Unless there is a compelling reason to upgrade). If history repeats itself, the eISY could be replaced by something else within 2-3 years anyways.

Not sure if I am 100% back yet as I think there is a Query All running but the "Upgrade Packages" button did nothing - so I read all the pages of this thread and tried a couple of different things that people mentioned: First I tried this (using a putty SSH session): sudo pkg update sudo pkg upgrade pkg This seemed to result in an endless loop, so I control C'ed out of it and did this: sudo pkg install -r udi pkg sudo /usr/local/etc/udx.d/static/udxops.sh upgrade.polisy I think this is what I should have done instead- After this, running the IoX A/C - I got the version mismatch message, then had to clear my java cache and now the admin console comes up and I am at version 5.5 - still have to see if anything was broken, though... Update: everything seems to be back and I am running 5.5 - FWIW the button definitely did not work for me, but it did for the previous upgrade to 5.4.5

Dumb question here - I just pushed the upgrade packages button and it only closed the admin console - no beeps or anything... very different from the upgrade to 5.4.5 - do I need to install the ZMatter before the update? Is that something that is checked? I thought that I could just go to 5.5 - I've ordered the ZMatter USB enclosure and am thinking about ordering the eisy but just wanted to update to 5.5 as-is

I have the exact same questions

1) Just to be clear, I can upgrade to v5.5 and continue to run with my Zooz USB stick and Insteon USB PLM, right? (as long as I don't push the migrate button) 2) Also, I don't see any mention of this working with the ZMatter board mounted inside the USB Enclosure and plugged into a Polisy USB port - will this method also work for the ZMatter migration? Or does the board have to be installed inside the Polisy? 3) If the enable TPM button is not greyed out, do I need to try pushing and enabling prior to ZMatter migration? Just my 2 cents but I'm not going to be an early adopter on this one if I risk having to re-enroll all my Z-Wave devices...

Well, now I wished that I had waited to buy the entire USB ZMatter Dongle - one more thing - there is supposed to be a member discount to get the USB enclosure - I logged into my ISY Portal account but still don't see a discount - is there another type of member or does the UD Store have a problem?

I am currently running IoP and PG3 on the Polisy Pro - I purchased and have received a ZMatter board, which plugs into the Polisy Pro box in one of the expansion slots - but it appears to me that (please confirm each) 1) I can purchase a USB enclosure for the ZMatter board for eISY 2) I can also use the ZMatter board in one of the Polisy Pro USB ports if I buy and put it into the enclosure 3) So there are two ways for the Polisy to use the ZMatter board? Internal slot OR USB Port? 4) And either one works? 5) And now you can purchase the ZMatter USB Dongle which = ZMatter board + enclosure? If all of the above is true, then I'm purchasing the USB enclosure and putting the ZMatter board on the end of a USB extension cable, which is exactly how I have the current USB sticks for ZWave (Zooz) and Insteon (2448A7) Finally - any benefits or advantages to using ZMatter in the slot vs. the USB Port?

It turns out that Weatherbit changed the frequency at which you can get data for the free plans - short poll has to be >= 1800 and long poll >= 43200 If you poll too often, you'll get errors Now I need to figure out why it's raining right now and the rain rate = 0.0000...

I updated to PG3, changed my short and long poll as advised (1800, 43200) and Weatherbit otherwise seems to be working, but I have noticed that the temperature and rain rate didn't seem to be changing and I see the following in the log file (below) - is this a problem? 2022-12-07 01:28:51,138 Thread-457 udi_interface ERROR udi_interface:write: Exception in thread 2022-12-07 01:28:51,142 Thread-457 udi_interface ERROR udi_interface:write: Thread-457 2022-12-07 01:28:51,143 Thread-457 udi_interface ERROR udi_interface:write: : 2022-12-07 01:28:51,143 Thread-457 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-12-07 01:28:51,144 Thread-457 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner 2022-12-07 01:28:51,149 Thread-457 udi_interface ERROR udi_interface:write: self.run() 2022-12-07 01:28:51,150 Thread-457 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 917, in run 2022-12-07 01:28:51,154 Thread-457 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2022-12-07 01:28:51,155 Thread-457 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db953c604_6/nodes/Controller.py", line 128, in poll 2022-12-07 01:28:51,157 Thread-457 udi_interface ERROR udi_interface:write: self.q.query_forecast(False) 2022-12-07 01:28:51,157 Thread-457 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db953c604_6/nodes/query.py", line 154, in query_forecast 2022-12-07 01:28:51,159 Thread-457 udi_interface ERROR udi_interface:write: node.update_forecast(f_obs, float(self.elevation), float(self.plant_type), float(jdata['lat'])) 2022-12-07 01:28:51,160 Thread-457 udi_interface ERROR udi_interface:write: AttributeError 2022-12-07 01:28:51,161 Thread-457 udi_interface ERROR udi_interface:write: : 2022-12-07 01:28:51,162 Thread-457 udi_interface ERROR udi_interface:write: 'NoneType' object has no attribute 'update_forecast' 2022-12-07 03:01:01,588 Command udi_interface ERROR udi_interface:write: Exception in thread 2022-12-07 03:01:01,590 Command udi_interface ERROR udi_interface:write: Command 2022-12-07 03:01:01,590 Command udi_interface ERROR udi_interface:write: : 2022-12-07 03:01:01,591 Command udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-12-07 03:01:01,592 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner 2022-12-07 03:01:01,596 Command udi_interface ERROR udi_interface:write: self.run() 2022-12-07 03:01:01,597 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 917, in run 2022-12-07 03:01:01,601 Command udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2022-12-07 03:01:01,602 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 680, in _parseInput 2022-12-07 03:01:01,606 Command udi_interface ERROR udi_interface:write: NLOGGER.setLevel('DEBUG') 2022-12-07 03:01:01,607 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 811, in _handleInput 2022-12-07 03:01:01,611 Command udi_interface ERROR udi_interface:write: #LOGGER.debug('notices: {}'.format(item)) 2022-12-07 03:01:01,612 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db953c604_6/nodes/Controller.py", line 136, in query 2022-12-07 03:01:01,613 Command udi_interface ERROR udi_interface:write: self.q.query_forecast(True) 2022-12-07 03:01:01,614 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db953c604_6/nodes/query.py", line 154, in query_forecast 2022-12-07 03:01:01,616 Command udi_interface ERROR udi_interface:write: node.update_forecast(f_obs, float(self.elevation), float(self.plant_type), float(jdata['lat'])) 2022-12-07 03:01:01,617 Command udi_interface ERROR udi_interface:write: AttributeError 2022-12-07 03:01:01,618 Command udi_interface ERROR udi_interface:write: : 2022-12-07 03:01:01,619 Command udi_interface ERROR udi_interface:write: 'NoneType' object has no attribute 'update_forecast' 2022-12-07 08:31:18,399 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-12-07 08:31:21,837 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.51 Starting... 2022-12-07 08:31:21,980 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.15 [ISY: 5.4.5, Slot: 6] 2022-12-07 08:31:21,983 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.2.60', 'netmask': '255.255.255.0', 'broadcast': '192.168.2.255'} 2022-12-07 08:31:21,986 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2022-12-07 08:31:22,007 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2022-12-07 08:31:22,010 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2022-12-07 08:31:22,011 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '2.0.6'}} 2022-12-07 08:31:22,831 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2022-12-07 08:31:22,833 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:53:c6:04_6 - MID: 1 Result: 0 2022-12-07 08:31:22,887 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,) 2022-12-07 08:31:25,021 MainThread udi_interface.interface INFO interface:addNode: Adding node WeatherBit Weather(controller) [None]

Does anyone have IoP programs that check the status of node servers (off-line / on-line) and generate a message if there is an issue? Is there a compelling reason to do this?

Some things have always been kind of sluggish for me with IoP + PG2: 1-pressing a remote control (Harmony Hub/Home control button) button to control lighting (Virtual + Harmony Hub NS) has some really long delays sometimes 2-Z-wave motion sensors turning on lights has fairly long delays I think #1 seems improved after going to PG3

Yes running it all on a Polisy +IoP - I guess I'll just leave it alone for now - I saw somewhere in the forums that PG2 may still be required due to a process called mongod? (or something like that) - so I don't want to break anything

Just moved 9 node servers from PG2 to PG3. Is there anything that can be done to shut down PG2 (to possibly improve performance?), now that I no longer need it?

Thanks! That is very helpful, I was using the wrong variable GV7, instead of GV6 (either snow or snow depth) instead of rain, which is why it was always zero - now I need to figure out why Weatherbit doesn't update sometimes

I've been using Weatherbit with PG2 since the demise of the climate module but it has some issues: Sometimes it does not update and in my case it never seems to indicate any rain. I've been running PG2 exclusively up until today but have just completed updating my 3 free PG2 node servers to PG3 and am starting to investigate migrating the others, so this would be a good time to change, if needed. As a minimum I want a NS that can report the high and low temps for the day, the current temp and the amount of rainfall. What does everyone recommend? Also - I don't seem to recall how I got the high, low and rainfall in my daily home email notification - can someone explain this? (part of my notification is below) Total Rain Today = ${sys.node.n006_forecast_0.GV7} High Temperature = ${sys.node.n006_forecast_0.GV0} Low Temperature = ${sys.node.n006_forecast_0.GV1} (Can't seem to find how to get the above values)

Pushover notifications work well - I switched to this method when I encountered this problem. You don't need a Node Server, just create a free Pushover account and they provide you with an email address to send your notifications to. I just use the default IoP email for sending notifications - they appear in a timely fashion on your phone's pushover app. It's also nice to have your home notifcations separated from other text messages.

I was out of town for a few days and my Polisy went off-line. It has been plugged into one of the front 8 ethernet switch ports of a Ubiquiti Dream Machine Pro for over a year. When I returned, it took some experimentation to discover that the Polisy won't get an IP address if it is plugged directly into the UDM-Pro anymore, but it works fine if I plug it into an external ethernet switch, which then connects to the UDM-Pro. I am unsure if there was a Ubiquiti software update - a 2nd device (Raspberry Pi) also had the same problem. Has anyone else experienced anything like this?

I bought and installed a 2nd Ultraloq on my back door - I tried putting the lock cylinder from my Schlage BE469 into the Ultraloq but it is slightly too large to fit - after some research, I see that the Ultraloq cylinder drawing on their website exactly matches the drawing for a "Prime Line E 2103" lock cylinder at Amazon - not a good quality cylinder but regardless the fingerprint and code access combined with z-wave and other features is definitely nice enough for me to overlook the keying issue for now...

I saw this: https://mapleleaflocksmith.com/ultraloq-rekey-it-to-schlage-sc1/ indicating it can be re-keyed, but if the battery dies, it can be opened by connecting a USB power source via micro-usb, so perhaps there's no need to re-key - I am going to hold off on re-keying for a while

I installed the Ultraloq Pro Z-Wave and it is recognized by the Polisy+Zooz ZST10 - communication is much improved vs the old Schlage BE469 (probably due to it being z-wave plus vs old z-wave 300) - it reports battery % and lock status and can be commanded to lock and unlock via the Polisy - overall it has a lot more features than the Schlage BE469, but I am unsure if I can re-key it to match my other two Schlage's - the fingerprint feature is nice as it makes entry easier for those coming in the front door - will continue to evaluate...

Red light has not gone away and the Schlage lock is also draining batteries really fast - so it will be replaced

I just impulsively bought a Z-Wave Ultraloq (lightning deal on Amazon) - I don't see that anyone in these forums has used or installed one - is there anyone who knows about these? (Looking to get some additional ways to unlock the door besides a key or a code (fingerprint, bluetooth phone proximity auto-unlock?) and to replace a possibly failing Schlage lock