The device simulator is now generating values and sending through MQTT. The values get displayed and updated live on the AR marker overlay without glitching. A few days ago making elements clickable was figured out. This will be useful when there’s a need for buttons on the AR view. The topic structure was updated as well. The next step will be to make the device send and receive the data. The AR program is not set up for multiple devices or markers just yet. That will be future work as well.
AR markers triggering messages to send to the alternate (secure) MQTT server is working. The preliminary topic structure was chosen, which gives each marker type its own topic, and sends the state when it enters the view, still in the view, and exits the view. Next step is to make sure the device can receive these messages, and have the device send its sensor data – only when the marker is in view (as to not overload this MQTT server (since it isn’t running on our AWS)). As well, next step is sending a marker state heartbeat when it is in view.
A bit of running in a circle to get tls/ssl to work. It didn’t work at first. Some of the issue was around the common name, and the lack of clarity about what that actually needs to be. Ran in to issues with the mosquitto config file not being updated, and trying to start / stop mosquitto. This resulted in needing to reboot the ec2 instance often during the trial and error. Eventually was able to get back to a working state. The next steps will be to regenerate the certificates in the proper format, make sure the ports are open, and whatever else will be needed to get this working.
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.