-
-
Notifications
You must be signed in to change notification settings - Fork 96
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
Entity: hpea0 / Heating condensate pan (EA0) does not provide the current status #1598
Comments
This switch was reported in #1415 as telegram 0x48D, offset 3, bit 6. |
What exactly should I enter in the form fields for an individual entity? |
So wait for colder tempertures and check. Or is there a testmenu where you can manual set the output? |
Are there any other possible values that I should log? |
I can't think of any. Maybe there's a Test Function to simulate the switching on/off of the outdoor unit. Those Buderus systems usually come with test like these which the service guys use |
PROBLEM DESCRIPTION
Last year I replaced our Buderus GB142-15 condensing boiler with a split heat pump. This is the Logatherm WLW 166i-10 E (indoor unit) in conjunction with WLW-8 SP AR (outdoor unit). EMS-ESP recognized the new device immediately. I just adjusted the inadequate naming of some entities.
So that the condensation drain on the outdoor unit no longer freezes, I retrofitted the heating cable from Buderus. Unfortunately, the associated entity: hpea0 / condensate pan heater (EA0) remains continuously OFF. In order to be able to check the actual status of the heating cable, I connected a Shelly and was able to determine that it was switched on correctly.
REQUESTED INFORMATION
EXPECTED BEHAVIOUR
The entity should always reflect the actual status of the output.
SCREENSHOTS
ADDITIONAL CONTEXT
Add any other context about the problem here.
For your information, here are the entity names I made
The text was updated successfully, but these errors were encountered: