#Sonoff firmware trouble

1 messages · Page 1 of 1 (latest)

shell pecan
#

@visual geyser here, let's move this into a thread to keep things organized

visual geyser
#

just to be clear about it; Non-V2 is P and V2 is E?

shell pecan
#

Yep

visual geyser
# 
age;edition;version;shortpath;path;name;windows driver;
new;E;v2;/dev/ttyACM0;/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20230221140743-if00;SONOFF Zigbee 3.0 USB Dongle Plus V2, s/n: 20230221140743 - ITEAD;USB-Enhanced-SERIAL CH9102 (COM12);
old;P;;/dev/ttyUSB0;/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_4cb415d0ada4ed11bf54e8a32981d5c7-if00-port0;Sonoff Zigbee 3.0 USB Dongle Plus, s/n: 4cb415d0ada4ed11bf54e8a32981d5c7 - ITead;Silicon Labs CP210x USB to UART Bridge (COM13);

old = V2 = E
new = P
#

made this to keep track of it

visual geyser
shell pecan
visual geyser
#

old and new corresponds to when i got them

#

i can differentiate them physically because the "old" one has hot glue on it

visual geyser
shell pecan
#

Right. The two sticks have different firmware, the multi tool is only for the P stick

visual geyser
shell pecan
#

It can't communicate with the E stick for the same reason you can't flash the P stick with the web flasher

shell pecan
#

Make sure to unzip it first

visual geyser
#

should i erase before writing? or just write

shell pecan
#

Erase too

#

Erase fixes the nvram issue, write restores the firmware

visual geyser
#

i dont need to change the iEEE stuff tho, right?

shell pecan
#

Nope

visual geyser
shell pecan
#

Now you can try to restore the backup in ZHA, like before 🙂

visual geyser
#

do i need to reflash the normal fw before that?

shell pecan
#

Which one?

visual geyser
#

the one you sent earlier on the website

shell pecan
#

No, you're all set

visual geyser
#

okay, lemme try restoring

shell pecan
#

Migrate only works if you have something plugged in

#

Re-configure is to "migrate" if you have only one adapter

#

Migration has to reset the old adapter, which is why there is a separate button.

visual geyser
#

gotcha

shell pecan
#

Yours was already reset when the migration half worked so you just re-configure

visual geyser
#

meh

#

still unknown error :c

shell pecan
#

What's in the log?

visual geyser
# shell pecan What's in the log? 
2024-05-22 01:31:30.669 ERROR (MainThread) [aiohttp.server] Error handling request
...
  File "/usr/src/homeassistant/homeassistant/components/zha/config_flow.py", line 769, in _async_create_radio_entry
    await self.hass.config_entries.async_setup(self.config_entry.entry_id)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1726, in async_setup
    raise OperationNotAllowed(
homeassistant.config_entries.OperationNotAllowed: The config entry SONOFF Zigbee 3.0 USB Dongle Plus V2, s/n: 20230221140743 - ITEAD (zha) with entry_id 59ee77922cec06602094883ec9eba639 cannot be setup because is already loaded in the ConfigEntryState.SETUP_IN_PROGRESS state
shell pecan
#

Looking better, that's not a problem with the adapter

#

I think ZHA may have tried to re-connect to the old stick in the middle of the migration, which is a bug :/

#

Try it once more, should work

visual geyser
shell pecan
#

Submit

visual geyser
#

had to select the backup json again but now its loading

#

yeah nah it just hates me

shell pecan
#

Hmm. It could be that the broken migration from before is preventing it from properly migrating now

#

Try to reload HA Core, ZHA should be in a failed state (since your adapter is missing) and you can try the re-configure flow one more time

visual geyser
#

just for your information it was the same exception

homeassistant.config_entries.OperationNotAllowed: The config entry SONOFF Zigbee 3.0 USB Dongle Plus V2, s/n: 20230221140743 - ITEAD (zha) with entry_id 59ee77922cec06602094883ec9eba639 cannot be setup because is already loaded in the ConfigEntryState.SETUP_IN_PROGRESS state
#

will try reloading

visual geyser
shell pecan
#

Normal restart without reboot

visual geyser
#

gotcha, its doing that now

#

that was all for the P stick now right

shell pecan
#

Yep

#

If you keep the -E stick plugged in, ZHA will just start up normally and keep using it

visual geyser
#

the E stick should get the firmware you sent earlier, right? the gbl file

shell pecan
#

The E stick should have that firmware installed, no?

visual geyser
#

its showing up now and i would like to re-install the fw just to be sure

shell pecan
#

You can if you want, it shouldn't make any difference

visual geyser
#

it's installing rn, just to be sure

#

is this also NVRAM? or is the firmware layout on the E variant different

shell pecan
#

The E firmware is completely different

#

Nothing in common whatsoever

visual geyser
#

so the NVRAM of the P variant is the equivalent of the firmware of the E variant? just different things but all pretty much firmware

#

should i restore settings anyway?

shell pecan
#

Do any devices work?

visual geyser
shell pecan
visual geyser
shell pecan
#

The E stick doesn't have this problem. The firmware you flashed earlier just had a modification to enable the remote you were using to communicate with the stick

#

It didn't work 😄

visual geyser
visual geyser
shell pecan
#

No, the firmware modification test 😄

visual geyser
#

ah lul

shell pecan
#

I would give your network 10 minutes and see what devices work. If none are communicating, re-configure and restore that backup JSON you downloaded.

visual geyser
#

just want you to know that i now have the NEW stick in HASS for zha, the old one is unplugged for now

#

before i had the new one for the testing with z2m

visual geyser
#

just cant get my remote working still xD

#

1 step forward 1 step back

shell pecan