You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
puddly and agners have implemented a new zigpy packet API and native tcp:// protocol that the ZHA integration will not be able to use.
Their new tcp:// protocol will allow the ZHA integration and zigpy radio library/libraries to communicate with the radio using TCP/IP which should make for a much faster and more stable connection over a network in theory.
Could you maybe look into implementing this in your ESP firmware builds as an alternative to tunnelling via the ser2net style serial stream server with socket:// protocol (using pyserial)?
This has been implemented in upstream zigpy-znp and bellows radio libraries but does not think it is yet available in ZHA integration(?).
puddly and agners have implemented a new zigpy packet API and native tcp:// protocol that the ZHA integration will not be able to use.
Their new tcp:// protocol will allow the ZHA integration and zigpy radio library/libraries to communicate with the radio using TCP/IP which should make for a much faster and more stable connection over a network in theory.
Could you maybe look into implementing this in your ESP firmware builds as an alternative to tunnelling via the ser2net style serial stream server with socket:// protocol (using pyserial)?
This has been implemented in upstream zigpy-znp and bellows radio libraries but does not think it is yet available in ZHA integration(?).
See puddly's and agners's related work in zigpy:
zigpy/bellows#489
zigpy/zigpy-znp#179
zigpy/zigpy-znp#171
zigpy/zigpy-deconz#206
zigpy/zigpy#1043
The text was updated successfully, but these errors were encountered: