bob123

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.

I decided that if the PLM was over 8 years old and could possibly be heading for failure, it was a better move to use the new backup PLM I had. The restore took a few hours between the battery devices and a few stubborn devices that refused to communicate. I did notice few things - there is no option to exclude battery devices during the plm restore. This leads to endless loops of rewrites and retries and failures as it cannot contact them. - The system continuously tries to write to every unrestored battery device when you do any device related action from console. - it Is best to gather all the leak detectors, set them all to blink and then do a restore on any one of them which will sequence through all of them at once. But all is good - thanks all for the assistance.

Thanks for the quick responses. I did the diagnostics on several devices. - On several wall switches I samples, the link tables had a single line of differences in the link tables. I ran a device restore and they then worked properly giving status feedback to the polisy. - On several other wall switches, the link tables were identical, but did not feed status to the polisy. I ran the device restore and they worked properly. - On the battery powered leak sensors, the leak tables were identical ( i did notice there where no A2 entries). I ran a device restore, and they worked properly. So basically, no devices will feed back status without a restore. Is not dependent on link tables being identical. To run device restore on all my devices sounds one at a time sounds very painful (> 100 devices). Is there a way to do all devices at once? What could cause this to happen all of a sudden? The polisy upgrade 2 days ago I think only updated a few PG3 packages and possibly PGx. Is it worth just running a PLM restore? My PLM is 8.5 years old but has been rock solid. I have a new one in a box that could just restore to and then try it - is there any risk in that. Thanks

Two days ago, I noticed my Insteon leak detectors (20 of them) were not reporting heartbeats. I had just updated and rebooted the polisy so thought it was just a startup thing. Today I realized that they were not communicating at all - button pushes blinked the green light, but no communication back (no events on the event console). I investigated further and all of my Insteon hardwired devices also had only one-way communication- from the polisy to the device, nothing from devices to the polisy. I can control devices perfectly from the console, but turning a dimmer on or off does not send any events to the event log. So no status updates. Insteon scenes between devices still works fine, and programs controlling devices are fine for the most part, which was why I didn’t notice it on hardwired devices. power cycling the PLM did not help. Is this the sign of PLM failure? Any help is greatly appreciated.

This is a great, easy to follow guide. Thanks for putting it together. I have basic notifications working, but I can’t get the default notification message template to appear on my customization tab (page 6 of pdf). If I hit ‘add’ I get a blank row that is Name.28. Anything I missed?

Looks like it succeeded in the file removal- unless the password you entered was incorrect and it did not give an error message.