Battery Status not changing

Posted on
Sun Oct 15, 2017 9:55 am
InsteonDiego offline
Posts: 48
Joined: Dec 07, 2016

Re: Battery Status not changing

Thanks Matt! Log snippet follows. Let me know if you need anything else.

Z-Wave Debug RCVD nodeInfoFrame: 01 0B 00 49 84 14 05 04 07 01 5E 98 EC
Z-Wave Debug RCVD nonceFetch: node 020
Z-Wave Debug SENT nonceReport: 01 11 00 13 14 0A 98 80 C5 24 71 E7 15 A3 D6 43 25 F1 7B
Z-Wave Debug RCVD encryptedPacket: 00 84 07 (decrypted)
Z-Wave Debug RCVD nodeAwake: 01 08 00 04 00 14 02 84 07 FF
Z-Wave Debug . . nodeAwake: node 020
Z-Wave Debug SENT nonceRequest: 01 09 00 13 14 02 98 40 25 F2 FC
Z-Wave Debug RCVD nonceReport: node 020, nonce 6D 14 92 0D D0 9C D9 C5
Z-Wave Debug SENT requestBatteryLevel: 80 02 (encrypted)
Z-Wave Debug RCVD nonceReport: node 020, nonce 6A 55 D8 4D E9 FF 69 47 (saving)
Z-Wave Debug . . nodeAwake: inhibit count++ to 1
Z-Wave Debug . . nodeAwake: started inhibit sleep timer

Posted on
Sun Oct 15, 2017 10:29 am
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Battery Status not changing

That shows Indigo sending a request (polling) for the battery status but the module never replies. Well, it replies with a new encryption nonce value, but it doesn't actually send the battery level reply. It sounds like the modules might have a firmware bug that only occurs after the battery is replaced. You mentioned this only happens with modules that have encryption enabled. Those same modules were working correctly before the battery change but were they also in encrypted mode at that time?

You could try factory resetting the module. For most modules that just means excluding it from the Z-Stick, then re-including (and resyncing) it. I wonder if that will get it back into the previous state where it worked correctly.

Image

Posted on
Sun Oct 15, 2017 10:39 am
InsteonDiego offline
Posts: 48
Joined: Dec 07, 2016

Re: Battery Status not changing

Interesting. Yes, correct this only happens with the modules that are setup as encrypted. I never tested these specific modules unencrypted, rather I'm comparing to the initial modules I implemented without encryption. As the issue occurs with every single module with encryption turned on, I suspect you are right and there is in fact a firmware bug. With these type of modules, is it safe to assume that firmware updates are not possible (I have no way to physically connect to the device)?

Your assessment is correct, resyncing the module did get the battery to update, however it is a real pain to do every time I change batteries.

At the end of the day, I don't really need encryption for these modules. Is there a way to convert the modules from encrypted to unencrypted WITHOUT losing the data I have collected for them in the SQL database?

Thanks again,

Posted on
Sun Oct 15, 2017 10:44 am
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Battery Status not changing

I don't know about these particular modules, but a few modules have over-the-air (via Z-Wave) firmware updates. It normally is a cumbersome process, especially for us Mac users since the upgrade software tends to be Windows only.

You can just exclude, re-include (without encryption) then resync the module. As long as you keep the same Indigo device and just have it resync against the new node ID (if it changes), all of your database history should remain.

Image

Posted on
Tue Oct 17, 2017 11:02 am
InsteonDiego offline
Posts: 48
Joined: Dec 07, 2016

Re: Battery Status not changing

Thanks again Matt. Excluding and resyncing worked exactly as you suggested and all data was preserved.

Adam

Who is online

Users browsing this forum: No registered users and 1 guest

cron