Vesa Ruohomäki

Hi! I just received my [LilyGo T-CAN485](https://github.com/Xinyuan-LilyGO/T-CAN485) board today. As a fresh Home Assistant user and absolute first timer for ESP32, I found this step by step. I will record...

So I did select some items with ModbusManager and updated the LOG.SET file to the heat pump as instructed in the Nibe MODBUS 40 manual. As a point of focus,...

I had 7 sensors enabled, 3 of them were somehow enabled by "default" or automatically when I installed the integration. Now I dropped it to three, only the phase currents...

Nibe MODBUS 40 manual says "ModbusManager can be downloaded via www.nibe.se/kommunikation". That takes you to a page, where you can find menu PROFFSHJÄLP (Professional help) -> KOMMUNIKATION -> NIBE Modbus....

Nothing fishy in ESPHome DEBUG logs as far as I understand. Setting logging to VERY_VERBOSE was too much for the ESP to handle, the heat pump went to alarm state....

I actually did make another LOG.SET with only those three currents to try, did not help. Now I left logging not activated and even selected "Ignore LOG.SET" in the heat...

Logging was already dropped to VERBOSE, now at DEBUG (little difference between VERBOSE and DEBUG). OK, I also made an empty LOG.SET file. Seems to be disabled now, although it...

Confirmed. I also added 32 bit degree minutes, and that draws a nice, continuous graph. Phase current values are often unavailable. LOG.SET is now empty.

@elupus, any ideas on where this issue (some 32 bit values being constantly ok and some constantly not) might originate? Heat pump, NibeGW, configuration, something else? In other words, is...

@tobbensoft Yeah... My specific interest are just the phase current values (which are now broken) and with high update frequency (which is not the case now) :( This way I...