michaelschnyder / ondo Goto Github PK

A log a day
Add time & Date in log and filename
Delete old logfiles

Suggested implementation

1. devices announce themselves via mDNS including the update url/port
2. Small command line application that discovers the devices and sends the firmware

Commandline Sample

• ondo-update --firmware <ardunio-binary.bin>: Shows a list of devices and user has to enter select a specific item
• ondo-update --firmware <arduino-binary.bin> --target <ip | deviceId>: flash a specific device in local network
• ondo-update --firmware <ardunio-binary.bin> --target all: All discoverable devices are updated

Links

• Start mDNS and announce service: https://github.com/esp8266/Arduino/blob/master/libraries/ESP8266mDNS/examples/mDNS-SD_Extended/mDNS-SD_Extended.ino#L50
• Pre-build OTA library: https://github.com/esp8266/Arduino/tree/master/libraries/ArduinoOTA (might be configured to use hostname, password, etc.)
• http://arduino.esp8266.com/Arduino/versions/2.0.0/doc/ota_updates/ota_updates.html

Azure contains a sample for that: https://github.com/Azure-Samples/web-apps-node-iot-hub-data-visualization

Whenever a device receives a command and adjusts it's local settings and talks to AC, after completion, a message with the current state should be transmitted to MQTT

When changing Vertical Swing, nothing happens
When changing fan speed, nothing happens
When changing Quiet, the change is not reflected in the UI

Every 60s, the device should send information about

• Name of device
• SSID
• Free memory
• etc.

the device should only send update temperature information if there was an actual change, but at least once every 60s

A dedicated agent is required for this. See: https://devblogs.microsoft.com/premier-developer/azure-devops-build-pipelines-for-arduino-microcontrollers/

Suggested workflow

1. Trigger update from DevOps Pipelines (extend #10) to Azure IoT or Ondo Backend
2. Store new firmware somewhere (Azure Blob Storage, Ondo Backend?)
3. Change the desired firmware version in device twin
4. Download new firmware on device

Links

• Firmware Updates with Azure IoT: https://docs.microsoft.com/en-us/azure/iot-hub/tutorial-firmware-update
• Download firmware from webserver: http://arduino.esp8266.com/Arduino/versions/2.0.0/doc/ota_updates/ota_updates.html#

After receiving the setup command, a device should send IrCommands to make it easier to position it. The device should send 10 commands during 10s.

The MQTT should offer functionality to update reported properties on Azure IoT Device twin according to IoT Hub DevGuide

• https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-device-twins#device-operations
• https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-mqtt-support#update-device-twins-reported-properties

https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-mqtt-support#receiving-desired-properties-update-notifications

Replace the Losant API calls with Azure IoT Hub calls.

Two options

• directly call Azure IoT Hub API from Webpage
• implement own backend in NodeJs/.NET and proxy request to Azure IoT

Option 2) is preferred as it offers a more secure way to connect to Azure API (does not expose connection String) and offers more flexibility in the long term (i.e. support for Alexa)

It seems that sometimes the MQQT connection (or WIFI) is unreliable and a re-connect happens frequently. Should the connection be unreliable, this results in extremely frequent connection requests.

Idea: Increase the delay between re-connection attempts every time a connection got disconnected after short connection time.

1. The network configuration should become a separate node including signal stranght, SSID, BSSI, IP, Subnet and Gateway information.
2. sensor information needs to be refactored into separate node

The current tokens used by the embedded devices only last for max 365 days.

Options

• Use some kind of registration & refresh API on the cloud (maybe Azure IoT supports that with the device enrollment module)
• Regenerate the access token based on the connection string (some other libraries do that, but depends on some MD5 magic and the #3

Usage of the library EspSaveCrash and upload the results via http to the cloud.

Things to consider

• Clear local memory after successful upload
• Clear local memory after firmware update (relates to #12)

How to: https://mohitgoyal.co/2018/09/19/using-path-filters-in-build-definition-in-azure-devops-vsts/