• Action taken: the application code is flashed onto IZOKEE D1 Mini, and serial console is monitored.
• Expected result: the chip boots, finds 1-Wire devices, connects to WiFi, connects to MQTT broker, and starts sending samples.
• Actual result: the chip boots, finds 1-Wire devices, connects to WiFi, and fails to connect to MQTT broker, looping with failed, rc=-2 try again in 5 seconds.

1-Wire device address is printed in reverse order (MSB instead of LSB).

IMPORTANT: When this bug is fixed, configurations created at MQTT subscribers will stop working because device address reported will be different.

As an MQTT message consumer, I would like to know which hardware issued the sample, so that I could identify what kind of a sample it is (temperature, humidity, etc.)

Acceptance criteria: MQTT message contains the identifier of the device that provided this particular sample.

#3 demonstrated that there may be non-obvious pitfalls, so it would be nice if the firmware logged not only the IP address, but also all DHCP parameters that it's getting (subnet mask, gateway, and DNS servers off the top of my head), so that possible problems could be easier troubleshooted.