Support for Nefit Bosch Compress Hybrid 7000i #560
Comments
|
Could be that we don't have them in our database yet. Can you try |
|
Hello, Had to figure out SU password but found it. Set loglevel to all and retried. Please let me know if you need further info. regards, ems-esp:/$ scan devices |
|
you need to turn logging on first, and then the |
|
Hello First time I did not have logging enabled. Therefore I ran command twice. In between I enabled logging Log all Please check above. Regards, |
|
Did another run for clarity: ems-esp:/# log all |
|
Added also run in debug level: |
|
Are you sure you have connected the heatpump to the same ems-bus? This looks like there is only the boiler (and builtin controller) on the bus, no thermostat, no heatpump. To verify that, can you please post the output of |
|
does look that way doesn't it. @MichaelDvP I'm making some core changes today which should help with debugging |
|
Or it is only the heatpump identifies itself as product-id 123, ver 7.00, there are a lot of boilers using this product-id and it's not much difference controlling a burner or a compressor. |
|
ems-esp:/# read 8 7 I will check how everything is connected tomorrow if possible. I might have to contact the company that installed the equipment. I do see that the thermostat and outdoor sensor cables are going to heatpump now. Originally that was to heater. I looked at the documentation and outdoor unit is connected to canbus connection (Enviline mono block 5KW).. There are 2 EMS bus connectors in heatpump (occording documentation). One EMS (HDI) and normal EMS bus. I expect that from there it connects also to the normal heater (Trendline II). I will check tomorrow and open the heatpump unit. Note: Currently the EMS board is connected to service connector Trendline II. Thanks for support so far. I will try to support you as much as possible. If you need further info regarding equipment or want to debug let me know. |
|
Indeed according to 0x07-telegram there is nothing on the ems-bus but ems-esp, boiler and builtin controller. |
|
Spot on. Old boiler connected On/Off only. No EMS bus. New Heatpump is now recognized but no data available. Parameter 7 for all 3 devices: Heatpump is: Bosch Compress Hybrid 7000i ems-esp:/# read 38 7 ems-esp:/# read 8 7 ems-esp:/# read 10 7 |
|
More detail: (indoor unit) Boiler is Bosch Compress Hybrid 7000i AW |
|
We haven't implemented fully the heat pumps yet as there is little knowledge and data to go with. That's is why it says "no data available". If you could help us by
There might also be some info in the telegram 0xBC (see #309). The UBA Master (boiler) sometimes collects the heatpump data. |
|
I will do that. Also I will start reading on the EMS protocol and decoding and try to find values back.. Just to check, I see lot of CRC messages. Is that because something is not recognized or is there something wrong with communication itself? 000+02:35:09.694 E 359: [telegram] Rx: 80 FA 88 00 E3 00 01 00 01 00 00 00 00 00 00 00 00 01 2E 34 64 55 6F (CRC 6F != 10) |
|
@formadvi Not sure about the Bosch Compress but the related Enviline II unit has the servicejack inside the housing as a cable: |
|
Yesterday when I connected on EMS bus I did see that cable. It did not state its functionality. Tested it and it works like a charm. Picture for further reference, might help future users.
|
|
Logging on device 38 for 5 minutes: Pump is activated. ems-esp:/$ su .... 000+01:08:27.078 N 29: [emsesp] Heat Pump(0x38) -> (0x00), (0xBF), data: 38 C8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ... 000+01:09:47.920 N 34: [emsesp] Heat Pump(0x38) -> Thermostat(0x10), (0x42B), data: 00 C9 07 D8 01 .... 000+01:15:02.047 N 58: [emsesp] Heat Pump(0x38) -> (0x0B), (0x47B), data: 0A 2E 00 61 |
|
Hi, I also have a Nefit Enviline heat pump Tower model, with monoblock aouter unit. |
|
@FWES70 look at the documentation. https://emsesp.github.io/docs/#/ |
|
OK, I watch on 38 for a few minutes, and changed the set temp on the thermostat from 19,0 to 18,0 and later back to 19,0 |
|
@FWES70 what kind of data do you want to capture from the Heat Pump. Setting the thermostat data is on the thermostat so we're reading that anyway. For example in your log above the line |
|
@formadvi the telegram types 0x47B and 0x42B are the ones we need to decipher. The 0x47B doesn't look like it changes so this has probably the configuration settings. And the data from 0x42B like |
|
@proddy yes, i noticed that too. the heat pump is providing a lot of data that I would like to at least read (like boiler temp (different from actual water temp, which is a calculated value); HP modulation %; position of the 3-way valave etc...) . I did a watch on the HP and put it in excel so it is possible to filter. see att. if you prefer the data in another format pse let me know. |
|
sorry for the typo in the name of the attachment: "watch on 8" should be "watch on 38" |
|
@FWES70 the XLS format is really useful, thanks. Except you are actually watching the boiler (8) and not the heatpump (38)! In the WebUI what do you see when you click on the Boiler. Are the values you're after in the boiler data perhaps? Also try and upgrade to the latest 2.1 dev build which shows even more device data. What I'm struggling with is what data is available in the Heat Pump versus the Boiler (Enviline is actually a boiler) |
|
@proddy you're right, it was the boiler. however, I think the boiler is the "heart" of the system. I'll do a watch on 38, let you know/ this is what I see when I click "boiler"": |
|
There will be no data when you click on the Heat Pump or Gateway Module, because we don't capture any. That's the goal of this GitHub issue. I think you'll find all the data you need from your heatpump will be in the Boiler section. |
|
I think so too. in the meantime: here is the data from the HP (38 this time :-)). not so much it seems... |
|
I'll try again to upgrade to V 2.1 tomorrow, so far no success. maybe then it will change. |
the first byte is flags. 0x0B is in binary b1011 so bits 4, 2 and 1 are set. The temps are usually stored in a single byte and multiplied by 2. So the 2nd byte which is 0x33 means 25.5 degrees. |
Device 8 in my case is the indoor unit of the heatpump. The Bosch hybrid 7000i AW. The 7000iAW does not provide warm water functionality. So if it can be identified properly it also should not display values/settings for warm water system it does not contain. |
Thanks. That makes sense. I tried to find in software decoding of the existing messages and want to check those against my unit to see which are actually available. Any idea where I can find this? |
|
001+05:18:54.901 N 15: [emsesp] Heat Pump(0x38) -> Thermostat(0x10), (0x47B), data: 0C 34 00 74 34 = relative air humidity as measured by the thermostat. When air humidity changes it is confirmed that these values change |
|
nice work @formadvi . I'll go an add this to the code (relative air humidity & dew point). It would be interesting if you're seeing these same values in the Thermostat or the Boiler as a lot of data is passed through. While you're at it, could you also do a |
|
@proddy I updated the ems-esp to V2.1 (2_1_0b10). I see more info on the boiler and thermostat. however, when I try a watch Putty crashes after a few seconds. any idea what could be the problem? (sometimes the led on the emsesp flashes just before putty stops, sometimes putty just closes). log works fine it seems |
|
looks like a bug - I made some changes with the watch in b10. I'll take a look. Thanks for reporting! |
|
@FWES70 which watch command were you using? |
|
|
|
it looks like you're using an older build. Did you compile yourself or take from the GitHub firmware branch? |
|
I took it from Github |
|
I am monitoring the other values. BF is not send frequently and only first 2 bytes seem to be populated. Cannot find matching values yet at this point of time. The Thermostat (device 10, CW400) is the controller embedded in heatpump indoor unit. I am monitoring traffic to that controller and there seem to be a lot of telegrams that send data to this device. I will continue to map this traffic. And map to actual values in CW400. This might take some time. Telegrams: 0x2A5, 0x2B9, 0x2F5, 0x201, 0x240, 0x291,0x29B, 0x301, 0x2E0, 0x2EA, 0x61E, 0x267 |
|
I'm working on a new build to fix the watch issue. I'll let you know when its done. Some of those telegrams we already support like 2A* and 2B*. The others in your list I don't know. |
|
I took pictures of the different screens of the HP, and did a watch (shortly) on all. tried to convert hex to dec, but I do not recognize any value... |
|
I found the installation guide for the settings from Nefit, can this help figure out some of the telegrams? |
|
sadly not much info in that PDF I'm afraid. I'm still trying to figure out why ESM-ESP is crashing when watching telegrams in putty. Can you confirm
|
To calculate the dewpoint the temperature is needed, 0074 looks like the outdoor-temperature 11.6°C, |
|
004+03:53:20.763 N 2: [emsesp] Heat Pump(0x38) -> (0x0B), (0x47B), data: 0A 2C 00 61 I am monitoring multiple records over longer period of time to find more matching data. Hope to report more later this week. |
@proddy putty crashes whenever I try a watch (wether raw, or on) for "log" it does not crash. |
|
there is one message that comes in that is causing the crash. most probably an out-of-bounds error where the buffer is overrun (too much data for the allocated storage). it's hard to find and reproduce without using your setup and data. Are you able to compile and build the firmware yourself? I'll need to add some extra debug statements just for you |
|
@FWES70 can you check if this is still happening with the latest 2.1.1 ? |
|
@formadvi are you still seeing discrepancies with the data heat pump data? |
|
No not at this moment. Currently not connected because I need to work on other topics. Will pick up later. |
Hello,
I have a Nefit Bosch Compress Hybrid 7000i in combination with Enviline mono block outside unit.
My boiler and thermostat are shown on the dashboard but not the heatpump unit and outside unit.
Are these supported? If not what would be needed to support those?
Regards
Doc1.pdf
The text was updated successfully, but these errors were encountered: