Mobile App disconnecting node when integration is active #29
Replies: 2 comments
-
Frankly don't know if this is a bug or a feature. I did ask me this as well, I think that is something we need to ask / discuss in https://github.com/meshtastic/firmware/discussions My educated guess is that it rather a coincidence caused by need for simplicity (and maybe some technical limitations of the firmware libraries) But it is a known limitation for sure. There are some interesting ideas in #26 and PoC with the web interface worked ok, so there might be an option to workaround that meshtastic limitation by allowing the mobile app to connect to home assistant via bluetooth (and home assistant itself pretending to be a regular node). It should be possible on a technical level, but I haven't looked into if and how home assistant itself supports advertising as bluetooth peripheral |
Beta Was this translation helpful? Give feedback.
-
@daniel-hofer Please check the latest version, it now comes with bundled meshtastic web client and support to connect to the integration. Ensure to enable it by pressing configure on your existing meshtastic configuration I have not yet explored the bluetooth part, it is probably an exotic use case that you would want to connect via bluetooth to home assistance instance, the web client is the more natural fit for access. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I was happy to use this integration in home assistant with my raspberry zero hat node connected via WiFi.
Aber use I figured out that the mobile app is disconnecting the same node when the ha integration is enabled. So I can only one the app or the node with ha. Is this a bug or a feature?
Beta Was this translation helpful? Give feedback.
All reactions