upbeat prairie
https://www.home-assistant.io/connectzbt1/ says "Nothing changes for current users of the multiprotocol firmware who are happy with their experience. The experimental multiprotocol firmware will remain available, but we will not recommend it to new users." But in HA the add-on now shows as deprecated with a message that it will stop working soon ...
lethal shuttle
https://www.home-assistant.io/connectzbt1/ says "Nothing changes for current use...
multiprotocol has been "not recommended" and deprecated for a while. if you had a setup with it already it would not necessarily break but you should not start using it with a new setup.
upbeat prairie
Ok thanks so i don't need to worry about it being removed?
this kind of has me worried ...
Multiprotocol is no longer supported and will be removed in the near future! Disable multiprotocol support by migrating your radio back to Zigbee or Thread firmware.
lethal shuttle
> Multiprotocol is no longer supported and will be removed in the near future! D...
it will likely be removed at some point. however i am not aware of the exact timeline on it. If i was to guess its probably being left so long as it works but if another change somewhere else necessitates a fix it wont come and instead will just be removed.
I recommend that you do not use it and make plans to transition away from it.
upbeat prairie
It works perfectly fine for me and i bought this hardware for the multiprotocol support ...
seems a bit :/
I am a ha cloud subscriber and bought hardware to help support the project so this feels ... not great
lethal shuttle
I think it was technically only ever "experimental" but I understand your point and you are not the only one.
upbeat prairie
Yeah.
Experimental and it works for me.
Not experimental and now we will remove the add-on!
I'd understand if SI was dropping support but i don't think they are from what I was looking at.
lethal shuttle
basically everyone dropped it as it can be unstable. sonoff did push some updates bring it back recently in an experiment with one of their devices HERE
the way most people go these days is a smligh adaptor that has 2 radios in it so you can use both.
Perhaps a next gen ZBT-2 will appear in the future and support it better. i am aware there is some work being zone on a ZBT-2 but i have no idea about what its feature set would be.
that's my understanding of the situation anyway (although i dont claim to be an expert on it)
you might just end up in a situation where you wont be able to update and keep it working. i don't see why it would stop working with older versions. its unfortunately just the way its going to go.
upbeat prairie
basically everyone dropped it as it can be unstable. sonoff did push some update...
yeah i saw that. I was thinking of picking up that hardware to use regardless of multiprotocol support as a just in case it breaks or a "just in case it all comes good" bet. I would like to drop zigbee but matter devices aren't available at the same price point atm and thread isn't always selected - wifi isn't always a good solution for me.
sand sail
to my understanding, the best solution - now and in the future - is to use separate radios for zigbee and thread, ideally running on different channels. getting a second radio would make sense as a way to switch away from the multiprotocol firmware, and you might see some improvements in network stability or latency after switching.
some home assistant branded hardware that i'd be interested in would be a standalone thread border router with ethernet (poe?) and/or wifi connectivity. that would be useful for extending or improving signal in thread networks, would be more reliable for thread than serial-over-ip radios like the smlight stuff, and would be helpful for people who aren't using HAOS, and therefore can't use the OTBR add-on.
tiny current
You don’t necessarily need thread radio built on HA host machines. Devices like HomePod, Nest hub even Eero routers can do the job, that’s how it’s designed.