search

elupus / hass_nibe

Home Assistant Nibe Uplink Integration
185 stars 54 forks source link

[question] Fetching parameters and controlling heatpump via modbus #54

Closed yozik04 closed 4 years ago

yozik04 commented 4 years ago

I am trying to get rid of my openhab2 system and use hass as my main system. Openhab has a binding Nibe Heatpump Binding which I am currently using. It uses Modbus connection and an Arduino with Ethernet Shield. All this is way more stable than Nibe Uplink. I am using it for a half a year now. Controlling heating/cooling temperature offsets, water comfort modes, reading all parameters that I need, enabling/disabling heating and cooling for FREE.

Does it make sense to try to change current project to support second communication method or it is better to create a separate project? I am ready to contribute.

runevad commented 4 years ago

I used this (husdata.se) before and it was excellent, I still have the card lying around here somewhere but not plugged in anymore. It also uses MODBUS and was rock solid. It fetched almost all the parameters I wanted (at the time I didn't get the parameters for electricity price and a few others, not sure these can be reached through MODBUS or not) and I used it in combination with MQTT to sent the parameters to Home Assistant.

I might be interested in using MODBUS again just to have a fail safe and be a little less dependent on the nibe cloud.

elupus commented 4 years ago

You guys should have a look at: https://github.com/bebben88/NibePi Seems like neat solution. No integration for home assistant yet. Mostly standalone. But post a note on his issue page. Link back here :)

yozik04 commented 4 years ago

I have started writing a python library to work with nibegw, but it is stuck now due to lack of free time. Probably when COVID will end I will have time again to continue.

DenisMir commented 3 years ago

@yozik04 Did you went on with writing this python library?

yozik04 commented 3 years ago

No. I did not. Feel free to do it :)

elupus commented 3 years ago

I might if i end up building a nibepi hardware. But its just a might :)

yozik04 commented 3 years ago

I would not go via RPI hardware. Arduino with a netmodule or ESP module would be much better so it would handle sending acks back to Nibe by itself. It can be powered via Nibe heatpump. On the other side would be RPI or any other thing that would communicate with Arduino/ESP to query data it is interested in. This way if you reboot RPI your heatpump will not go into alarm state.

elupus commented 3 years ago

The nibepi hardware is powered by the pump. But sure it's rather pointless to have all that power. Would be nicer to just have a nibe to tcp modbus gateway as an esphome hardware. Then it could act identically to the new S series pumps.

I even think I have all the hardware lying around. Just not the time.

yozik04 commented 3 years ago

New S series pumps have TCP Modbus exposed?

elupus commented 3 years ago

New S series pumps have TCP Modbus exposed?

Yup

yozik04 commented 3 years ago

So this is the way to go for sure =)

DenisMir commented 3 years ago

I have gone the easy way now (at least for me since I am no Python guy at all). I'm running a Prodino MKR Zero Ethernet with NibeGW. (powered by the F1255) The client side is NibePI (which has a NibeGW client) and is running inside a simple homeassistant addon. It is collecting the NibeGWs UDP data and publishes it via MQTT as well as it allows to write data via MQTT the other way round.

yozik04 commented 2 years ago

@DenisMir I have pushed a Nibe modbus library today. Works with NibeGW developed for Openhab. https://github.com/yozik04/nibe I think it has all required parts to get started. It should be plug and play replacement for Openhab's nibeheatpump integration. I will start implementing MQTT version of the integration next week.