Closed arfoll closed 7 months ago
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!
(message by CodeOwnersMention)
vicare documentation vicare source (message by IssueLinks)
Did you just create the client? There were other users with the same issue but it got resolved by time.
I guess it was ~1h ago. I also saw such reports, will try again tomorrow and see if I get lucky.
On March 19, 2024 8:12:10 PM GMT+01:00, Christopher Fenner @.***> wrote:
Did you just create the client? There were other users with the same issue but it got resolved by time.
-- Reply to this email directly or view it on GitHub: https://github.com/home-assistant/core/issues/113830#issuecomment-2007937237 You are receiving this because you authored the thread.
Message ID: @.***>
Maybe we should add this to the docs.
Working as expected - took ~12hrs for the token to work. Sorry for the noise.
The problem
Can't manage to authenticate to viessmann backend. My token is generated as per the instructions:
I'm using the flow on my smartphone that has the vicare app installed and working correctly. There is a vitoconnect OPTO2 with a Vitocal 200-S connected and working. Just using the default flow from either my pixel6 (as per instructions) or from the laptop results in an authentification error but seemingly not much more detail
What version of Home Assistant Core has the issue?
core-2024.3.0
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
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
I've never had this configured or working before so the "one client" messages are rather odd. My account is new from today as I only just installed the OPTO2.