Dear Alex
thank you for the link, i’ll follow next time so i’ll be able to test before.
And finally sorry for all the confusion concerning quantities and these ghost channel configs. i try to explain. i had an old checkout on my computer dating from May that was not in my github local space, and the vvm320 config (vvm320-channel-types.xml) i have edited has been wrongly picked up from there (i really don’t know why,since all my other edits where based in the right tree, just that vvm320-channel-types.xml was picked up in that other old tree). So obviously the commit i provided you back on github was without the edits i had performed on this specific config (thankfully), and that explains your later commit of 5th December to remove channel 43437 since it was obviously not carried inside my own commit. thankfully otherwise that would probably have created a big mess.
All the discrepancies i had found and reported to you were indeed based on this old config of May… So you can ignore all, and big sorry again for all that confusion.
I’m currently testing the new 2.4 bundle, i’ll report back as soon as i’ve verified everything (so far so good!)
@yozik04:
There is some data which is visible in the diplay of NIBE such as the current priority but it is not available via uplink.
There is a special channel I mentioned it a while ago which can be decoded (it is a bitset) and thus you can see if the heatpump is currently idle or cooling or heating or doing hotwater (I believe it has also registers for pool but I do not have one).
thanks @yozik04 for the tip,
now i’m using the new DEV bundle recently compiled by Alex so i get these channels directly, however i didn’t know about the generic “profile/function” thing or capability to link to expire. Very helpful, thank you!
I’m making the fist steps with the Nibe uplink binding, reading values is working fine already. But actually i have a problem with writing values, e.g. changing the state of “Temporary Lux”. I’ve created the following:
Item:
Number TemporaryLuxMode “Temporary Lux Mode [MAP(TemporaryLuxMode.map):%s]” { channel=“nibeuplink:f1155:F1155:hotwater#48132”}
If i set the corresponding parameter on the heatpump itself, i can see in the OH log (and also in the BasicUI) that the value changes from 0 to 1 and remains.
Hi all and Merry Christmas,
Hopefully someone her can help me with tracking, why some values, which my openHAB receives from NIBE uplink, look weird?
I have a fresh VVM325 /F2040-8 installation and could implement the machine into OpenHAB quite easily - thanks to @AlexF !
This set of items from the NIBEuplink binding show unexpected results or behaviours:
1) compressor#44073
The results for the operating time for the Hotwater shift constantly between the value, which is as well shown online (3 hrs), and the Degreminutes of the NIBE system. The log looks like this:
2018-12-25 19:38:37.195 [vent.ItemStateChangedEvent] - NIBE_OPT_HW changed from 3.0 h to -437.6 h
2018-12-25 19:38:37.275 [vent.ItemStateChangedEvent] - NIBE_DEG_MIN changed from -434.40000000000003 °·min to -437.6 °·min
The other counters for two other operating hours (Total and Compressor) do not show this behaviour.
For the Hotwater counter I have made a workaround and read only the max value for this item,as teh Degree Minutes are always negative (so far). However a way to stop this double reading would be better.
2) airsupply#40025, airsupply#40026, airsupply#40075
All these values are reported as -3277 Kw. I would expect some temperature values.
Well, this is indeed weird. Did you define any rules which update the items?
Did you configure via paperui or via files? If you configured via files please post all your nibe related config.
do you have a paid subscription for write access at NibeUplink?
If you have such subscription you should be able to update the values via the official Nibe Uplink app or via web site.
If you do not have such subscription the binding is not able to set the values.
I cannot find any issue in your configuration. I have checked my setup, I have a VVM320+F2040-8, so this is a very similar setup. I cannot reproduce your issues.
The airsupply channels require a air ventilation unit (ERS-XXX). Do you have such installed? But even if there was none installed it should not display wrong values/units.
Hello @AlexF
Thanks for quick reply.
I have indeed no air exchanger installed, so I took these items out now.
I was originally assuming that the device had some sensors in the outdoor unit. It’s a pity, that the documentation on the machines parameters from side of NIBE is kind of sparse. Have all values been reverse engineered?
I rebooted the OpenHab device now and both problems disappeared. The ondulating values in the Operating time vanished and NIBEuplink doesn’t respond to requests for the non existing air sensors.
1000 Tak
Maybe this channel is only used by models which have a outdoor unit, basically all “VVM XXX” models. Maybe there is a equal channel for your model. I have written a tool that logs all possible channels (basically 10000-10500 + 40000-49999) to an excel file once per minute. You could then filter for changes. And of course you could trigger some changes on the Nibe while the logger is active.
I could share my code on github but it is really only a dirty tool.
Hi there, I have Nibe F470 heat pump and trying to bind it to Openhab via Nibe Uplink binding. I can see from the binding documentation this specific model is not supported. However I’m trying to use thing type F750 as it is same kind of product. Let see what happens.
Dear Alex, hope all is good for you your great project and wishing you a fantastic 2019 with continued successes!
little things to say really, first to finally report back that the DEV bundle you compiled for me after my contrib of mid-december has worked like a charm since then, so great, and thanks again.
then i guess you have received this warning from the nibeuplink API webmaster about this forthcoming upgrade end of Jan concerning this upgrade of the Transport Layer Security (TLS). Do you reckon we should do anything on our side to keep all working or it will be transparent?
