For https://tovvel.nl I'm running meshtasticd on linux for the ingestor, without an actual radio but with the UDP multicast protocol so it can get the state of the mesh that way.
(Reason for this is I've already got meshsense connected to the actual nodes)
It works well, but in the page header the mesh is reported as being on 915MHz and I'm not sure where it's getting that. The node itself, despite having no radio, is configured to use the EU_868 preset. And for all the nodes, including the ingest node itself, potatonet is correctly reporting 868 MHz. But the header continues to claim 915...
I fully admit I haven't dug into the source yet to try and see if I can work this out myself - maybe I will if I have some time next week.
For https://tovvel.nl I'm running `meshtasticd` on linux for the ingestor, without an actual radio but with the UDP multicast protocol so it can get the state of the mesh that way.
(Reason for this is I've already got meshsense connected to the actual nodes)
It works well, but in the page header the mesh is reported as being on 915MHz and I'm not sure where it's getting that. The node itself, despite having no radio, is configured to use the EU_868 preset. And for all the nodes, including the ingest node itself, potatonet is correctly reporting 868 MHz. But the header continues to claim 915...
I fully admit I haven't dug into the source yet to try and see if I can work this out myself - maybe I will if I have some time next week.
<!-- github-sync-id:3551232518 -->
I'm an idiot and didn't notice that was just set via environment variables - this one wasn't listed in the docs for setting it up with Docker in my defense :)
I'm an idiot and didn't notice that was just set via environment variables - this one wasn't listed in the docs for setting it up with Docker in my defense :)
<!-- github-comment-id:3445162997 -->
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.
For https://tovvel.nl I'm running
meshtasticdon linux for the ingestor, without an actual radio but with the UDP multicast protocol so it can get the state of the mesh that way.(Reason for this is I've already got meshsense connected to the actual nodes)
It works well, but in the page header the mesh is reported as being on 915MHz and I'm not sure where it's getting that. The node itself, despite having no radio, is configured to use the EU_868 preset. And for all the nodes, including the ingest node itself, potatonet is correctly reporting 868 MHz. But the header continues to claim 915...
I fully admit I haven't dug into the source yet to try and see if I can work this out myself - maybe I will if I have some time next week.
I'm an idiot and didn't notice that was just set via environment variables - this one wasn't listed in the docs for setting it up with Docker in my defense :)
Thanks for bringing this up. I'll double check all config flags :)