currently i have to unplug heltec device from my meshcore-hub vm and manage channel changes on my desktop pc, then i have to re-plug it into vm and restart docker container.
could be nice to add a function where you can manage channels directly from meshcore-hub.
currently i have to unplug heltec device from my meshcore-hub vm and manage channel changes on my desktop pc, then i have to re-plug it into vm and restart docker container.
could be nice to add a function where you can manage channels directly from meshcore-hub.
<!-- github-sync-id:3943907475 -->
We could configure this as a comma/other delimited environment variable
What aspects of channel setup are we talking about?
We could add channels with a name and encryption secret: https://github.com/meshcore-dev/meshcore_py/blob/3f561904232c4c3263d2aac921e00f2f859bc54f/src/meshcore/commands/device.py#L187
We could configure this as a comma/other delimited environment variable
<!-- github-comment-id:3922329509 -->
We now use LetsMesh Observer model so this is now handled by the https://github.com/agessaman/meshcore-packet-capture which allows the decryption and parsing of private channels without configuring them on the companion node.
We now use LetsMesh Observer model so this is now handled by the https://github.com/agessaman/meshcore-packet-capture which allows the decryption and parsing of private channels without configuring them on the companion node.
<!-- github-comment-id:4271670993 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
currently i have to unplug heltec device from my meshcore-hub vm and manage channel changes on my desktop pc, then i have to re-plug it into vm and restart docker container.
could be nice to add a function where you can manage channels directly from meshcore-hub.
What aspects of channel setup are we talking about?
We could add channels with a name and encryption secret: https://github.com/meshcore-dev/meshcore_py/blob/3f561904232c4c3263d2aac921e00f2f859bc54f/src/meshcore/commands/device.py#L187
We could configure this as a comma/other delimited environment variable
We now use LetsMesh Observer model so this is now handled by the https://github.com/agessaman/meshcore-packet-capture which allows the decryption and parsing of private channels without configuring them on the companion node.