Everything posted by bob123
-
Max daily message count
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
-
Baldwin (Kwikset) Z-wave lock just shows as "Entry Control"
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.
-
OAuth error showing devices
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.
-
OAuth error showing devices
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.
-
OAuth error showing devices
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.
-
UD Mobile Favorites not updating
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.
-
Issue with new Yale Zwave lock
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
-
Notifications for Dummies
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?
-
Trying to migrate to Polisy - stuck on zwave
Looks like it succeeded in the file removal- unless the password you entered was incorrect and it did not give an error message.
-
Trying to migrate to Polisy - stuck on zwave
I know you tried this already but you might want to try the steps I received from support (prior post) again. It re-enables the support of non-zmatter zwave after a migration
-
Trying to migrate to Polisy - stuck on zwave
Sorry you are still having issues. Did you check that your zooz stick is seated well in the hub? I had to use a right angle usb adaptor to have it properly connect. Also try the other usb slot.
-
Initial value of state variable on UD Mobile startup
Perfect- much appreciated
-
Initial value of state variable on UD Mobile startup
First- I think UD Mobile is great. I’m getting used to configuring some creative favorites and hit an issue. Under favorites, I created a type folder with display mode being a state variable. In the folder, I put 2 programs nodes that set the variable to different values. The folder has configurations to change its color and icon based on variable value. This all works great. The issue is with starting up UDM. When I first go into favorites, all my other nodes have correct status and values ( locks, alarm…). The variable folder is blank with no value showing for the variable until I modify the variable either with the programs, with UDM or on the admin console. Is there a way to get the value of the variable to be queried on UDM startup?
-
ISY994 ELK program migration to EISY
I recently migrated from isy with ELK to polisy and ELK node server. Was pretty painless. I had copied out my programs to notepad prior to starting. After I had restored to the polisy, I installed the ElK nodeserver. Each program that referenced an ELK item has those references commented out; I just updated the program with the appropriate device/ item from the ELK nodeserver. I used the notepad program text as an aid when I wasn’t sure what the placeholder was. It has been working well for a few weeks now.
-
Reverse Zmatter migration
Great news (except for the zwave rebuild). I did the full rebuild which was pretty straightforward. I had only door locks and repeaters- had to exclude each one and then include. Had to uninstall the door locks to bring them close to the zooz stick so that process would work. I then had to edit each program fixing the zwave device name - some were commented out and some were incorrect. pretty painless except removing the physical locks from the doors.
-
Reverse Zmatter migration
See my thread from a few weeks ago. My issue was very similar - I was going from isy to polisy. The last response in the thread is the solution I used that worked perfectly. Not sure if eisy supports the zooz stick or only zmatter, but worth a shot. Polisy supports both.
-
Trying to migrate to Polisy - stuck on zwave
Here is the solution from the great support staff (Chris) - it worked great. Basically resets the configuration/system tab on the admin manager and restores ability to have a zooz 700 zwave stick instead of a zmatter. One additional step I found was to re-enable insteon and zwave on the configuration/system tab. Do not do migrate to zmatter. 1) ssh to Polisy 2) run command: sudo rm /var/isy/FILES/CONF/0.UCF 3) close ssh (unless you want to keep it open for something) 4) Restart IoX 5) Go to Configuration Tab in Admin Console, you should see a button "Migrate to ZMatter Z-Wave", this indicates that you are now currently using original Z-Wave. (Don't press the button obviously) 6) Update the values in the Configuration Tab to what they were before 7) Under the Z-Wave top level menu you should see all the options (like add, remove, etc.)
-
Trying to migrate to Polisy - stuck on zwave
I received a response from support. When migrating a backup from ISY-994 to eisy or Polisy, it automatically sets it to use ZMatter Z-Wave. So, any restore of an isy backup to polisy will configure it to zmatter only. They will be sending me instructions how to configure the Polisy use the original Z-Wave implementation (using the Zooz dongle). Thanks everyone for the assistance.
-
Trying to migrate to Polisy - stuck on zwave
I did not do a separate zwave backup on the isy. I just did a normal full backup. How would doing the zwave backup have affected the restore to the polisy? If the older 300 series zwave file was 'restored' to the polisy, how do I rebuild the polisy zwave from scratch. The polisy does not even recognize the device. Unfortunately, I did not backup the polisy when it was running correctly with zwave dongle, so can't restore that way. Is there a way to reset iox/zwave on the polisy to initialized state? If I were to do that, how would I prevent the 300 series zwave from my isy from restoring again? Thanks
-
Trying to migrate to Polisy - stuck on zwave
Thanks landolfi - I tried the suggestions in the link to override the usb port for the zwave stick. Unfortunately did not help.
-
Trying to migrate to Polisy - stuck on zwave
Tried unplugging all the zwave devices in the network - was only 2 plug in aeotec doorbell/range extenders and a lock. Rebooted. No change. The polisy still says zmatter zwave not responding. I tried the usb extender to ensure the zooz stick was firmly plugged in. No help either. I've submitted a support ticket. Very frustrating since I went through all the effort to ensure that zwave with the zooz stick worked properly on the polisy prior to moving my insteon to it from the 994. Now I have a non-functioning isy994 because I upgraded to 5.3.4 which does not support my 300 series zwave and a polisy that I can't use.
-
Trying to migrate to Polisy - stuck on zwave
Thanks- will unplug my zwave devices and reboot. Strange part is it was working great prior to the restore from backup. I also ordered up a usb plug extender. Found some posts that plugging in the plm usb could possibly cause interference to the zwave stick usb connection as it’s a tight fit.
-
Trying to migrate to Polisy - stuck on zwave
Yes. It was still checked after I restored the backup from the isy. I then unchecked it, saved and rebooted, then checked it, saved and rebooted. Still not working. I then tried removing the PLM and rebooted- still no help.
-
Trying to migrate to Polisy - stuck on zwave
I decided to finally take the plunge and upgrade my isy to my polisy. I got the polisy up and running prior to the upgrade. All running great. Also had some PG3 node servers running great. My isy was on 300 series zwave. I upgraded it to 5.0.16 and all went well. I then installed a zooz 700 stick on the polisy, unrolled some of my zwave devices from the isy and enrolled them on the polisy. Worked great. Next step was to upgrade the isy to 5.3.4 so that I could back it up and restore my insteon stuff to the polisy. I knew that zwave would not migrate (series 300) and that I would manually have to rework it on them on the polisy. Did not do the 'migrate zwave' backup - just normal backup. Restored the fresh backup from the isy to the polisy. Problem - the zwave does not work anymore on the polisy. Clicking the zwave menu says - zmatter zwave not responding. I am completely stuck. Why would the polisy support the zooz stick perfectly prior to restoring the backup from the isy? Now is seems like it does not recognize the device and is looking for the zmatter board. I have checked and unchecked the zwave support under configuration and rebooted several times. Any help is appreciated.
-
Using network module to set variables between isy and polisy
The timeout was not the issue. It was my own late night testing. I started from scratch with new entries and it worked. I had a typo in the actual isy test command. Entered /rest/get/vars/1/1. It should be /rest/vars/get/1/1. I tested different timeouts from 800-3000 and all worked. thanks everyone for the assistance