-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
Smart grid option #69
Comments
I think it is possible within the P1/P2 protocol, and it is on my todo-list; I purchased an BRP069A61 to see to what extent this can be done via P1/P2, but this will take some time. I hope P1/P2 enables for more precise control than is possible via the SG relay inputs. |
Maybe the hints on this side will help you further: https://community.openhab.org/t/how-to-integrate-daikin-altherma-lt-heat-pump/16488/14 I use the BRP069A61 with a shelly that closes the pins and I send HTTP Request to the BRP069A61 with the form data to change the value the allowed power consupmtion. This is a bit hacky, but it works. |
And the P1/P2 wires already run into my house, so saves me some new cabling as wireless connection near/inside the heatpump is hard. I might look into your suggestions as well @bausi2k Main purpose for now is to start heating the boiler water when te sun is high. To prevent my solar pannels to drop out due to too high voltage on the main 😄 . I need some consumes and this seems like a useful one. |
For that case, the BRP069A61 works like a charm. Even if you have a static value for the allowed consumption eg. 3500W the heat-pump takes the power and heats up the boiler(if room buffering is disabled) to the max allowed temperature(60degrees Celsius in my example) event though the desired temperature is only set to 47°C. |
@bausi2k Would you mind to share the needed HTTP request? My LAN adapter always runs into issues after power loss, it is a hazzle to get it running again. Many thanks in advance :) |
Find the complete HTML file attached and in the code section is the form data.
|
@nicx this may take some time as other things are higher priority (HA integration and COP calculation). But why would you prefer the backup heater over the more efficient heat pump? |
good question, i have also thought about this: i have considered that it might be more gentle for the compressor, especially in the summer months, if it does not only start briefly for the hot water heating. in my case, the hot water is heated to 45 degrees per default, which takes approx. 1h. in case of pv surplus i switch the smart grid contact, the hot water is then heated up to 55 degrees. this again takes about 1h. this would mean 2 compressor starts per day, which could be saved by using the heating rod. out of the belly, the heating rod is wear-free, but the compressor is not. maybe the compressor will last a few years longer this way?! ;) oh and with pv surplus the efficiency is rather secondary I think. |
As far as I know, you can only tell the heatpump to do it's work with a defined amount of power in kWh.
|
True, though 30 starts/day is not uncommon in winter due to defrosts, so I would personally not worry about 2 starts/day for DHW.
I guess that depends on your personal goals and local electricity pricing. |
I will monitor that in the upcoming winter which is my first one ;) My Goal would be to have as minimum compressor starts as possible. so in best case its 1 and the heat pump ist just running all day (for heating my house). |
With the BRP06(whatever) you have full control about when and how long your heatpump runs, so you can optimise that. Defrosting is another issue of course… My heatpump is controlled by Loxone, because ist is much easier and also more energy efficient. I don't see any reason why my hp should run at 3am in autumn at moderate temperature… |
@Arnold-n another thought: i could switch the heating rod on and off more often, and depending on the pv surplus, i could also let it run for a short time. i could imagine that the compressor prefers it to run for a minimum time at startup and not to clock. it wouldn't matter to the heating rod, which could also be switched on every 5 minutes, for example. |
Hi @bausi2k , |
@Th301
for details on NodeRed Integration find this thread & post |
Any updates on this @Arnold-n? Anything a fellow dev could help with? I've got ESPAltherma hooked up to my EHVH11SU26CB6W but what I really want to do is do whatever it is the LAN adapter does to handle a PWM signal to adjust the power usage of the heatpump. We have a 5kW cap on our export and on sunnier days are regularly hitting that so would be nice to have a gentle way to soak up the extra head into our DHW. Since the LAN adapter supposedly can do this via PWM and my heatpump is apparently compatible with the BRP, I'm hoping there could be a way to do the same thing via your little module when hooked up to my RPI5 home assistant :) |
Still on my activity list, for now the only power limiting option is to use the quiet levels which also limit the maximum power consumption. |
Although I only did a quick manual test so far, I would like to add my thoughts about the differences between quiet mode and power limiting as I am not only interested in this because of solar power management, but also to improve efficiency. If my heatpump draws full 2kW for water heating I observe a massive drop of the average heat exchanger temperature on the outside unit. This is of course not surprising, but it also reduces the COP as the unit has to work against a larger temperature difference. I expect that in a situation when time is not critical, slowly heating the water at 1kW or less would lead to a higher COP when the heat exchanger is not cooled down that much and can maintain a higher temperature. In the release notes for v0.9.46 you mention that the quiet mode actually has a better efficiency then the default mode, which you attribute to lower power consumption of the fan. I suspect that it is actually due to the heat exchanger not being cooled down so much and the reduced fan speed would actually be counter productive here. So, if time is not an issue and if you are not concerned about noise, running the fan at max, but heating only at 50% (i.e. power limiting instead of quiet mode) might actually be even more efficient. (Disclaimer: These are the thoughts of a physicists with a Carnot process in mind. Some insights by an engineer or just some experience from someone who tested this more systematically are very welcome :) ) |
Fantastic info, thanks. Can't wait to find some time (and good weather conditions) to compare with my system. Have been thinking about using 24h average as well. (But then we would be leaving the original topic of this issue.) |
@Arnold-n many thanks for the HA and COP integration! :) Now I think we can go back to the origin topic question: Is the smart grid control still on your list? any idea when it will be implemented. This feature would be the last missing feature to completely get rid of my ESPaltherma which I have running in parallel to P1P2MQTT ;) PS: sorry if I am annoying ;) I love your project! keep up your great work :) |
You're welcome, thanks! Smart grid release is still (and high) on the agenda, but cannot predict yet when. |
Hi together, is there an update on this? 😇 |
Hope to provide this in October! |
Has your heatpump a setting to support 24-hour averaging of outside temperature?
|
See e.g. 9.B.3 [1-0A]. |
Out of curiosity, will it be possible to support the same settings which are possible with the Dakin Home Hub EKRHH? The device has an extensive set of registers accessible by modbus. It looks like this is what is needed for this ticket, even better than the BRP069A61. |
As far as I know the average value is not communicated over P1/P2. If the outside temperature is within the weather-dependent range points, it can be calculated from the current LWT setpoint. I plan to add temperature averaging in the code anyway. |
Plan is to something similar indeed. It seems the EKRHH implements SG more direct, if I understand correctly it adds a dynamic power limitation via modbus registers 57/58, whereas the BRP069A61 calculates from the E_meter input what the power limitation should be. However availability of the EKRHH is still very limited. |
In addition, register 1 (inlet temperature) looks very promising to me because it allows to dynamically limit the heating to what is needed or do rooms heat buffering even if you do not have a Daikin room thermostat. |
Depending on the operation mode (LWT absolute or weather-dependent) it is already possible from HA to control power indirectly via the LWT setpoint resp. LWT deviation setpoint. The power is then determined by flow and difference with return temperature; the latter may be influenced by other factors depending on your heating system. |
Does your Modul work with EKRHH? I thought it is not working? I have EKRHH working (Modbus-Mode), if you need to try something I would be happy to help. |
Thanks! The bridge does not communicate with EKRHH, so EKRHH and the P1P2MQTT bridge will both act as auxiliary controller. I expect that when LWT is set from either that the last value will remain active. Would be interesting to see how dynamic power limitation is communicated in the P1/P2 traffic, so a log of P1P2/R# while hex data output is activated ('J3') and power limitations are changed over Modbus would be very useful. |
The msg suggests the EKRHH gets another ID than 0xF0/0xF1/0xFF. I need to modify the code a bit to get rid of these but I would need a bit more info, can you either run v0.9.56rc1 and look at the msgs again, or have a look at the hex data packet 00xx31/40xx31 where xx deviates from 0xF0/0xF1/0xFF which triggers these messages? As for the power meter, I think it is one of the ways the EKRHH can do power limitation, but instead of a meter input signal I think you can also write the power limit directly to the modbus register (58 or 1002, not sure which). |
I tried v0.9.56rc1. It is still the same msg. In attachment there is the hex log. |
Thanks! The msg is slightly more informative, and the hex log is even more useful. The EKRHH takes auxiliary controller address 0xF2. I'll provide you with an updated firmware tomorrow that can keep history of the 0x31/0x32 messages. |
P1P2MQTT-bridge v0.9.56rc2 gets rid of the error messages and can inform you about changes in the 0x31 and in the new 0x32 packet from/to the EKRHH in topics like |
Hi Arnold, it works now. log p1p2 modbus 58 (general power limit).txt Here is the log for Power limit (Modbus 57) ( I changed values to 19, 18, 17, 16, 17, 18, 19, 20) Here I found out some error msgs |
There is no change in this values: On the heatpump it was changes because the modbus register shows the new values. |
Many thanks! Seems packet 0x32 is surprisingly meaningless. The EKRHH seems to use (previously unseen) parameter numbers 0x0093-0x00A0 and 0x0194-0x0195 in packet type 35, but these are mostly 0 all the time. The only parameter which matches your system changes is 0x0094 which seems to communicate the general power limit (with 0.5kW resolution, in u16div2 notation). New P1P2MQTT-bridge firmware v0.9.57 should resolve all errors above and will output various SG related entities in subdevice HC_SG, perhaps one of these will show up to change during your experiments. |
Hi Arnold, I installed v0.9.57 but in HomeAssistant I don't get values (even if I change) (I changed SG Mode Value and And Limit for "Empfohlen Ein") when I changed "General Power Limit" new sensors appeared: After time a lot of more Sensors appeard, but still all unavailable In Teminal I get: Here is the HEX Logfile were I change SG Mode from 0 to 3 to 0 to 3 to 2 to 0 (I am not sure if previous log was correct) |
Long Log: From that log I found out that this: repeats 6 times and is related to SG Mode: 3
this log should be SG Mode 2 (but not 100% sure)
log related to SG Mode 0 not found the times are related to the actual changes with modbus (I made the log larger to filter out other stuff) I changed in total 6 times in the order SG Mode 3, SG Mode 2, SG Mode 0 This is also somehow related but I can't interpret it:
|
I just uploaded v0.9.58rc2 which should now really fix the errors/unavailability of the SG entities and should make analysis easier... I have not yet renamed the info above to make a SG-mode entity, it is still called SG_Q_35-0195. In the messages above, the message 00F235 9501 01 encodes in packet type 35 that the single-byte parameter nr 0195 has changed to 01. |
I just installed 0.9.58 and got the SC sensors. Am I right that this is the current dev state and I cannot set the SG ready state yet? |
@Arnold-n could you perhaps give me a very short yes/no answer? :) |
Sorry, slipped through, indeed currently SG control paramters can only be set via the cryptic E command and not yet from HA, for example setting limit parameter 94 in packet 35 to 19kW can be done with E35009426 (0x26=38, 38/2=19). I think "127" means "no limit" - to be verified. Confusingly there were 2 entities with the same name |
@Arnold-n Changes in Modbus 57 (Leistungsbegrenz während Empfohlen Ein / Pufferung) are not displayed in HC_SG |
Thanks, I'll try to look into the others. |
This suggests that 5 is not a power limit but a status? |
@Arnold-n no I don't think so. As far as I understand the sensor value "HC_SG SG_35_0093-General_Power_Limit_Active_Q" is directly reflecting the Smart Grid mode (free running = 0; recommended on = 1). after smart grid mode is switched tn "recommended on", the Daikin itself decides when to start extra heating. That's why the value "5" is set a little bit later in the sensors "HC_SG SG_35_0094-General_Power_Limit_kW" and "HC_SG SG_General_Power_Limit_ 2". This is exactly the time when the Daikin decides to start the extra heating. |
@Arnold-n I is there a chance that this work via the P1P2 adapter? |
Our Daikin heatpump has two relays for smart grid connectivity.
I am not sure if this is even within the protocol, but could this project support the smart grid features as well?
The text was updated successfully, but these errors were encountered: