openevse_esp32_firmware
openevse_esp32_firmware copied to clipboard
OpenEVSE
lora: Initial work at LoRaWAN support. Empty announcements.
This has been greatly simplified using a common LoRa library, and removing the Heltec code.
- If enabled for the board, LoRa is setup using the network credentials hard coded within the code (these can be pulled via the OpenEVSE storage, but just not there yet)
- If a LoRaWAN gateway is in range (a few miles), the device will begin to announce the OpenEVSE status. (the status is empty at the moment, need to pull from OpenEVSE still. The status information needs packed into as small a datastructure as possible)
- The LoRaWAN network (in my case The Things Network) will receive the data, translate it, and pass it onto any configured integrations the user specifies. (aka, Plugshare??? :-) )
Testing has been limited thus far, without a spare OpenEVSE module testing is tough since the ESP32 enters a "Unable to communicate to OpenEVSE" loop. The code was taken from another (working) project I have.
All code remains inactive however unless you build for the heltec LoRa board.
Oh.. beyond The Things Network, this code could be used to connect to any other LoRaWAN network (915 Mhz in the US). one option is Helium. https://developer.helium.com/console/cli
Not sure of the options there, however there are a ton of Helium devices out there today. https://network.helium.com/coverage
Ok. The latest patch has a bunch of fixes and actually pushes useful data over LoRaWAN :-)
The only change which is active when building non-lora enabled firmware is the addition of the "create_rapi_packed" function to input.cpp. This takes important values and packs them into a bunch of uint8's to be broadcast over LoRa. If a value could be reasonably > 255, I added a conversion factor (voltage, elapsed, temp)
Keep in mind this is all still untested. I need to short circut the OpenEVSE communication tests to try and fake the ESP32 to send some data over LoRaWAN.