-
Notifications
You must be signed in to change notification settings - Fork 50
Fix devices request in Tado X for 0.18.x #183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
in Tado X, the serial number is in the "serialNumber" field, "shortSerialNo" was the field in Tado V3
Could we release a |
@wmalgadey @erwindouna could you maybe take a look at this? This is essentially only a backport from master (https://github.com/wmalgadey/PyTado/tree/master/PyTado/interface/api/hops_tado.py#L76), no big changes. Unfortunately, without this fix the
|
Looks good to me. Would this also be Home Assistant compatible? |
@erwindouna Yes, I tested the changes both with tado V3 and tado X (latter of which of course still doesn't work in HA without any further changes). It is also compatible with the patches from last year for rudimentary tado X support in the HA core integration, which I updated based on your OAuth changes: https://github.com/karlbeecken/ha-core/tree/tado-oauth-deviceflow/homeassistant/components/tado |
Hey, thanks for working on this karlbeecken! |
Has this been merged down now with the new release or do we still need the custom component? |
I have the same question, made upgrade 2025.4 and not working integration. Error: Logger: homeassistant.components.tado.coordinator Unexpected error fetching tado data I have only Tado X. |
@wmalgadey can we bring this in, along with: #189? |
Downloading https://github.com/karlbeecken/ha-core/tree/tado-oauth-deviceflow/homeassistant/components/tado as custom_component and reinstalling Tado integration did not work also. |
Solved copying contents of inside (followed this instructions: https://community.home-assistant.io/t/guide-transfer-files-to-components-folder/413272) |
it should have been merged already to support/0.18. I will check, why this is not working anymore. |
@erwindouna and @jgpazos70 the change got somehow reverted in 0.18.x I just made the change again an will create a 0.18.12 to be used in HA again |
@wmalgadey I am not sure, but it seems you reverted the fix again? 😅 |
I am confused! where did the error from jgpazos70 commented 2 days ago did come from? which version was used there? I will implement the solution from current master branch, it should be compatible in either way. |
@karlbeecken I just pushed the current implementation of tadox from master to support/0.18, bevor I create another useless release, would somebody mind taking a test here with this version? |
I think that might be because HA didn't bump to the latest release yet? If I recall correctly, they are still on 0.18.9 for HA 2025.4. I can test with the current 0.18 branch in the evening. |
A RP to merge in version 0.18.11 has been approved and will be added shortly. |
@wmalgadey I just tested latest from the 0.18 branch, works with Tado X and V3. |
Ok, will release it as 0.18.13 |
Description
in Tado X, the serial number is in the
serialNumber
field,shortSerialNo
was the field in Tado V3. This breaks API interaction with Tado X setups, because theserialNo
field doesn't existRelated Issues
none
Type of Changes
Mark the type of changes included in this pull request:
Checklist
Additional Notes
Would be awesome if this could be merged soon, it is a requirement to make the temporary fix for the Tado X HA integration work again with the new OAuth flow.
Thank you for your contribution to PyTado! 🎉