edgehog icon indicating copy to clipboard operation
edgehog copied to clipboard

Easily manage your IoT device fleet with Edgehog at once. Get information on device status, deploy updates, geolocate your devices and much more!

Results 63 edgehog issues
Sort by recently updated
recently updated
newest added

Querying for fields of nested GraphQL object types inside a delete mutation fails, example: ```graphql mutation deleteHardwareType_Mutation($id: ID!) { deleteHardwareType(id: $id) { result { partNumbers { partNumber } } }...

ash-porting

Since we're breaking the API during the porting to Ash, this could be a possibility to revisit how they're handled since we practically never supported locales other than the default...

ash-porting

Right now, sometimes tests fail due to the fact that tags are in a different order on the left hand side and right hand side of an assertion, since they're...

good first issue
chore

Currently if a target update fails before its OTA Operation is started (e.g. unsupported starting version), the reason for the failure is not exposed to the user and it's just...

Right now we have a boolean flag `manual?` which indicates if an OTA Operation was started manually or from an Update Campaign. We should expose the Update Campaign too, so...

Right now, the Edgehog Device Runtime has an MQTT keepalive interval of 120 seconds (the Rust one has a keepalive of 30 seconds). This means that if a device disconnects,...

This puts the campaign in a temporary state where no new Updates are sent out. This could be useful to debug errors without having to cancel the whole campaign, possibly...

It should be possible to cancel a running Update Campaign. When a campaign is canceled, a Cancel operation is sent on the `OTARequest` interface to all pending targets, and then...