Charles Crossan

I know a lot of folks have been waiting for this, and I believe I finally have it to a working state! 🎊🎉 I know it's at least working with...

@OttoWinter @jesserockz I think this is ready for review again :-)

@stuartwishart I've got this branch deployed on my ESP32's and it's _mostly_ working. There's an intermittent (once every 5-010 minutes) reboot issue that I think is caused by something in...

> I would love to see this implemented. I would be willing to test if you are at that point. I have been running this on one of my ESP32...

I've been pondering a similar idea: https://discord.com/channels/429907082951524364/524177279270780928/924048338666524692 I want to use Meshtastic as a transport layer for ESPHome API messages; something like this:  My approach would not flash Meshtastic...

The Meshtastic protobuf defines a number of application port; with the idea that more may be added: https://github.com/meshtastic/Meshtastic-protobufs/blob/master/portnums.proto#L9 I am thinking about registering ESPHome as an application port, so that...

Not totally sure, but it's all sensor data (I think wrapped in protobufs).

I've got a similar issue, where one `Version` is displaying _thousands_ of commits: none of which are in the git traversal between the previous `Version` and this `Version`

I'll take a look on Monday. I've actually been using my branch here as part of a build pipeline

I'm having a similar issue: https://github.com/less/less.js/issues/3611#issuecomment-1172325438