Skip to content
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

External Temperature Sensors are listed as "This entity is no longer being provided by the danfoss_ally integration." #109

Open
MacKender opened this issue Mar 4, 2024 · 9 comments
Assignees
Labels
bug Something isn't working

Comments

@MacKender
Copy link

Describe the issue

The External Temperature sensor entity for all my Allys are listed as "This entity is no longer being provided by the danfoss_ally integration. If the entity is no longer in use, delete it in settings." I have another test VM running your Ally integration v1.2.1 and it is showing the same,

However -
When checking the Ally API at https://developer.danfoss.com/catalog/danfoss-ally-api/danfoss-allytm-api#tag--device-control there's an attribute named "ext_measured_rs" shown for all my Allys - which I assume is the counterpart to the entity "External Temperature Sensor" in your integration?

Example:
{
"code": "ext_measured_rs",
"value": 2175
},
{
"code": "SetpointChangeSource",
"value": "Externally"
},

The "external sensor temperature" entity stopped working February 27, last seen @ 14:30 hrs (shown by the graph history for the entities).

What version of Home Assistant Core has the issue?

core-2024.2.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Diagnostics information

No response

Anything in the logs that might be useful for us?

No response

Additional information

I tried altering the value for the 'External Sensor via the Ally API
(All identifying values are fake)

curl -X POST "https://api.danfoss.com/ally/devices/bffe273c31bb75be00aa00/commands"
-H "accept: application/json"
-H "authorization: Bearer CADIrXYZBADWGDvFAKE8TZj8gJHb"
-H "content-type: application/json"
-d '{"commands":[{"code":"ext_measured_rs","value":2550}]}'

{"result":true,"t":1709473914801}

If i perform a GET for the same Ally it returns the value I POSTed ('2550') ..but I cannot see any changes in the Ally App for the thermostat so maybe the error is @ Danfoss?

@MacKender MacKender added the bug Something isn't working label Mar 4, 2024
@MTrab
Copy link
Owner

MTrab commented Mar 4, 2024

Which version are you using?
All this shoud be fixed in the latest version

@MacKender
Copy link
Author

Sorry, my main environment is running v1.3.2 of your integration

@MTrab
Copy link
Owner

MTrab commented Mar 4, 2024

Then please add the missing diagnostics information

@MacKender
Copy link
Author

What kind of diagnostics info do you want?

@MTrab
Copy link
Owner

MTrab commented Mar 4, 2024

Click on download diagnostics in the Ally integration

@MacKender
Copy link
Author

MacKender commented Mar 4, 2024

Click on download diagnostics in the Ally integration

There doesn't seem to be a 'Download diagnostics' for the Ally integration in any of my environments (hence me not adding anything in the diagnostics section when submitting the issue). I can find the 'Download diagnostics' option for other integrations but not for any of my HACS integrations (except for HACs itself).

Attached are the ALLY events gathered after I enabled debugging for the integration and then reloaded the integration.

image
Ally_debug_log.txt

@beringtom
Copy link

I had this issue after updating, what worked for me was rebooting the HA instance, and reloading the integration.

@peeweedk
Copy link

@beringtom - Unfortunately that didn't help for me. I really hope this will get fixed soon as this bug makes it quite useless for those who are using external sensors.

@MTrab
Copy link
Owner

MTrab commented Jul 15, 2024

Right now I'm relying on someone that have this setup makes a fix for this, as I have no access to such setup right now.
Also I'm in the process of moving and it'll be quite some time before I even have the time and opportunity to look into this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants