-
Notifications
You must be signed in to change notification settings - Fork 22
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
Register 7, 8, 9 #57
Comments
I do not have the app (Airwell has an issue at their side an say they are working on it) and also do not have a electrical heating element for DHW. So I am afraid that I am not able to test it right now |
So maybe wait to confirm by others before implemented it ;) -I left decision for you ;) if yes I prepare pull req. ;), No we wait ;) |
I've tested today this. After enabling in heatpump controller (unfortunetly this is only available on heatpump itself -not via modbus -for officially registers) than after switch on Forced Water Tank Heating and Forced Tank Buffer Heater working as expected, also when this is set by Mobile app smart home these values are set and don't revert after few seconds and on original controller there also icon showing that heater is enabled. PS. for parameters 210 I see in york sm that bits 6, 8 and 14 could be read/only... -but I'm not sure -so i think we wait to see if time shows true ;) |
Add pull request for setting Forced Electrical Heater for these Registers: 7, 8, 9 ? or we wait to future request from users? |
Yeah this is a bit of a difficult one. That logic that happens is, of course, implemented in the heatpump self and the goal of this ESPHome config is not to replace the logic in the heatpump, but to be an addition to it. That is for example the main reason why I think that automations should not be implemented in this ESPHome config, but should be done for example in Home Assistant if a user wants that. |
;) and with ESPHome itself it isn't so easy make all checks and restrictions with conjuction with other registers ... unfortunetelly |
the one for register 9 is interesting here. However I want to disable AHS outside the boundaries of the ranch.
both have a range from -15 to 10. (I think both default to -5, this is a question in the yaml) I actually only want to rely on, I think, So it might would make sense to be able to turn it off, once turned on. I know the logic should be done by the controller, but those settings are actually limited. |
OK. So this min value could be manufacturer depended value... |
Hi
In SM these registers are configurable. I don't have any heater to force it -maybe something must be also set in config to be working ;)
Can you try look what happens when you "force DHW heating" or "fast DHW" in Smart Home mobile app -this option enables electrical heater in DHW and it changes Register 7 value from 0 to 1, but in my case after few seconds it is disabled.
In Modbus register description in York there is info that 0 is invalid, 1 = Forced On, and 2 = Forced Off... but from mobile Smart Home App values are 0 or 1 and never have 2.
If moved this (and also register 8 and 9) to switch than the code looks like this (and we can ignore off value in this check except write_lambda -but it can be assumed as 0 means off not value 2):
The text was updated successfully, but these errors were encountered: