Not sure, if all parameters are available from uplink.
I already tested it and Nibe uplink came back with more than 5000 parameter values when I requested 10000 - 99999. So I guess it is all available although it is not documented anywhere.
Unfortunately the Modbus manager database does not know the F2025. Is that a new model? Maybe it will be added to the database at a later point of time.
Actually, it may be too old then. It is basically a 2020 with minor enhancements. Oh well, I might install the binding and see what I get with VVM310 data. Cheers!
If the F2020 supports Nibe Uplink I just need a mapping of channel IDs.
You could login to Nibe Uplink and use for example Firebug to analyze the JSON responses to the periodic POST requests. It will return pairs of keys (Nibe IDs) and values (actual sensor data) to be displayed in the WEB-UI.
Of course the WEB-UI offers only a small subset of sensor data but I think that is the most relevant data.
Cool!
How should I format it, and which data do you actually want?
For example, the heat pump compressor hours has ID44071 (and gives me 10904 hours). The title text is ācompressor operating time EB101ā.
Hereās anyway the data. But let me know if I miss something, or shall reformat!
(I see now, that I actually has a F2026, not 2025, as I wrote first. But they are very similar anyway!)
status
ID44396,charge pump speed EB101
ID44362,outdoor temp. EB101-BT28
compressor module
ID10014,blocked
ID44071,compressor operating time EB101
ID44073,compressor operating time hot water EB101
ID44069,compressor starts EB101
ID44058,condenser out EB101-BT12
ID44363,evaporator EB101-BT16
ID44059,hot gas EB101-BT14
ID44060,liquid line EB101-BT15
ID44055,return temp. EB101-BT3
ID44061,suction gas EB101-BT17
info
Title Value
ID0, product F2026-8
ID44014,version EB101
the F2026 is the outdoor unit belonging to your VVM310? In that case all data should be retrieved by the VVM310. Outdoor units are not handled seperately.
Aha! Yes, this is the outdoor unit - and it looks like all the IDās are supported, as you say, through the 310.
Is there a jar somewhere? Iām on 2.10 release still will it work or does it need 2.2? (I am considering upgrading to 2.2, so if this is needed for this binding, Iāll do this).
first of all thanks for your efforts Alex and also the others earlier. This thread is actually the reason Iāve registered here.
I wanted to try the jar youāve uploaded a few days ago, but could not get it working with my F1155 as openhab always claimed no binding would support that thing.
After having a look at your code I saw that in the SUPPORTED_THING_TYPES_UIDS enumerator in NibeUplinkBindingConstants.java you only listed the VVM320.
Is there a particular reason for it? (maybe the only one thatās currently supported & tested?)
Would be really great if you could add the others as well and build a new jar.
The new build works on my side for the F1155 as well, but Iām getting similar warnings as Henrik does.
Apparently there are 15 IDs defined as number for my heat pump as well which should be Strings.
Iāve listed them here, would be great if you could adjust it at some point in time.
Thanks, but I still have the same issue.
I think the problem is within the defintion of the channels. (Iāve seen the ids are still defined as doubles)
