DennisC

No worries, but there looks like there is still an issue. While the shades no work, it is throwing an error. 2023-06-19 13:14:22,003 MQTT udi_interface.interface INFO interface:_message: Successfully set c702e129edd7 :: GV0 to 50 UOM 51 2023-06-19 13:14:22,003 MQTT udi_interface.interface INFO interface:_message: Successfully set c702e129edd7 :: GV0 to 50 UOM 51 2023-06-19 13:14:25,542 Thread-57 udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:25,542 Thread-57 udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:30,552 Thread-59 udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:30,552 Thread-59 udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:35,580 Thread-61 udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:35,580 Thread-61 udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:40,227 Command udi_interface INFO ryse:speed: set shade speed {'address': 'c702e129edd7', 'cmd': 'SET_SPEED', 'value': '85', 'uom': '51', 'query': {}} 2023-06-19 13:14:40,227 Command udi_interface INFO ryse:speed: set shade speed {'address': 'c702e129edd7', 'cmd': 'SET_SPEED', 'value': '85', 'uom': '51', 'query': {}} 2023-06-19 13:14:40,327 Command udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:40,327 Command udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:40,330 Command udi_interface INFO ryse:position: set shade position {'address': 'c702e129edd7', 'cmd': 'SET_POSITION', 'value': '0', 'uom': '51', 'query': {}}% 2023-06-19 13:14:40,330 Command udi_interface INFO ryse:position: set shade position {'address': 'c702e129edd7', 'cmd': 'SET_POSITION', 'value': '0', 'uom': '51', 'query': {}}% 2023-06-19 13:14:40,433 Command udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:40,433 Command udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:40,440 MQTT udi_interface.interface INFO interface:_message: Successfully set c702e129edd7 :: GV0 to 0 UOM 51 2023-06-19 13:14:40,440 MQTT udi_interface.interface INFO interface:_message: Successfully set c702e129edd7 :: GV0 to 0 UOM 51 2023-06-19 13:14:40,582 Thread-63 udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:40,582 Thread-63 udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:45,584 Thread-65 udi_interface ERROR ryse:query: query failed: 'speed' 2023-06-19 13:14:45,584 Thread-65 udi_interface ERROR ryse:query: query failed: 'speed'

To find your IP address look in your Eero app under DHCP & NAT section of Advanced settings. I posted the full DHCP instructions below. I am wondering if the subnet changed between your old router and the new. Do the IP addresses start with the same numbers? The eero mesh network offers a range of advanced features accessible through the eero app. These features include: Static IP Address Custom DNS DHCP and NAT Configuration IP reservations and Port Forwarding Band (Client) Steering. DNS: Your DNS translates an address like www.eero.com to an IP address that your phone or computer can understand. Your ISP typically provides an automatic DNS server that resolves web addresses. However, if you’d like to set Custom DNS, you can do so from the eero App. Tap the Settings tab, then select Advanced. Select DNS, then tap the Custom DNS bubble to enter your desired DNS server. DHCP & NAT: Under the DHCP & NAT section of Advanced settings, you can configure the way your eero network assigns IP addresses to the connected devices in your home. If you choose Automatic, we will automatically choose the best settings for your network. If you have a particularly complex home network, you can set custom IP address settings for your eero network. You’ll need to tap Manual, then choose your IP address prefix and specify the lease range manually. Finally, you can choose to put your eero mesh network in Bridge mode. If you choose to put your eero network in bridge mode, it will still provide WiFi access but you’ll need another router to provide network services. Reservations & Port Forwarding: Under this Advanced setting, you can assign IP reservations and port forwarding rules for devices on your eero network. Port forwarding allows you to manually open an Internet port for a single client, to let traffic pass directly through to that machine. For example, if you wanted to run a FTP server on your laptop with IP address of X.X.X.X, you might create a port-forward on port 21 that directs TCP traffic to that IP address through your eero. Check out our detailed directions here on how to set up port forwarding. UPnP: Universal Plug and Play (UPnP) allows devices like game consoles and media centers to open direct connections to other devices on the Internet. We enable this feature by default. If you’d like to turn it off, toggle the slider so it’s no longer green. Band Steering: Many devices are dual-band capable, meaning they support both 2.4 GHz and 5 GHz. 5 GHz is typically less crowded and offers higher performance. Band steering tracks whether a device has previously been seen on both 2.4 GHz and 5 GHz, and if so attempts to “steer” it to 5 GHz to improve long-term device performance. Band steering does not guarantee that a device will choose the 5 GHz band, but helps to favor that preference. eero DDNS: eero DDNS, available to eero Plus customers, gives you the ability to remotely access your network easily regardless of if your dynamic IP changes. With the new DDNS feature in eero Plus, users receive a unique hostname for their network that is simple to recognize and recall.

Is your ISY connected via WIFI or ethernet?

I updated the node server this morning and then updated my programs for the new format. Now, none of the programs will run, including a new one I created just to test. I am seeing the following in the log: KeyError: 'POSITION.uom51' 2023-06-19 10:52:13,600 Command udi_interface.interface ERROR interface:_handleInput: _parseInput: failed c702e129edd7.runCmd(SET_POSITION) 'POSITION.uom51' Traceback (most recent call last): File "/var/polyglot/pg3/ns/000db952c01c_7/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 889, in _handleInput self.nodes_internal[item['address']].runCmd(item) File "/var/polyglot/pg3/ns/000db952c01c_7/.local/lib/python3.9/site-packages/udi_interface/node.py", line 166, in runCmd fun(self, command) File "/var/polyglot/pg3/ns/000db952c01c_7/ryse.py", line 69, in position new_position = cmd['query']['POSITION.uom51'] KeyError: 'POSITION.uom51'

I wonder if the restore PLM did not successfully complete. Try looking in the event log and the error log to see if there were any issues with the restore PLM operation.

That would be great, thanks.

Hi @bpwwer, 1. Would it be possible to extend the number of characters the node server will accept for the shade name? Since I have bridges at two locations, my naming convention includes the location + the room the shade is located in. Currently, I have a shade name that is being abbreviated. I am shy 3 characters. 2. I created a program that sets the shade speed and the position of the shade. Currently, in order to do this, you need to list 2 "Set Shade" commands, one for speed and one for position. When you copy the program, it looks like this: DR Shade Closed - [ID 0055][Parent 0050] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'Noyac Dining Room Sh' Set Shade Set 'Noyac Dining Room Sh' Set Shade Else - No Actions - (To add one, press 'Action') First set shade sets speed to 85%. Second set shade sets position to 100%. With the current configuration there is no way to see what the set shade command is doing. Is there any way to enhance this so the full command is shown?

Glad you have everything covered. As @MrBillstated above, with the unpredictable nature of folder conditions, you need to be prepared for unforeseen circumstances. I also use Schlage ZWave locks and have since ZWave was added to ISY. I have seen an occasional status failure. but not since updating to ZMatter dongle.

What happens if the door unlocking/locking status fails to update correctly?

Just be aware that folder conditions can be unreliable at certain times. For a rental location, they might not be the best choice. I have stopped using them all together.

I would suggest setting the logging to debug, stop and restart node server. The log should give details as to what is happening. If it still shows not connected, then you might not have the configuration set up correctly.

Looks to me like the trigger to run the program is the garage door closing. I don't see a trigger for running then if the garage door is already closed. What criteria do you want to lock the door, if the door is closed and not locked? Do you want a wait period before turning the light off and locking the door? Is it possible you need the light on in the garage for awhile, possibly while working in the garage? Maybe use another program or consider using a variable as a trigger?

I realize the pdf was what you were asking about. I supplied the migration link in case you needed it. Instructions were provided on the board when the ZMatter dongle came out. I also seem to remember receiving instructions in the bag when I purchased the dongle.

@bpwwer I just updated eisy to 5.6.2. As part of that upgrade, PG3x updated to v 3.1.28. I couldn't find a release notice or a support thread, so I am posting here. When I entered the IP address for Polyglot, the login screen for the portal didn't appear. Instead, I had the login page for Polyglot, which I logged in to. PG3x opened normally, with everything in place, however, after a short delay, I received the log in box for the portal. I logged in, and all seemed fine, but after a shorter delay than before, the portal login box appeared a second time. After logging in to the portal again, all appears fine. Just wanted you to know about it.

I have attached the instructions for installing the USB ZMatter dongle. Here is the link for migration instructions: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration Read through the instructions, it contains information for ISY994 & Polisy migration and for eisy. Let us know if you have any other questions. ZMatter-Assembly- Instructions.pdf

I installed a few Ryse SmartShade controllers a couple of weeks ago, along with Bob's node server. As expected, the node server has performed flawlessly. I have also had the opportunity to communicate with them to get some pre-purchase questions answered. They were very helpful and responsive. Currently, Ryse is offering a 10% discount until June 18th. The discount code is available on their website. Disclaimer: I am not profiting from this, just passing along the discount information.

Have you changed the eisy login credentials? It looks like the plug-in is using admin.

I wasn't necessarily commenting about Indigo. I was only commenting on the above statement. While I agree, the OP might have been talking about a PLM linked to Indigo, I thought it was also possible he was speaking about a previous PLM from his ISY, that wasn't completely clear to me. So I based my comment only on the above statement.

While that is true, I think you might be missing the underlining concern, you shouldn't have to repeatedly exclude/include a Zwave device with an Universal Devices infrastructure. Exclude/Include is the recommended method for 1st time installation of a ZWave device. Once included, I have never had to repeat the procedure for a ZWave device. If you find the need to repeatedly exclude/include a device, there is something else going on and should be investigate to determine how and why this is required.

Did you follow the Configuration instructions completely? Once the iAquaLink Service node appears in the ISY Adminstative Console and the iAquaLink Service shows as connected, click "Discover Devices" in the iAquaLink Service node to load nodes for the systems (pool controllers), devices, and OneTouch macros configured in your account.

For the PLM, you would need to do a restore modem. Here is what UD says about ZWave: Z-Wave Our Original Z-Wave implementation is the certified version of Z-Wave on the ISY-994. This code was ported to Eisy / Polisy, but is being deprecated in favor of our new more functional implementation called ZMatter Z-Wave. The original implementation on Eisy / Polisy can use generic Z-Wave controllers such as the Zooz stick, or, it can use the ZMatter Z-Wave controller (either board or USB dongle). The ZMatter Z-Wave implementation can only use the ZMatter Z-Wave controller (either board or USB dongle). However, without a proper backup (possibly a migration backup) this will not restore any programs you might require.

The only time you might have a program issue is if the ZWave address changes.

Let's start from the beginning, since some of the procedure you spelled out doesn't agree with instructions. You will want to follow the directions below exactly as written. https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration Since you are already having issues, I suggest powering down, removing power, than restarting both units. Looks like your ISY994 firmware is current, so make a complete backup. Your Polisy needs to be updated, so go to Configuration tab and select upgrade. Note, this is the current way to upgrade now. If you have trouble upgrading Polisy and since you indicated you have a very early unit, you might require UD assistance for the Polisy upgrade, but try the process first. If Polisy upgrades, complete a backup and then follow the instructions I posted the link for. You will need to follow the migration instructions, not just moving things over and expecting everything to work. If you run in to trouble, post exactly what you did, any errors, and your exact issue.

Suggest opening a support ticket as I don't recall seeing that error code before. Think you will need UD's input.

Are you running the latest firmware, v5.6.2? If not, try upgrading.