Since the AR view uses the camera, this means the connection has to be secure using ssl. MQTT was added to the AR code, but it can’t communicate over websockets – it has to be secure websockets. The next step will be to generate certificates for the ssl connection.
Set up AR framework, the AR detection method that will be used is with custom markers. Ran in to a lot of debugging. Transparent background and cache on the marker pattern were the culprits. Figured it out, and everything works! Marker can be detected, tracks nicely, and calls some javascript. Testing at various distances will be needed to understand how close you can be to the marker. Works at 60fps on modern mobile device. Onto the next, which is integrating MQTT into this.
Sending updates from an ESP32 device to the MQTT server is working! Right now, it’s just barebones running with default values for GPS latitude, longitude, and a random number for air temperature. Ran in to a few issues with library selection, but that was easily remedied. It took some time to test the types that are sent and the precision. Once it started to work, was simple. The library being used will retry connection to the MQTT server in 15 seconds if it loses connection. The next steps are either AR view, score counter, or making the sensor device. Tune in for the next log to see which one of those is chosen.
Next step is to start adding new devices to the map – so on to the hardware with MQTT on an ESP32.
