#Disable Multiprotocol Support

116 messages · Page 1 of 1 (latest)

inland crow
#

Hi All,

I have recently (and not the first time I might add) had an issue where the multiprotocol addon didn't start properly, even with start and watchdog enabled,
I have nor decided to remove multiprotocol support, but in the Setting > System > hardware (where the docs say to disable it) I only have CPU, Memory and All Hardware,

I can not find the option to disable this,
Hardware,
HA-Yellow

Core
2024.10.4
Supervisor
2024.10.3
Operating System
13.2
Frontend
20241002.2

any help is appreciated

tranquil wraith
#

You can also remove the Multiprotocol add-on, disable ZHA and remove the Thread integrations.
Install the SiliconLabs Flasher add-on, configure and run it.
Look at its logs. If it finishes without errors, you can remove the add-on, enable ZHA again and use the ZHA settings to change the radio to the onboard one.

#

Regarding the "I have recently (and not the first time I might add) had an issue" part: Multiprotocol is not recommended and its development has been frozen.

inland crow
#

does the flasher automatically take it back to ZHA?

tranquil wraith
#

No. The flasher just flashes the Zigbee firmware.

#

You have to migrate the radio in the ZHA settings yourself.

inland crow
#

ZHA still says Yellow multiprotocol, this is not an issue is it?

tranquil wraith
#

At least if there is no option to do everything automatically when using the CONFIGURE button on the hardware page,

tranquil wraith
inland crow
#

it looks like it is only, I clicked Migrate to Skyconnect (paraphrasing) keep settings, it went unkown error > initilising > to running

tranquil wraith
#

You talked about migrating the Yellow`s radio from Multiprotocol to Zigbee. The SkyConnect has nothing to do with that.

inland crow
#

sorry, I didn't read the full text, just the dev att something 1

i had 0, 1 with a lot of text (where the multiprotocol one was) and 2

#

I assume this means there is an issue?

tranquil wraith
#

Did you remove the Multiprotocol add-on and flashed the Zigbee firmware successfully before?

inland crow
#

I think so, it gave me an exit with code 0

#

I am running it again

#

same result

tranquil wraith
#

Reboot the Yellow and try again

inland crow
#

re-configure or migrate?

tranquil wraith
#

migrate

inland crow
#

even with migrate, just says error, performing a power cycle

#

I don't restore backup do I?

tranquil wraith
#

You do, if you want the devices to stay paired.

#

What do the network info in ZHA say?

inland crow
#

still booting, please hold

#

my backup settings?

tranquil wraith
#

What do the network info in ZHA say?

inland crow
#

I currently can't get to that page

tranquil wraith
inland crow
#

I do have a conbee II somewhere i think

tranquil wraith
inland crow
#

performing a full restore of HA, to before the latest update, ffs, never should have enabled this

tranquil wraith
#

You aren't restoring an HA backup now, are you? facepalm

inland crow
#

yes

#

I am aware that will run the multiprotocol and put it back into that spot

tranquil wraith
#

An HA backup does not restore the radio firmware.

inland crow
#

but the Mutliprotocol add-on should, as it has the auto flash enabled

tranquil wraith
#

Multiprotocol IS the problem, not the solution.

inland crow
#

I am aware, but if I can get ZHA online and pull a manual backup, I can then delete ZHA and restore it once the radio is working correctly, correct?

tranquil wraith
#

Deleting ZHA is not necessary.

inland crow
#

any other suggestions other than manual flashing the radio?

tranquil wraith
#

I already posted my suggestion. Removal of Multiprotocol, reflashing the Zigbee firmware and migration to the on-board radio.

inland crow
#

that didn't work, maybe I messed it up, but it seamed fairly straight forward

tranquil wraith
#

If you don't mind re-pairing ZHA devices, you can also remove ZHA and restart HA (after flashing the Zigbee only firmware).

inland crow
#

some are in a wall, so I would rather not if I can avoid it

tranquil wraith
#

Then the ZHA migration and/or ZHA backup are the ways to go.

inland crow
#

HA is back up, and the way the mutiprotocole come up and thread and zigbee both came online, the the flashing didn't work originally

#

universal_silabs_flasher.flash INFO Firmware version '4.3.1-4f7f9e99-dirty-e3b0c442' (4.3.1) is flashed, not re-installing

tranquil wraith
#
  • Disable ZHA integration
  • Remove Thread integration
  • Remove OpenThread integration
inland crow
#

you asked for this earlier

#

ZHA is disabled

#

I didn't delete thread last time

nocturne cave
#

Did you run the Flasher addon?

tranquil wraith
#
  • Stop and uninstall Multiprotocol add-on
  • Install and configure SiliconLabs Flasher add-on
  • Run SiliconLabs Flasher add-on
  • Look at add-on protocol and make sure it stops with code 0
  • Uninstall SiliconLabs Flasher add-on
#
  • Enable ZHA integration
  • Migrate radio to the /dev/ttyAMA1 one
inland crow
#

mutli protocole removed

nocturne cave
inland crow
#

isn't the old "stick" not there anymore?

#

like it was the multiprotocol

#

universal-silabs-flasher-up script exited with code 0

nocturne cave
#

Right. Just select "re-configure the current radio" instead of "migrate" in ZHA.

inland crow
#

I just enabled ZHA

#

what option?

nocturne cave
#

Disable it once more, since it's going to try to connect to the (now deleted) multiprotocol addon

#

Oh, looks like it still works like that. You want to pick "restore an automatic backup"

#

You should have only a single network in the dropdown

inland crow
#

and select the one it just made?

nocturne cave
#

What does the dialog show?

inland crow
#

I have 3 backups

nocturne cave
#

Hmmm. Do you have access to your /config/ folder?

inland crow
nocturne cave
#

Can you upload your zigbee.db file here?

#

Can you also click the "Enable Debug logging" option?

inland crow
#

for some reason it appears to be up

#

even after the error

nocturne cave
#

Hmm, interesting. There may be some bug with the integration reloading/retrying during migration.

inland crow
#

it is super slow though

nocturne cave
#

If ZHA has been offline for a while it will try to communicate with every device on your network to pull updated state, give it a few minutes

inland crow
#

restarting HA

nocturne cave
#

This is also improved in the beta

inland crow
#

right

#

makes sense

#

I still expect status updates to be a little quicker

nocturne cave
#

What do you mean?

inland crow
#

the hue motion sensor is set to a 10 second occupancy window

#

but after 10 seconds it still says detected

#

and trying to read the attribute times out

nocturne cave
#

I would give it a try after migration, since you're now running up-to-date firmware

#

And after the status for your mains-powered devices has been read

inland crow
#

and the hue's are flashing as if there is no connection

#

do I have to power cycle the zigbee routers?

nocturne cave
#

If they were children of the coordinator and the coordinator has been offline for a while, they could think it's offline. I'd just give it 10 minutes.

inland crow
#

so i could be just too darn impatient

#

ZHA seams to have a 6 second delay

#

and node red is broken

#

nothing in ZHA is working correctly

tranquil wraith
#

I would try to powercycle the Yellow (shutdown, pull power power on again)

inland crow
#

would not?

#

leaving Multi protocol on

#

ZHA is clearly not working

tranquil wraith
inland crow
#

I tried, nothing works

#

now 5:30 am, been up all night working on this shit

#

is z2m better than zha?

#

nope, everything is broken...

#

I didn't have the configure button the first time around

#

and, added bonus, the Thread intergration is no longer appearing

inland crow
#

after many hours of wiping and trying
I even flash to thread only and back again

I deleted the zigbee.db file and restored from the manual backup, it has so far auto discovered 50% approx of the devices

nocturne cave
#

I would restore your old backup, as otherwise your entity names and customizations are all gone. There's no difference between the network state from when ZHA was running without multi-PAN and the network after you manually uploaded the JSON file.

#

Figuring out why you have a multi-second delay would be the best way forward, because multipan is not going to stick around forever and whatever issue it's hiding needs to be fixed