Closed Murray112 closed 9 months ago
Same for me, then i disabed Mosquitto broker and restarted HA and it worked.
Solved! Thanks for the tip! Have a nice day ;)
Hi,
I seem to have the same problem. Restarting seems to not have helped. zha, zigbee2mqtt and mosquito are all disabled and i tried restarting HA.
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
s6-rc: info: service banner successfully started s6-rc: info: service cc2652-flasher: starting [10:58:58] INFO: Starting CC2652P flasher with Sonoff socket://192.168.0.59:8123 Setting filename to /root/firmware.hex sonoff Opening port socket://192.168.0.59:8123, baud 500000 Reading data from /root/firmware.hex Your firmware looks like an Intel Hex file Connecting to target... ERROR: read failed: socket disconnected [10:58:59] INFO: cc2652-flasher-up script exited with code 1 s6-rc: warning: unable to start service cc2652-flasher: command exited 1 /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: stopping 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
Good morning!
I contact you because I'm struggling to flash my dongle with the latest firmware and It seems it doesn't want to flash. I've activated the option for sonoff and tried with the bootloader button too but always the same message. I put the Home assistant IP.
This is the log:
`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: ZigStar TI CC2652P/P7 FW Flasher ZigStar TI CC2652P/P7 firmware flasher add-on
Add-on version: 0.4.0 You are running the latest version of this add-on. System: Home Assistant OS 11.5 (aarch64 / raspberrypi4-64) Home Assistant Core: 2024.2.1 Home Assistant Supervisor: 2024.01.1
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 [10:16:19] INFO: Starting CC2652P flasher with Sonoff socket://192.168.1.30:8123 Setting filename to /root/firmware.hex sonoff Opening port socket://192.168.1.30:8123, baud 500000 Reading data from /root/firmware.hex Your firmware looks like an Intel Hex file Connecting to target... ERROR: read failed: socket disconnected [10:16:21] 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`
I decided to update because I had several problems with connection devices in my zigbee net.
I hope that is only a configuration problem.
Thanks a lot for your help.
Murray