Firmware update


#1

Hi,

I’m trying to do a firmware update but without success. There seems to be newer firmware available:

Type String │ Firmware HM-TC-IT-WM-W-EU │ *1.1 HM-CC-RT-DN │ *1.3 *: Firmware update available.

But whenever I do pud 1, or pud 1 true and manually put the device in FUP mode, at the end it is still the same firmware version.

Am I doing something wrong? The newer firmware is in /var/lib/homegear/fimware/


#2

Hey,

you are using the COC to communicate with your HomeMatic devices, right? Make sure, you have a current version of CULFW installed. With old versions it’s not working. If it’s still not working then, please send me a log excerpt of the update process.

Cheers,

Sathya


#3

Yes it’s a COC. The culfw is v1.61 which I believe is the latest.

This is the log when trying to update:

[quote]11/26/14 20:25:22.496 Info: CLI connection accepted. Client number: 8
11/26/14 20:25:22.502 Listening for incoming commands from client number 8.
11/26/14 20:25:39.553 Module HomeMatic BidCoS: Debug: Size of firmware is: 61924 bytes.
11/26/14 20:25:39.559 Module HomeMatic BidCoS: Debug: Current block size is: 290 bytes.
11/26/14 20:25:39.560 Module HomeMatic BidCoS: Debug: Current block size is: 290 bytes.
11/26/14 20:25:39.560 Module HomeMatic BidCoS: Debug: Current block size is: 290 bytes.
[…]
11/26/14 20:25:39.783 Module HomeMatic BidCoS: Debug: Current block size is: 290 bytes.
11/26/14 20:25:39.786 Module HomeMatic BidCoS: Debug: Current block size is: 290 bytes.
11/26/14 20:25:39.787 Module HomeMatic BidCoS: Debug: Current block size is: 18 bytes.
11/26/14 20:25:39.789 Module HomeMatic BidCoS: COC “COC”: Info: Sending (COC): 0A353011FD0786321767CA
11/26/14 20:25:39.790 Debug: Writing: As0A353011FD0786321767CA
Ar

11/26/14 20:25:40.312 HomeMatic BidCoS packet received (COC, RSSI: 0x2A): 0A358002321767FD078600
11/26/14 20:25:40.314 Info (COC): Packet processing took 2 ms.
11/26/14 20:25:40.315 Module HomeMatic BidCoS: Info: Enter bootloader packet was accepted by peer.
11/26/14 20:25:40.946 HomeMatic BidCoS packet received (COC, RSSI: 0x2B): 14000010321767000000004C455130393933393339
11/26/14 20:25:40.947 Info (COC): Packet processing took 1 ms.
11/26/14 20:25:41.018 Module HomeMatic BidCoS: COC “COC”: Info: Sending (COC): 0F4200CB000000321767105B11F81547
11/26/14 20:25:41.018 Debug: Writing: As0F4200CB000000321767105B11F81547
Ar

11/26/14 20:25:41.019 Module HomeMatic BidCoS: Info: Enabling update mode.
11/26/14 20:25:41.019 Debug: Writing: AR

11/26/14 20:25:41.120 Module HomeMatic BidCoS: COC “COC”: Info: Sending (COC): 0F4320CB000000321767105B11F81547
11/26/14 20:25:41.121 Debug: Writing: As0F4320CB000000321767105B11F81547
Ar

11/26/14 20:25:46.132 Module HomeMatic BidCoS: Info: Disabling update mode.
11/26/14 20:25:50.449 Debug: Writing: X21
Ar

11/26/14 20:25:53.827 HomeMatic BidCoS packet received (COC, RSSI: 0x2A): 0D00A410321767FD078606000000
11/26/14 20:25:53.921 Module HomeMatic BidCoS: COC “COC”: Info: Sending (COC): 0A008002FD078632176700
11/26/14 20:25:53.922 Debug: Writing: As0A008002FD078632176700
Ar

11/26/14 20:25:53.922 Info (COC): Packet processing took 95 ms.
11/26/14 20:25:55.981 HomeMatic BidCoS packet received (COC, RSSI: 0x29): 0901A03F321767FD0786
11/26/14 20:25:56.075 Module HomeMatic BidCoS: COC “COC”: Info: Sending (COC): 0F01803FFD078632176702021C08E5C3
11/26/14 20:25:56.076 Debug: Writing: As0F01803FFD078632176702021C08E5C3
Ar

11/26/14 20:25:56.170 Module HomeMatic BidCoS: COC “COC”: Info: Sending (COC): 0A018002FD078632176700
11/26/14 20:25:56.170 Debug: Writing: As0A018002FD078632176700
Ar

11/26/14 20:25:56.170 Info (COC): Packet processing took 189 ms.
11/26/14 20:25:56.149 HomeMatic BidCoS packet received (COC, RSSI: 0x29): 0C02865A321767000000A8D531
[/quote]

The thermostat goes correctly into FUP mode and displays 1.1 and SYn at the end.


#4

I will look into it. I haven’t tested firmware updates with a COC for a while. I should have a few minutes on Sunday and hopefully can tell you a little more then :wink:.

Cheers,

Sathya


#5

Hey,

that was a bug [1]. It’s fixed in the next nightly (0.5.14-56) and in Homegear 0.5.15.

Thanks :wink:.

Regards,

Sathya

[1] https://github.com/Homegear/Homegear/issues/121


#6

I was only able now to test it, and it worked perfectly. Thanks!