Devices do not show up (room sensor, floor heating) #112009
Comments
|
Hey there @CFenner, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) vicare documentation |
|
Great that you're testing the dev version. What do you expect to see, what sensors do your devices expose? Sharing the diagnostics would be helpful. I think at least room sensors are not that difficult to add. |
|
I added a PR to expose the room sensor, but I have no hardware to test this. If you would be so kind, we could make it to the march release with this. |
|
Hi, Thank you for the really fast answer :) For the floor thermostat, it's a bit more complicated since I believe PyViCare doesn't support it yet, and I'm not really surprised given I'm one of the few, if not the first to use it in France... So I guess it's not widely sold in germany either. I just tried the PR and I did get 2 new entities for one of the room sensor, but I suppose they should be added as separated device since they can be in different room.
Please find attached the diagnostics and the logs. config_entry-vicare-8059c83839f26cf125fdf59a4fc0b0f8.json |
|
😭 due to the way entities get their id, the room sensors overwrite each other. For historical reasons the gateway serial is used as identifier and not the device serial. In PyViCare there is a radiator actuator, could that be a floor heating? What you uploaded is just the log, the diagnostics file can be downloaded from a vicare device in HA when you click on the |
|
It's two different product, but the end goal is pretty much to do the same when you have a floor heating/cooling. |
|
Isn't the json file I uploaded the diagnostics?
Or it's something else I don't see on mobile?
|
|
@home-assistant rename Devices do not show up (room sensor, floor heating) |
home-assistant
bot
changed the title
|
Hi, i am completely new to HA, but i know my way aroud in a terminal. I have a Vicare Setup with a 252a heatpump (with integrated low power Radio), 8 rooms and 12 radiator thermostats. If i can help with testing something let me know. |
|
Device serial for room sensor is now exposed with openviess/PyViCare#369 (release pending), floor heating is still pending openviess/PyViCare#362. |
|
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
|
This is not stale. |
|
Unique id issue was solved (almost) in Feel free to test @Roguyt @solbadguy2010 |
|
I can confirm the PR 125243 added the support for room sensor (in conjunction with the PR to fix the serial handling). |
|
@solbadguy2010 I have a PR ready to implement TRV support: #127348 Would you mind testing this..? |
|
Sorry, just yesterday reactivated my heatpump and i also deleted my HA Pi. Need to reinstall :-) will test asap |
|
@CFenner can i help testing? I have a vitocal 20 heatpump with 18 room climate sensors in my house. I also want to use the integration with the room sensors. Advanced API is activated in Viessmann dev portal. Do i have to install a dev version of the integration to test the feature? At the moment i only see my heatpump with 28 entities in the main Home Assistant 2024.10.3 release. |
|
@schoysi-p so the room sensor PR is already merged and will be available in the November release. You could try to use the PR script, to load the PR content to your system and test. |
|
Oh dear, 18 sensors, so with the current implementation your update rate will drop from once per minute to once per 20 minute... |
|
yeah, new limits are 3000 API calls per day with the paid version of the API. |
|
Yes, I can see the Temperature and Humidity entities for my TRVs and Climate Sensors. The TRVs don't show up as Thermostats, though. I suppose that is on purpose for now.
|
TRV != Floor Heating |
You can argue as much as you want, but to me it's still a different API. |
|
Thanks for the awesome work on this @CFenner! Higly appreciated! Please keep up the good work, you are as far as nobody else integrating the (almost) closed Viessmann eco-system in a smart home! Thanks for that! Do you have a BuyMeACoffee or similar? May I ask a question what is the plan of releasing TRVs and the temperature sensors into the official integration? So far I only see my heatpump, which is great already, however the TRVs would hit the spot! Also what is the chance of (besides the setTemperature API) you know anything "partially official" about whether at some point in time functions like "setWindowOpenForce" (see here) will be supported? I really would like to connect my window sensors, instead of the thermostats "guessing" if a window is open or not. That would be an awesome goal!! Thanks for your reply! :) |
TRVs and Climare Sensors are already in the official integration. But you need to subscribe to the Premium API to see them. Unfortunately, the Premium API is way too expensive and doesn‘t rectify the price to get TRVs and Climate Sensors. I‘m pretty sure the reasoning behind this is the fact that polling and reacting with the room components would quickly exceed the Basic API request limits.
as you notice, it is already possible to do this in both z2m and ZHA when connected directly to Zigbee.
send me a PM about this if you want to know more. It is possible, “unofficially”.😉 |
|
Hello @ckpt-martin thank you so much for the detailed answer. It is very hard do find condensed information in the ViCare / Viessmann eco-sphere, so your post summarizes it on point! This is really helpful to anyone starting to look into integrating ViCare / Viessmann into their smart home! Thanks a ton for your effort! 💯
This connects the dots! I recently also contributed in the ViCare Community (sorry German only) "complaining" about this fact, I somehow thought reading about it in this issue & in the official HA integration documentation that this "limitation" was somehow circumvented in the HA integration. Thanks for pointing out that this is actually not the case unfortunately. This means the integration still will be only partially useful by many many community members, as, as you said, the high price of the premium Viessmann APIs makes it essentially impossible to justify the possible savings you gain from a better API access. That is a huge bummer. I stand by my point I posted in the Viessmann community: I think Viessmann has to introduce a (much cheaper) "Smart Home" API plan, in order to make integrations like this viable for the general public. Thanks for your work on this anyways @CFenner and @ckpt-martin!
Agreed, however, as I think many "regular users", I don't know if I am ready yet to "go down that rabbit hole"... I think to make this work reliably it needs a lot of tinkering, and to explain to my wife, that she should now start using a different app, that has half of the features the Viessmann app provides will be a "challenging discussion" grin In the end it is also somehow a huge waste in resources to essentially try to re-implement what the Viessmann app already provides. A "hybrid" solution (ViCare + Smart Home where useful) would be the most optimal solution, however I understand that Viessmann "ties" our hands here. :/ Maybe as one suggestion to @CFenner, shall this information "ViCare Thermostats and Sensors will not become visible if not subscribing to the premium API" be included in the official integration readme? I was "waiting" for the Thermostats to appear, because of this comment in the documentation:
Then I thought, "ok maybe it is not yet in the public version of HA", which is why I then started to look into this issue. So I think many end-users would maybe face the same and adding this as a "Important" info box in the HA integration description, would maybe also increase the pressure a little bit towards Viessmann to maybe do some things about it / adding a new API plan for us end-users.
I will definitely follow-up on that offer @ckpt-martin thanks! 👍 |
Can you tell me how to remove the custom integration and revert back to official? |
There is a PR for TRVs temperature control, that needs to be tested (help needed)!
@ckpt-martin this could be mitigated on PyViCare side (see openviess/PyViCare#431), we could fetch all device values via the connected gateway instead and dramatically reduce the API calls for TRV / Room Sensor scenarios.
@kristian yes, we should add this limitation here https://github.com/home-assistant/home-assistant.io/blob/current/source/_integrations/vicare.markdown
You're welcome, I'm building on a great foundation from others (PyViCare). However, sponsor links are now on my GH profile page 😉 🍻 |
Run the command again, and you should see a description how to remove it in the console output. Basically just remove the |
Sure, let me come up with a PR for this! Appreciated 👍
Appreciation was already sent your way! 🥇 Thanks a lot! |
|
@CFenner I created a PR, please let me know in case you would like to see any changes on the wording 👍 home-assistant/home-assistant.io#36176 |
If you want I have a house with 9 or so TRV valve to test it with. But if it also depends on the paid API, we will need to find someone else since it's a different Viessmann account (my father's).
Making noises, as a customer, or as a Viessmann Proactif does nothing. It's a political issue with Viessmann Germany not being competent enough to figure out the monetization schema for the rest of Europe. You know the issues I had with getting access to the paid API, getting shadowbanned and then being unbanned 9 months later. |
|
But back on the main topic, I think we can now close and merge the Room Sensor PR, I've been using it for a little bit over 2 months, and it works perfectly fine in the limitation of the Viessmann API. |
Shouldn't you be able to do by adding the room sensor to the vicare room ? |
Oh thats great! Just to be clear, we're talking about #127348, right? I’m wating for feedback on that PR to hand it in for review as I cannot test myself. |
that statement related to using the Zigbee binding capability when the TRV is connected via Zigbee to my Smarthome. Viessmann have removed capability that was available in the reference TRV from Danfoss so it will only be able to control the TRVs using external temp sensors within the ViCare world. Unfortunately ViCare does not utilize the Zigbee binding capability, but rather has built the logic into the cloud. This is also probably the reason my TRVs do not work correctly in rooms with external sensors if for some reason internet connectivity is disrupted. I had such a case where my internet was down for 4 hours and in the rooms with external sensors the TRVs just kept their open or closed state that they had before the disruption. So, some rooms cooled down while others just kept getting warmer. The TRVs apparently receive a command over one of the Zigbee attributes that disables the operation via the internal temp sensors within the TRV and will only change state when the cloud tells it to. |
|
hi all,
greeetings, |
|
@14656ADF16 You also have a subscription to the advanced api that you can read the thermostats value via the API? I would have an implementation for the TRVs ready, that needs testing: #127348 |
|
Good question,
I have login for the Viessmann API but it wasn’t what I was hoping for, so I haven’t revisited that. I will check and let you know.
Regards
Nick
Von: Christopher Fenner ***@***.***>
Gesendet: Tuesday, 21 January 2025 11:37
An: home-assistant/core ***@***.***>
Cc: 14656ADF16 ***@***.***>; Mention ***@***.***>
Betreff: Re: [home-assistant/core] Devices do not show up (room sensor, floor heating) (Issue #112009)
@14656ADF16 <https://github.com/14656ADF16> You also have a subscription to the advanced api that you can read the thermostats value via the API?
I would have an implementation for the TRVs ready, that needs testing: #127348 <#127348>
—
Reply to this email directly, view it on GitHub <#112009 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOMW5PUTJLMTXFF2OXEZIXT2LYPLDAVCNFSM6AAAAABECUPGNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBUGM2DEMZYGI> .
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
hi again, does this screenshot give the info you are looking for regarding API subscription?
|
You are in the free „Basic“ API Tier. If you want to get access to your thermostats, the only option Viessmann provides, is to upgrade to their „Advanced“ API Tier package for 20€ per month:
Any cheaper option doesn‘t provide any access to your smart home / ViCare appliances, other than your heatpump / boiler. |
|
Hmmm... that's expensive! |
|
Someone who said who works at Viessmann joined the Discord and stated this. 
So at least there is something at the horizon... |
Yes… I don‘t see any argument that could justify the price. Please also see my comment here:
|
Oh, wow! That‘d be some good news. Any idea what „device data“ and / or regulation they could be referring to? |
|
Just signed up for the free trial month of the Advanced API. The status of the floor thermostat and its outputs doesn't show up yet. For my information (and no, I didn't plough through the small print) - I assume the HA integration is pulling the data from a Viessmann server, not direct from the controller of my heating system? (Apologies for being so poorly informed.) How are the TRVs and floor thermostat communicating via the Viessmann "low power radio" in the heatpump's indoor unit, is that Zigbee or similar? |
The Viessmann eco-system is unfortunately completely closed and not locally accessible (these are all issue the community is complaining about). Meaning communication to the thermostats requires internet & connection with the Viessmann servers / API in any case. While the thermostats are using Zigbee Pro / IoT to communicate, Viessmann requires the use of their propriatary Viessmann Vitoconnect / Optolink Interface, which acts as a Zigbee hub. As Vitoconnect doesn‘t provide any possibility for local access or interfering with the thermostat communication, the „Advanced“ API is currently the only way to connect with the thermostats, which is a huge bummer. Especially because it blocks any kind of home automation efforts, for example connecting the thermostats to window sensors and / or third party temperature sensors. Eventhough Viessmann doesn‘t even provide own window sensors to begin with. |
|
For anybody interested in getting the same info you get in the ViCare App for free without the need of a premium subscription, check out my implementation which emulates the ViCare App when connecting to the ViCare Cloud. It‘s not a HA „Integration“ as such, but a way to script accessing the ViCare Cloud exactly the same as the App does it. |
|
@14656ADF16 great that you tried the trial! Integration of the TRVs is in principal ready but untested. It would be really helpful, if you could test that state. Maybe we can talk on #127348 about it. The floor heating is working a bit different, I think. That could take some time to implement. Anyhow, feel free to ping me (Hafenstrand) on discord for faster feedback cycles. If the trial period ends, you may need to contact the support, that they activate the free api again. I think I had some issues with my api client after I tried. |
The problem
I've been toying with the dev version of HA to try to make my HomeAssistant show all of my ViCare sensors and connected stuff.
I do see the device in the diagnostics as well as the debug log, but I can't get them to display in my HomeAssistant.
If it helps, I'm on the paid plan and my Viessmann installation is the following:
I do see them all on the debug, but not in the generated devices and entities :(
What version of Home Assistant Core has the issue?
core-2024.4.0.dev20240301
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
config_entry-vicare-1e69f700c2d474ca5937934ae2726753 (1).json
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: