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

Unable to change temperature with ViCare TRVs #133577

Open
enke5 opened this issue Dec 19, 2024 · 5 comments · May be fixed by #127348
Open

Unable to change temperature with ViCare TRVs #133577

enke5 opened this issue Dec 19, 2024 · 5 comments · May be fixed by #127348

Comments

@enke5
Copy link

enke5 commented Dec 19, 2024

The problem

Hi,

I am trying to add my vicare components into home assistant to do some automation. I have expected that I will be able to set the target temperatures of my ViCare thermostats, as I have a developer subscription to the ViCare API.
Unfortunately, the thermostats show up as sensors only. Is this a bug, or is the feature missing?
Another observation: The ids of the thermostats do not show. There are also entries in the debug log, that device.serial datapoint was not offered.

Can you please have a look at this? Thanks in advance. I appreciate your efforts a lot.

Best wishes,
Andreas

What version of Home Assistant Core has the issue?

core-2024.12.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

vicare

Link to integration documentation on our website

https://www.home-assistant.io/integrations/vicare/

Diagnostics information

home-assistant_vicare_2024-12-19T13-41-36.000Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

Hey there @CFenner, mind taking a look at this issue as it has been labeled with an integration (vicare) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of vicare can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign vicare Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


vicare documentation
vicare source
(message by IssueLinks)

@CFenner
Copy link
Contributor

CFenner commented Dec 19, 2024

Hey @enke5, you're right, this feature is missing but ready to be tested for quite a while. As I do not have a thermostat and could not find anyone to test this, it is not merged yet.

#127348

It would be great if you could try this. You can do so by running this in there terminal in HA:

curl -o- -L https://gist.githubusercontent.com/bdraco/43f8043cb04b9838383fd71353e99b18/raw/core_integration_pr | bash /dev/stdin -d vicare -p 127348

Regarding the device issue I will have a look, thanks for reporting.

@CFenner
Copy link
Contributor

CFenner commented Dec 19, 2024

@enke5 please share also your diagnostics file.

@CFenner CFenner mentioned this issue Dec 19, 2024
19 tasks
@CFenner
Copy link
Contributor

CFenner commented Dec 19, 2024

Serial issue will be fixed with #133619

@CFenner
Copy link
Contributor

CFenner commented Dec 19, 2024

@home-assistant rename Unable to change temperature with ViCare TRVs

@home-assistant home-assistant bot changed the title Vicare thermostats are only sensors, serial not available - even with developer account Unable to change temperature with ViCare TRVs Dec 19, 2024
@CFenner CFenner linked a pull request Dec 19, 2024 that will close this issue
19 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants