Jump to content
C4 Forums | Control4

APD120 continuously trying to update it's firmware


Recommended Posts

I have an adaptive phase dimmer that was just installed a few weeks ago.  After having these installed I generally look through to see that they've all dne their due diligence of receiving the firmware colonoscopy.  Well I must have missed one as this poor thing is on 03.19.25 and the zserver is insisting on an upgrade to 3.21.06.  I sat and watched this process for at least an hour today (gives new meaning to watching paint dry).  Here's what it does (complete with log snippets):

 

NOTICE ZSVR: Found out-of-date firmware on 0x000fff000071e720 - device on 03.19.25 should be on 03.21.06

...

NOTICE ZSVR: Node LID: 0x000fff000071e720 SID: 0xf0d1 update status set too: ZNODE_UPDATING

...

DEBUG ZSVR: [Reflash 000fff000071e720] Reading attributes to check device can be updated

...

INFO [19790]: ZBPRO: Received zigbee MIB packet: 0r29b4 n01, source: 000fff000071e720

ERR [19790]: In HandleMessageFailed, this packet failed:'' - raw '0r29b4 n01', destination: 000fff000071e720

ERR [19790]: Device Adaptive Phase Dimmer(1127):The MIB packet: c4.dmx.key  failed!

...

DEBUG ZSVR: [Reflash 000fff000071e720] Read attributes: profile = 6,  fwv = 03.19.25,  product = c4:control4_light:C4-APD120

..

DEBUG ZSVR: [Reflash 000fff000071e720] Reading eeprom validation type

INFO [19790]: LID 000fff000071e720 Profile 104 Cluster 4 Src 1 Dest 1 Group 1

...

DEBUG ZSVR: [Reflash 000fff000071e720] Invalid response to eeprom write response command

...

DEBUG ZSVR: [Reflash 000fff000071e720] Valid response to eeprom write response command

 

Then it sends the bootloader over and begins the  update process....The dimmer supposedly updates and it reports success, but it's still on the old firmware.  I found that this has been an ongoing game for weeks now with this thing so I finally pulled it out of the project to save the poor zigbee mesh some headache.

 

I've tried all the various reset patters, i've left the mesh, joined the mesh - and it does work fine other than not taking the new firmware.   Hell I even cut power for a few minutes to see if that would help.

 

Any ideas?

Link to comment
Share on other sites


  • 2 weeks later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.