Bump dataplicity agent to 0.5.13 (fixes 403 for device-gateway devices)#53
Open
alex-mextner wants to merge 1 commit into
Open
Bump dataplicity agent to 0.5.13 (fixes 403 for device-gateway devices)#53alex-mextner wants to merge 1 commit into
alex-mextner wants to merge 1 commit into
Conversation
The pinned 0.4.40 agent talks to the legacy api.dataplicity.com and is rejected (HTTP 403, agent disk-poll/sync fails) for devices provisioned via the new device-gateway API that the integration already uses. 0.5.13 works with the new provisioning. iptool/device_meta were dropped in newer releases, so their compatibility monkey-patches in import_client() are made best-effort.
Owner
|
I don't see any problems with |
|
Hi 
|
Owner
|
I checked it. I'm getting a 403 error on both the old and new versions of Dataplicity. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
After provisioning through the new device-gateway API (the flow this integration already uses, added in #50), the agent fails at runtime:
The device shows up but never comes online.
Cause
The agent is pinned to
dataplicity==0.4.40, which talks to the legacyapi.dataplicity.comand is rejected (403) for devices registered via the new device-gateway provisioning. Thelomond==0.3.3--no-depsinstall workaround is already onmaster, but the agent version itself is the remaining blocker.Fix
dataplicity==0.5.13, which authenticates against the new backend (both thefake_installguard and theasync_process_requirementspin are updated together so the--no-depsinstall path still applies).iptool/device_metawere removed in newerdataplicityreleases, so theimport_client()monkey-patches are made best-effort (try/except ImportError) —dataplicity.client.Clientis still imported normally.No other behavior changes; version bump left to the maintainer.
Testing
HA 2026.5 / Python 3.14, device provisioned via the new API: with
0.4.40the agent logs the 403 above within seconds of each 60s poll; after this change the agent (dataplicity 0.5.13) starts and runs across multiple poll cycles with no 403, and the device comes online.