Error flashing 20240710FW on my TubesZB Gateway - 'utf-8' codec can't decode byte 0xcb in position 7008

[Kugelfang666]

Hi all,

I just tried to flash my tubes ZB gateway with this add-on to the new released FW Your firmware 20240710.

Config of the Addon:

network_device: 192.168.178.97:6638
device: /dev/ttyS0
trigger_esphome_bsl: true
device_type: false
flow_control: false
firmware_url: >-
  https://github.com/Koenkk/Z-Stack-firmware/raw/master/coordinator/Z-Stack_3.x.0/bin/CC1352P2_CC2652P_launchpad_coordinator_20240710.zip

The process was aborted with the following logs:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service banner: starting

-----------------------------------------------------------
 Add-on: TubesZB TI CC2652 FW Flasher
 TubesZB TI CC2652 firmware flasher add-on
-----------------------------------------------------------
 Add-on version: 0.2.2
 You are running the latest version of this add-on.
 System: Home Assistant OS 13.1  (amd64 / generic-x86-64)
 Home Assistant Core: 2024.8.3
 Home Assistant Supervisor: 2024.08.0
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service banner successfully started
s6-rc: info: service cc2652-flasher: starting
[08:12:23] INFO: Triggering Bootloader mode on 192.168.178.97
[08:12:48] INFO: Starting cc2652 flasher with socket://192.168.178.97:6638
Setting filename to /root/firmware.hex
Opening port socket://192.168.178.97:6638, baud 500000
Reading data from /root/firmware.hex
Your firmware looks like an Intel Hex file
ERROR: 'utf-8' codec can't decode byte 0xcb in position 7008: invalid continuation byte
[08:12:48] INFO: cc2652-flasher-up script exited with code 1
s6-rc: warning: unable to start service cc2652-flasher: command exited 1
s6-rc: info: service banner: stopping
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service banner successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

any idea on what I did wrong?

[Kugelfang666]

somehow this does not look like a legit response

[tube0013]

I suspect this has to do with Koenkk/Z-Stack-firmware#512

I'll look at repackaging the binary and posting to GitHub to work around this shortly.

I deleted the non-responsive response.

[tube0013]

Update the addon, added options flash the latest release - pointed to new zips on my repo, any doubt you can compare the md5hashes to the files from koenkk/Z-Stack.

[Kugelfang666]

:-) much appreciated, will test later and report back!

No need to test, if I would not trust you I would not use your hardware in the first place ;-)