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

Missing sensor MK1? (question) #285

Open
sshknoll opened this issue Oct 13, 2024 · 12 comments
Open

Missing sensor MK1? (question) #285

sshknoll opened this issue Oct 13, 2024 · 12 comments
Assignees
Labels
todo issue ready to implement

Comments

@sshknoll
Copy link

Hi everyone,

first of thank you very much for the work you are putting into this project! :)

I recently installed the integration in HomeAssistant and it works quite well. What I am missing is the sensor values for MK1 mixing circuit (MK1 target and current). Are these deliberately not included or am I missing something here?

Thanks for any hints on that!

@toggm
Copy link

toggm commented Oct 18, 2024

Same problem here. Tried to add them manually, but without any luck:

- platform: luxtronik2
  sensors:
   - group: calculations
     id: ID_WEB_Temperatur_TFB1
     friendly_name: Mischkreis1-Vorlauf
     icon: mdi:thermometer
   - group: calculations
     id: ID_WEB_Temperatur_TFB2
     friendly_name: Mischkreis2-Vorlauf
     icon: mdi:thermometer
   - group: calculations
     id: ID_WEB_Sollwert_TVL_MK1
     friendly_name: Mischkreis1 VL-Soll
     icon: mdi:thermometer
   - group: calculations
     id: ID_WEB_Sollwert_TVL_MK2
     friendly_name: Mischkreis2 VL-Soll
     icon: mdi:thermometer

@sshknoll
Copy link
Author

As far as I understand, there is no use trying to add sensors anymore. Latest version doesn’t support Yaml config anymore.

There is a workaround by using the old plugin by Bouni in parallel.

But I was wondering if these sensors were intentionally left out.

@Mehli12
Copy link

Mehli12 commented Oct 19, 2024

Try to find this in the hidden entities.

Bildschirmfoto 2024-10-19 um 11 45 44

@sshknoll
Copy link
Author

Thanks, but I have already done that. There is no hidden entity that matches MK1 Temperature, only the curves for MK2 and MK3 can be accessed - not even their current temperatures.
If an MK1 sensor existed, wouldn't it show up under hidden sensors, by the way?

Bildschirmfoto 2024-10-19 um 17 41 53 Bildschirmfoto 2024-10-19 um 17 42 53

@Mehli12
Copy link

Mehli12 commented Oct 19, 2024

In my installation the MK1 = Heizkurve 1 = Heizkurve of the heat pump was directly discovered by the integration. MK2 is in my case for the curve for my floor heating. I don't use another curve because I have just 2 heating circuits. (heat pump it self and floor heating)

@toggm
Copy link

toggm commented Oct 20, 2024

I only see those values regarding the measured temperatures:
image

MK2 is only available to define the "Heizkurve" and is a static value over time:
image

What I'm missing are those:
image

Defined here as:
image

@sshknoll
Copy link
Author

Thank you for pointing that out with the screenshots. That's exactly what I am looking for! Any way to implement that. I'd be happy to help if somebody pointed me toward a way to do so. (which files?)

@toggm
Copy link

toggm commented Oct 21, 2024

Wild guess would be to add a descriptor of those flags to https://github.com/BenPru/luxtronik/blob/main/custom_components/luxtronik/sensor_entities_predefined.py#L74

But didn't try it out yet...

@macrauder
Copy link

+1 Same behavior in my installation MK1 is missing

@Plobli
Copy link

Plobli commented Oct 28, 2024

For me, MK1 is called in Home Assistant heating curve 1 (Heizkurve 1) and is displayed. I only have an MK1 in the cooling area in the integration.

@toggm
Copy link

toggm commented Oct 28, 2024

@Plobli But that's the "Heizkurve", which means the configuration of it and not the measured temperatur

@Firetribe
Copy link
Contributor

I have the same issue... cannot add the mk1 or mk1_target, I don't have the entities. Would be nice to have to make sure I don't heat up my storage tank instead of the floors...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
todo issue ready to implement
Projects
None yet
Development

No branches or pull requests

7 participants