edgehog-device-manager / edgehog-esp32-device Goto Github PK

6.0 3.0 4.0 237 KB

Edgehog ESP32 Device is a component for Espressif esp-idf written in C, that enables remote device management using Astarte MQTT connection.

License: Apache License 2.0

CMake 1.02% C 98.98%

iot-device esp32 ota-update device-management iot esp32-library edgehog edgehog-device

edgehog-esp32-device's People

Contributors

Stargazers

Watchers

Forkers

harlem88 francescovaiani bettio sorru94

edgehog-esp32-device's Issues

Rename OSBundle to BaseImage on ESP32 Edgehog SDK

Rename Appliance to System on ESP32 Edgehog SDK

Make ESP32 Component Available to esp-idf Component Manager

Implement OS/Firmware Version Identification

Bump Astarte device sdk to v1.2.0

Bump to latest version of Astarte device sdk.

edgehog-esp32-device/idf_component.yml

Line 27 in b7b6260

version: "v1.1.2"

Define a Device API for Publish Battery Status

LedBehavior: GPIO still active after behaviors

If you execute one of the behaviors implemented by LedBehavior, the GPIO remains enabled after execution.

To reproduce it, go on Edgehog frontend page and click the identify button in check my device section.

Support for ESP-IDF 5.0

The ESP-IDF 5.0 was released in December 2022.
It is a major release with breaking changes. Appropriate fixes should be applied to this project to support this version.

Send `connected` State Along with `WiFiScanResults`

Send connected true/false.
See also: edgehog-device-manager/edgehog-astarte-interfaces#46

Implement API for Publishing Battery Status

Make ESP32 Component REUSE Compatible

Make use of updated OTARequest and new OTAEvent interfaces

Wrong description of geolocation_info telemetry

https://github.com/edgehog-device-manager/edgehog-esp32-device/blob/b7b626035d41d89cceddb97e071a3bd0c2f4ae66/include/edgehog_device.h#LL54C1-L54C1

Implement Remote Management Commands

Add ESP32 Doxygen Doc

ESP32 Edgehog component API doc should be generated using doxygen, and published automatically using CI.

Bump Astarte Device SDK to 1.2.0

This version of Astarte Device SDK introduces many depreciation changes, so create a PR that resolve all warnings.

Decouple the initialization from the first data send

The edgehog_device_new contains both the Astarte interface configuration and the initial sending data. They should also be separated for reasons of integration with other components that use Astarte.

Tipical app Integration with Astarte

add edgehog-interface
add third-party-interface
...
init edgehog
init third-party compent

There are several options for achieving this :

Add init method to edeghog device where move the initial send data.
Move the initial send data to start method
...

Implement Data Rate Control

[Example] Move the Edgehog setup before Astarte device start

Move from the example the edgehog_device_new function before the astarte_device_start function, this also prevents publication of data before publishing the Astarte introspection.

edgehog-esp32-device/examples/edgehog_app/main/main.c

Line 151 in 93bad61

edgehog_device_telemetry_config_t telemetry_config
        = { .type = EDGEHOG_TELEMETRY_SYSTEM_STATUS, .period_seconds = 3600 };

    edgehog_device_config_t edgehog_conf = { .astarte_device = astarte_device,
        .partition_label = "nvs",
        .telemetry_config = &telemetry_config,
        .telemetry_config_len = 1 };
    edgehog_device = edgehog_device_new(&edgehog_conf);

    if (!edgehog_device) {
        ESP_LOGE(TAG, "Failed to create Edgehog device");
        return;
    }
    
    ...
    
     if (astarte_device_start(astarte_device) != ASTARTE_OK) {
        ESP_LOGE(TAG, "Failed to start astarte device");
        return;
    }