In order for MeshSense to support future firmware updates, it would need to use the maintained version of the JS code. It's not immediately clear to me how that would be implemented without looking further into the Monorepo. Unless I'm missing it, the usage documentation is not present.
Admittedly, having had to fork meshtastic/js to take advantage of updated protobufs and making modifications to fix integration issues, it's a bit deflating to have to revisit all over again.
Who knows, maybe porting to the new codebase won't be as difficult as it sounds, but it will take valuable time to research, implement, and test so I'm creating this issue to track the effort.
In order for MeshSense to support future firmware updates, it would need to use the maintained version of the JS code. It's not immediately clear to me how that would be implemented without looking further into the Monorepo. Unless I'm missing it, the usage documentation is not present.
Admittedly, having had to fork
meshtastic/jsto take advantage of updated protobufs and making modifications to fix integration issues, it's a bit deflating to have to revisit all over again.Who knows, maybe porting to the new codebase won't be as difficult as it sounds, but it will take valuable time to research, implement, and test so I'm creating this issue to track the effort.