bob123

Thanks @Javi

@Javi - any insight into the issue based on the error message

Here’s a screenshot. It’s a 6th gen ipad on iPadOS 17.72

Thanks. Definitely using the portal to connect. I looked at the wiki- it might be outdated as I can view the api key on both devices (dated 8/11/23 so not recently modified), but not sure what to do next as differences in current UI.

I’ve been using UD Mobile on my iPhone since it was first released. It’s an outstanding interface to my automation. I recently tried to use the installed UDM on my iPad. It all works okay, except the for notifications. When I hit the notifications icon, I get ERROR. The operation couldn’t be completed. No APNS token specified before fetching FCM Token. Tried deleting the app, restoring from a fresh backup of my iPhone install. Any help appreciated.

I was using the free version knowing I would not be close to 8 messages a day. Have not seen a reoccurrence since upgrading.

Thanks. I am on the free version of the notification server, but average about 1 notification a week. This was the first notification I had received in a while. I will purchase the full version, as that’s going to be easier than figuring this out.

Got the following notification in UDM. Reached max daily message count, please upgrde to standard edition. Does anyone know what is generating this notification or what it means? The misspell on ‘upgrade’ is how the notification reads. Thanks

I had this same issue with a yale lock. I removed the lock from the door and placed it very close to my Policy. Then removed and added it back to the zwave network. Solved the issue.

My polisy was on 5.8.0. I ran an upgrade to 5.83 and a reboot. All works fine now. Not sure if it was the upgrade to 5.8.3 or the reboot. Thanks Javi.

Status still does not update on UDM. I have narrowed it down to node server items only. Statuses on Insteon devices update when you control them. Statuses on devices such as ELK and Ecobee do not update when you control them. You have leave the screen and re-enter to update statuses. So, asynchronous update of any node server devices is not working.

Upgraded to 1.1.61. Still have status update issues. Status on favorites does not show until I click into the device page on the icon . Status on the device page (not favorites) does not update until leave and re-enter page.

I am having a similar issue. Logged into UDM. There is no status on my favorites icons - Ecobee no longer shows temperatore on the icon and ELK does not show status. When I lock or unlock a lock either from the favorites or from the device page itself, the lock responds, Admin Console shows lock status, but UDM device status does not update until I leave the screen and go back in. Setting the ELK alarm from UDM, I have no idea if I actually set it as there is no status. Also missing status and temp on icons of the favorites. My UDM is on version 1.1.60.

I have 3 yale zwave deadbolts that have been working flawlessly with my polisy zooz setup. One of the locks failed and I purchased a new model. The older locks are from 2015. The new lock comes with a newer zwave version 2 module. I know that locks are secure devices and a pain with zwave, but it seems to be added fine to the network. The old locks are Yale yrd210 and the new lock is YRD216-ZW2-OBP. ‎ The new lock added to the network okay and I can control it (lock, unlock). But I cannot create programs based on lock actions. For example, unlock the door then turn on a light. This has always worked flawlessly. If I substitute one of the older locks to the program, it works fine. Events are being generated in iox, but no actions are triggered. But, in the admin console, if I manually lock and unlock the lock, the correct status changes (locked, unlocked) on the device viewer. There are some differences in the events between the old locks and new locks. From the event viewer. Old Lock Manually lock Fri 01/19/2024 07:25:33 PM : [ZWAVE-TX-NONCE ] ... Fri 01/19/2024 07:25:33 PM : [ZW008_1 ] ST 100 (uom=11 prec=0) Fri 01/19/2024 07:25:33 PM : [ZW008_1 ] ALARM 4 (uom=15 prec=0) New Lock Manually lock Fri 01/19/2024 07:25:45 PM : [ZWAVE-TX-NONCE ] ... Fri 01/19/2024 07:25:45 PM : [ZW010_1 ] ST 100 (uom=11 prec=0) Fri 01/19/2024 07:25:45 PM : [ZW010_306 ] ALARM 1 (uom=25 prec=0) Fri 01/19/2024 07:25:45 PM : [ZW010_306 ] DON 100 (uom=78 prec=0) Old Lock Manually unlock Fri 01/19/2024 07:25:37 PM : [ZWAVE-TX-NONCE ] ... Fri 01/19/2024 07:25:37 PM : [ZW008_1 ] ST 0 (uom=11 prec=0) Fri 01/19/2024 07:25:37 PM : [ZW008_1 ] ALARM 6 (uom=15 prec=0) New Lock Manually unlock Fri 01/19/2024 07:25:52 PM : [ZWAVE-TX-NONCE ] ... Fri 01/19/2024 07:25:52 PM : [ZW010_1 ] ST 0 (uom=11 prec=0) Fri 01/19/2024 07:25:52 PM : [ZW010_306 ] ALARM 2 (uom=25 prec=0) Fri 01/19/2024 07:25:52 PM : [ZW010_306 ] DON 100 (uom=78 prec=0) I don't know what the various ALARM #'s mean; the iox is seeing the events, but not triggering any actions. I have tried this both with manually using the lock and using the keypad as triggers - neither trigger programs, but they all show events. Any clues, or additional debugging I can try. Thanks

Thanks Paul. Didn't see that icon.