Oakland Jeff Posted November 17, 2021 Share Posted November 17, 2021 I put the open/close sensor into linking mode and do "Write Updates to Device"... it fails. All my wireless devices are like this now. Yea, the batteries have all just been replaced... I wish it were that simple. Here is the Device Communications Events log when I tried to write updates: Wed 11/17/2021 01:53:25 PM : [14 D6 91 1 ] Link 2 : 0FE8 [62011BBF93000001] Writing [62011BBF93000001] Wed 11/17/2021 01:53:25 PM : [INST-TX-I2CS] 02 62 14 D6 91 1F 2F 00 00 02 0F EF 08 62 01 1B BF 93 00 00 01 F8 Wed 11/17/2021 01:53:34 PM : [INST-TX-I2CS] 02 62 14 D6 91 1F 2F 00 00 02 0F EF 08 62 01 1B BF 93 00 00 01 F8 Wed 11/17/2021 01:53:42 PM : [INST-TX-I2CS] 02 62 14 D6 91 1F 2F 00 00 02 0F EF 08 62 01 1B BF 93 00 00 01 F8 Wed 11/17/2021 01:53:46 PM : [14 D6 91 1 ] Link 2 : 0FE8 [62011BBF93000001] *Failed Writing [62011BBF93000001] What's the way forward? Link to comment
MrBill Posted November 17, 2021 Share Posted November 17, 2021 6 minutes ago, Oakland Jeff said: I put the open/close sensor into linking mode and do "Write Updates to Device"... it fails. All my wireless devices are like this now. Yea, the batteries have all just been replaced... I wish it were that simple. Here is the Device Communications Events log when I tried to write updates: Wed 11/17/2021 01:53:25 PM : [14 D6 91 1 ] Link 2 : 0FE8 [62011BBF93000001] Writing [62011BBF93000001] Wed 11/17/2021 01:53:25 PM : [INST-TX-I2CS] 02 62 14 D6 91 1F 2F 00 00 02 0F EF 08 62 01 1B BF 93 00 00 01 F8 Wed 11/17/2021 01:53:34 PM : [INST-TX-I2CS] 02 62 14 D6 91 1F 2F 00 00 02 0F EF 08 62 01 1B BF 93 00 00 01 F8 Wed 11/17/2021 01:53:42 PM : [INST-TX-I2CS] 02 62 14 D6 91 1F 2F 00 00 02 0F EF 08 62 01 1B BF 93 00 00 01 F8 Wed 11/17/2021 01:53:46 PM : [14 D6 91 1 ] Link 2 : 0FE8 [62011BBF93000001] *Failed Writing [62011BBF93000001] What's the way forward? Try putting device in linking mode and right clicking the device and doing "restore device". Link to comment
Teken Posted November 17, 2021 Share Posted November 17, 2021 6 minutes ago, Oakland Jeff said: I put the open/close sensor into linking mode and do "Write Updates to Device"... it fails. All my wireless devices are like this now. Yea, the batteries have all just been replaced... I wish it were that simple. Here is the Device Communications Events log when I tried to write updates: Wed 11/17/2021 01:53:25 PM : [14 D6 91 1 ] Link 2 : 0FE8 [62011BBF93000001] Writing [62011BBF93000001] Wed 11/17/2021 01:53:25 PM : [INST-TX-I2CS] 02 62 14 D6 91 1F 2F 00 00 02 0F EF 08 62 01 1B BF 93 00 00 01 F8 Wed 11/17/2021 01:53:34 PM : [INST-TX-I2CS] 02 62 14 D6 91 1F 2F 00 00 02 0F EF 08 62 01 1B BF 93 00 00 01 F8 Wed 11/17/2021 01:53:42 PM : [INST-TX-I2CS] 02 62 14 D6 91 1F 2F 00 00 02 0F EF 08 62 01 1B BF 93 00 00 01 F8 Wed 11/17/2021 01:53:46 PM : [14 D6 91 1 ] Link 2 : 0FE8 [62011BBF93000001] *Failed Writing [62011BBF93000001] What's the way forward? If you have a Pro version turn off battery writes. It will make all battery operated devices grey in color. Go to one single device and right mouse click and select write updates to device. Link to comment
Oakland Jeff Posted November 17, 2021 Author Share Posted November 17, 2021 Teken, unfortunately I do not have pro. Waiting for Polisy to fully support ISY and be out of Beta and then I'll buy one and be totally up to date with the latest and greatest. MrBill, this is the com log when I try to Restore Device: Hey, why won't the forum let me enter a code formatted section in my response like I did in my original post? Well, here it is, formatted poorly: Wed 11/17/2021 02:39:28 PM : [ 14 BF 3B 1] Preparing Device '~Main Hall - Entry-S' for Restore Wed 11/17/2021 02:39:28 PM : [ 14 BF 3B 1] Device '~Main Hall - Entry-S' ready for Full Restore Wed 11/17/2021 02:39:28 PM : [All ] Writing 99 bytes to devices Wed 11/17/2021 02:39:28 PM : [INST-TX-I2CS] 02 62 14 BE B1 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/17/2021 02:39:28 PM : [INST-ACK ] 02 62 14.BE.B1 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/17/2021 02:39:37 PM : [INST-TX-I2CS] 02 62 14 BE B1 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/17/2021 02:39:46 PM : [INST-TX-I2CS] 02 62 14 BE B1 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/17/2021 02:39:50 PM : [INST-TX-I1 ] 02 62 14 BF 3B 0F 0D 00 Wed 11/17/2021 02:39:59 PM : [INST-TX-I1 ] 02 62 14 BF 3B 0F 0D 00 Wed 11/17/2021 02:40:08 PM : [INST-TX-I1 ] 02 62 14 BF 3B 0F 0D 00 Wed 11/17/2021 02:40:12 PM : [INST-TX-I1 ] 02 62 1C B3 F8 0F 13 00 Wed 11/17/2021 02:40:16 PM : [INST-TX-I2CS] 02 62 14 BF 3B 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9 Wed 11/17/2021 02:40:24 PM : [INST-TX-I2CS] 02 62 14 BF 3B 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9 Wed 11/17/2021 02:40:33 PM : [INST-TX-I2CS] 02 62 14 BF 3B 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9 Wed 11/17/2021 02:40:37 PM : [D2D EVENT ] Event [14 BF 3B 1] [ERR] [1] uom=0 prec=-1 Wed 11/17/2021 02:40:37 PM : [ 14 BF 3B 1] ERR 1 It continues to try to write stuff, but I don't think it's related to the restore. I suspect it's related to all the other queued writes for other devices?... Wed 11/17/2021 02:40:38 PM : [INST-TX-I2CS] 02 62 21 D0 FD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/17/2021 02:40:41 PM : [INST-TX-I1 ] 02 62 1C B3 C6 0F 13 00 Wed 11/17/2021 02:40:50 PM : [INST-TX-I2CS] 02 62 21 D0 FD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/17/2021 02:40:59 PM : [INST-TX-I2CS] 02 62 21 D0 FD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/17/2021 02:41:03 PM : [14 D6 91 1 ] Link 2 : 0FE8 [62011BBF93000001] Writing [62011BBF93000001] Wed 11/17/2021 02:41:03 PM : [INST-TX-I2CS] 02 62 14 D6 91 1F 2F 00 00 02 0F EF 08 62 01 1B BF 93 00 00 01 F8 Wed 11/17/2021 02:41:11 PM : [INST-TX-I1 ] 02 62 30 67 B0 0F 13 00 Wed 11/17/2021 02:41:12 PM : [INST-TX-I2CS] 02 62 14 D6 91 1F 2F 00 00 02 0F EF 08 62 01 1B BF 93 00 00 01 F8 Wed 11/17/2021 02:41:21 PM : [INST-TX-I2CS] 02 62 14 D6 91 1F 2F 00 00 02 0F EF 08 62 01 1B BF 93 00 00 01 F8 Wed 11/17/2021 02:41:25 PM : [14 D6 91 1 ] Link 2 : 0FE8 [62011BBF93000001] *Failed Writing [62011BBF93000001] Wed 11/17/2021 02:41:26 PM : [31 AE CD 1 ] Link 3 : 0FE0 [62011A673A000001] Writing [62..............] Wed 11/17/2021 02:41:26 PM : [INST-TX-I2CS] 02 62 31 AE CD 1F 2F 00 00 02 0F E7 08 62 01 1A 67 3A 00 00 01 B2 Wed 11/17/2021 02:41:34 PM : [INST-TX-I2CS] 02 62 31 AE CD 1F 2F 00 00 02 0F E7 08 62 01 1A 67 3A 00 00 01 B2 Wed 11/17/2021 02:41:41 PM : [INST-TX-I1 ] 02 62 1A 69 5A 0F 13 00 Wed 11/17/2021 02:41:43 PM : [INST-TX-I2CS] 02 62 31 AE CD 1F 2F 00 00 02 0F E7 08 62 01 1A 67 3A 00 00 01 B2 Wed 11/17/2021 02:41:47 PM : [31 AE CD 1 ] Link 3 : 0FE0 [62011A673A000001] *Failed Writing [62..............] Wed 11/17/2021 02:41:48 PM : [31 B6 54 1 ] Link 3 : 0FE0 [E2011A66E1000001] Writing [E2011A66E1000001] Wed 11/17/2021 02:41:48 PM : [INST-TX-I2CS] 02 62 31 B6 54 1F 2F 00 00 02 0F E7 08 E2 01 1A 66 E1 00 00 01 8C Wed 11/17/2021 02:41:57 PM : [INST-TX-I2CS] 02 62 31 B6 54 1F 2F 00 00 02 0F E7 08 E2 01 1A 66 E1 00 00 01 8C <Truncated because it went on and on> Link to comment
MrBill Posted November 18, 2021 Share Posted November 18, 2021 code the code button seems to be working,... maybe a browser cache issue? That looks like it's cycling thru multiple devices, which is where Teken was going with his suggestion. just to be clear, "pro" is a feature level, it adds to the number of nodes and programs allowed and gives you these two buttons on the admin console ribbon The one on the right, shown in the off or deselected state is what teken is talking about. Do you have those two buttons? Link to comment
Oakland Jeff Posted November 18, 2021 Author Share Posted November 18, 2021 Yes, I cleared browser cache and it's back. Oh, I thought Pro was a hardware thing, given that it supports more nodes and programs (i.e. eats up more memory). Well in any case I don't have those buttons Link to comment
MrBill Posted November 18, 2021 Share Posted November 18, 2021 10 minutes ago, Oakland Jeff said: Yes, I cleared browser cache and it's back. Oh, I thought Pro was a hardware thing, given that it supports more nodes and programs (i.e. eats up more memory). Well in any case I don't have those buttons I hate to recommend doing it because if it doesn't solve the problem for you.... but it is a soft instant upgrade... Help > Purchase Modules. Link to comment
Oakland Jeff Posted November 18, 2021 Author Share Posted November 18, 2021 When I select Help > Purchase Modules... this is what I get. Even when I go to the Store menu there are no software modules to be found. Link to comment
MrBill Posted November 18, 2021 Share Posted November 18, 2021 I don’t have my laptop but I think you want “my products” Link to comment
Oakland Jeff Posted November 18, 2021 Author Share Posted November 18, 2021 OK, I found it. Thanks! Turns out I had 3 ISY's listed under my products and the one I'm currently using didn't have a valid serial number so clicking on modules showed nothing but an error message. Link to comment
Oakland Jeff Posted November 18, 2021 Author Share Posted November 18, 2021 MrBill, thank your for all your help! Best $30 bucks I spent all year. With Pro now, I turned off the wireless writes and auto writes and did my Restore Modem (PLM) which went smoothly. With 71 total devices in my house (many keypads and sensors that have sub-nodes) the PLM now has 280 links in it's table, which seems about right. Link to comment
MrBill Posted November 18, 2021 Share Posted November 18, 2021 In the future watch for changes that require wireless writes and make sure to stay on top of them. Not sure what firmware version you're on, but there was a long time bug that was fixed around 5.2 (it existed for most revisions of 5). The bug was linked to wireless devices that were scene controllers and programs that used "Adjust scene" which would generate the need for wireless writes. Not sure what firmware version you're on but it should be 5.3.4 unless you have a 300 series z-wave board in which case the last firmware that works with the 300 series z-wave is 5.0.16C Link to comment
Oakland Jeff Posted November 18, 2021 Author Share Posted November 18, 2021 OK, well, after that detour, I'm still back to my original problem... here is the level 3 com log when I tried to update a motion sensor that needed writes (as indicated by the gray 1011 icon)... Thu 11/18/2021 10:13:56 AM : [INST-TX-I1 ] 02 62 14 BF 3B 0F 0D 00 Thu 11/18/2021 10:13:56 AM : [INST-ACK ] 02 62 14.BF.3B 0F 0D 00 06 (00) Thu 11/18/2021 10:14:05 AM : [INST-TX-I1 ] 02 62 14 BF 3B 0F 0D 00 Thu 11/18/2021 10:14:14 AM : [INST-TX-I1 ] 02 62 14 BF 3B 0F 0D 00 Thu 11/18/2021 10:14:18 AM : [INST-TX-I2CS] 02 62 14 BF 3B 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9 Thu 11/18/2021 10:14:27 AM : [INST-TX-I2CS] 02 62 14 BF 3B 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9 Thu 11/18/2021 10:14:30 AM : [INST-SRX ] 02 50 14.BF.3B 00.00.01 CF 13 01 LTOFFRR(01) Thu 11/18/2021 10:14:30 AM : [Std-Group ] 14.BF.3B-->Group=1, Max Hops=3, Hops Left=3 Thu 11/18/2021 10:14:30 AM : [D2D EVENT ] Event [14 BF 3B 1] [DOF] [1] uom=0 prec=-1 Thu 11/18/2021 10:14:30 AM : [ 14 BF 3B 1] DOF 1 Thu 11/18/2021 10:14:30 AM : [D2D EVENT ] Event [14 BF 3B 1] [ST] [0] uom=100 prec=0 Thu 11/18/2021 10:14:30 AM : [ 14 BF 3B 1] ST 0 (uom=100 prec=0) Thu 11/18/2021 10:14:30 AM : [INST-SRX ] 02 50 14.BF.3B 00.00.01 CF 13 01 LTOFFRR(01) Thu 11/18/2021 10:14:30 AM : [Std-Group ] 14.BF.3B-->Group=1, Max Hops=3, Hops Left=3 Thu 11/18/2021 10:14:30 AM : [INST-DUP ] Previous message ignored. Thu 11/18/2021 10:14:31 AM : [INST-SRX ] 02 50 14.BF.3B 44.CD.0D 2F 0D 02 (02) Thu 11/18/2021 10:14:31 AM : [Std-Direct Ack] 14.BF.3B-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Thu 11/18/2021 10:14:40 AM : [INST-TX-I2CS] 02 62 14 BF 3B 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9 Thu 11/18/2021 10:14:40 AM : [INST-ACK ] 02 62 14.BF.3B 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9 06 (00) Thu 11/18/2021 10:14:44 AM : [D2D EVENT ] Event [14 BF 3B 1] [ERR] [1] uom=0 prec=-1 Thu 11/18/2021 10:14:44 AM : [ 14 BF 3B 1] ERR 1 After this completes, I get an error message that pops up that says the ISY can't communicate with the Motion Sensor and the icon is now a red "!" instead of the needs-write "1011". After a few minutes, the red "!" reverts to the gray needs-write "1011". Link to comment
Oakland Jeff Posted November 18, 2021 Author Share Posted November 18, 2021 Also, what's the difference between the grey "1011" and the green "1011" icons? FWIW, I am using "adjust scene" in my programs to: Lower the on level of motion triggered scenes at night to something less blinding Set many lights in motion activated scenes to "Ignore" during the day so they don't come on at all when it's light out I started to use this methodology after it was reported that the bug you mentioned was fixed. I'm currently on v.5.3.3. Link to comment
MrBill Posted November 18, 2021 Share Posted November 18, 2021 2 hours ago, Oakland Jeff said: here is the level 3 com log when I tried to update a motion sensor that needed writes (as indicated by the gray 1011 icon)... We need someone that's better than me at reading level 3 logs... there are many members that might but i'll tag @kclenden in case he's around.... He's an amazing link wizard. 1 hour ago, Oakland Jeff said: Also, what's the difference between the grey "1011" and the green "1011" icons? That new button you got... When you press it and turn it to grey the 1011 icons will turn grey, and they are inactive or deselected. When they are green the ISY will be trying to write them constantly, which slows down communications because each has to error out 3 (?) times. So keep them grey and see if you can put one device at a time into linking mode, then right click the device and write updates. 11 hours ago, Oakland Jeff said: Restore Modem (PLM) which went smoothly. I was surprised when you said this. Did you confuse Restore Device with Restore PLM? Really "Write updates to device" is all you should need but I did also suggest trying "Restore Device". Link to comment
Oakland Jeff Posted November 18, 2021 Author Share Posted November 18, 2021 AH, OK, thanks MrBill, that makes perfect sense about the grey buttons being on hold from my new Pro button. Oh, and regarding restoring the PLM, no confusion. This was the thing that I needed to do from the beginning, since a brown out pretty much seemed to erase most everything on it and none of my programs were getting triggered or taking effect (e.g. turn off the lights 20 minutes after someone hits the paddle to turn them on; turn on my accent lights at dusk; etc.) The good news is that everything seems to be working fine now, despite all the grey "write needed" buttons. And those concern me because it just seems like something is broken and those effects will surface later. Link to comment
MrBill Posted November 18, 2021 Share Posted November 18, 2021 19 minutes ago, Oakland Jeff said: grey "write needed" buttons. And those concern me because it just seems like something is broken and those effects will surface later. Correct. Try to get rid of them one device at a time. With wireless writes disabled, put one device in linking mode, then right click the device name and Write Updates to Device. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.