Let the Spark announce itself for zeroconf discovery.
Hostname is device ID, so it is always unique.
The brewblox server can find all hosts implementing the brewblox service. Tested on hardware (P1) and using the simulator running in docker.
I have also added a simple http server on port 80. If the user visits the IP address of the Spark, he can be instructed that it is not intended to be used that way and a separate BrewBlox server should be used to communicate with the Spark.
We could later expand this simple http page with some status info.
Bob, please see if you can use this to find running Sparks automatically. They're visible using avahi-discover.
We can use the TXT records for extra info like the API version or firmware version.
Let the Spark announce itself for zeroconf discovery.
Hostname is device ID, so it is always unique.
The brewblox server can find all hosts implementing the brewblox service. Tested on hardware (P1) and using the simulator running in docker.
I have also added a simple http server on port 80. If the user visits the IP address of the Spark, he can be instructed that it is not intended to be used that way and a separate BrewBlox server should be used to communicate with the Spark.
We could later expand this simple http page with some status info.
Bob, please see if you can use this to find running Sparks automatically. They're visible using avahi-discover.
We can use the TXT records for extra info like the API version or firmware version.