Hi,
I see that the F2120 is not supported currently, but what would be the steps to support it? Or could I just try with some other configuration and hope they are similar?
Cheers,
Andres
Hi,
I see that the F2120 is not supported currently, but what would be the steps to support it? Or could I just try with some other configuration and hope they are similar?
Cheers,
Andres
Hi you could try another model which is similar to yours.
Hey Alex,
I find a error (Version: org.openhab.binding.nibeuplink-2.4.0-SNAPSHOT):
The response of nibeuplink:f750:id123:compressor#43123 is 12 Hz.
The real value is 120 Hz.
Hi,
channel 43122:
The Openhab value 2 Hz.
I think the original nibe value must be 20 Hz.
Yes, the scaling is wrong.
I have fixed this, could you try the latest version?
Hi Alex,
yes, you fixed it! The new version works great.
Thank you
Hi there Alex,
Iāve noticed that the channel base#10012 does not work. Iām using it on a F1145 but i think it does not matter since it is defined in a common group of channels for all models.
Iāve put the log in DEBUG on and i think i found a possible culprit: Although the channel is defined as ābase#10012ā, the channel that gets updated is like it used to be in a former version ācompressor#10012ā.
Here the log i get:
2018-11-19 15:35:35.960 [DEBUG] [k.internal.model.GenericDataResponse] - Channel 10012 updated to: 0 (no)
...
...
2018-11-19 15:35:36.036 [DEBUG] [ternal.model.DataResponseTransformer] - Channel compressor#10012 transformed to OnOffType (0)
...
...
2018-11-19 15:35:36.683 [DEBUG] [nibeuplink.handler.UplinkBaseHandler] - Channel is to be updated: compressor#10012: OFF
It would be great if you could check
thanks!
PS: i forgot to say that iām using the last version i found on the server, i.e. 2.4.0.201811031309
openhab> bundle:list | grep NibeUplink
119 ā Active ā 80 ā 2.4.0.201811031309 ā NibeUplink Binding
fixed it.
ā> https://github.com/openhab/openhab2-addons/pull/4252
As soon as this is merged it will be part of the official 2.4.0-SNAPSHOT build.
thank you Alex
i take the opportunity before this next build is generated, could you please add these channels in the F1145 config that are still missing. i really think they are very very relevant to an F1145:
i repeat them again here:
40015 Number Ā°C /10 EB100-EP14-BT10 Brine In Temperature
40016 Number Ā°C /10 EB100-EP14-BT11 Brine Out Temperature
43439 Number % EP14-GP2 Brine Pump Status EP14 (Brine Pump Speed)
43437 Number % Supply Pump Speed EP14 (Climate supply water pump)
44270 Number Ā°C /10 Calculated Cooling Supply Temperature S1 (equivalent of general#43009 but for cooling as opposed to heating)
43103 Number HPAC state (state of the HPAC cooling accessory)
the three first (40015, 40016 and 43439) are to monitor the brine system which is where the heat comes from in an F1145 setup (the underground geothermal pipe is called the brine), the fourth one (43437) is to monitor the heat supply and i see you have already put it in the VVM310 / VVM 500 and VVM320 / VVM325 configs, but it would be also needed in the F1145 config at least.
Then then 5th (44270) is the equivalent of the base#43009 bit for the cooling mode of operation (43009 is for heating, 44270 is for cooling). Again you have put it in the VVM310 / VVM 500 and VVM320 / VVM325 configs but it would be needed as well in the F1145 config.
then the last one (43103) is also very useful (at least) for an F1145 to know how the connected HPAC should be operating (e.g. free cooling, active cooling, heating, etc) as there is no other way to distinguish for instance between active and passive cooling. I think also the use of an HPAC with an F1145 is very common, so monitoring the HPAC state is very relevant.
for each one iāve provided you in the table the scaling to apply (and the corresponding dimension unit after the scaling is applied). A blank is the column following the unit column means no scaling should be applied.
please tell me if you have anything against putting these in the F1145 config and iāll not bother you with this anymore!
thanks
I have seen you requested these channels already a few months before. Well I missed this, somehow.
I will add the channels but as this is not a fix but additional functionality I am in doubt that those changes will be included in the official 2.4.0 version.
Also this requires several files including documentation to be changed this takes more than 10 minutesā¦
Finally it should be tested before getting this integrated into the master.
BR
Alex
Hi again Alex, i understand
just wanted to tell you i would be more than happy to contribute directly on GitHub if you wish in order to spare you some effort after all what youāve done, or even if it can help getting these changes in before the official release (btw, hoorray to you!). I think iāve understood the principle of the configuration (as well as the documentation) and would mostly need your guidance to know in which group you would like each of these parameters to be assigned (e.g. the common ābaseā group, or the specific F1145/F1155 group, etc).
Iāve already contributed on github so I could proceed as i did in the past (clone the master, apply some changes, and create a pull request with the changes that you can then review before merge). Obviously i could also support the test.
please let me know!
Hi,
I canāt get any values from the binding. In paperUI I se that the binding are logging in and then I get a communication error. After that the binding logs in again and I get a communication error again. This goes on forever. I could have done something wrong, I donāt knew what.
Iām using serialnumber for the nibeId, I suppose that is correct?
Iām running this version
2.4.0.201811211702
Openhab version is 2.3 and iām trying to acces my F750
OpenHab log file shows this i Debug mode:
2018-11-21 21:30:44.679 [DEBUG] [ing.nibeuplink.handler.UplinkPolling] - polling NibeUplink org.openhab.binding.nibeuplink.config.NibeUplinkConfiguration@7621309d[user=xx,password=xx,nibeId=xx,pollingInterval=60,houseKeepingInterval=3600,asyncTimeout=120,syncTimeout=120,customChannel01=0,customChannel02=0,customChannel03=0,customChannel04=0,customChannel05=0,customChannel06=0,customChannel07=0,customChannel08=0]
2018-11-21 21:30:44.938 [DEBUG] [llback.AbstractUplinkCommandCallback] - received content, length: 136
2018-11-21 21:30:44.940 [DEBUG] [llback.AbstractUplinkCommandCallback] - HTTP response 302
2018-11-21 21:30:44.940 [DEBUG] [llback.AbstractUplinkCommandCallback] - onComplete()
2018-11-21 21:30:49.997 [DEBUG] [llback.AbstractUplinkCommandCallback] - received content, length: 130
2018-11-21 21:30:49.999 [DEBUG] [llback.AbstractUplinkCommandCallback] - HTTP response 302
2018-11-21 21:30:54.943 [DEBUG] [llback.AbstractUplinkCommandCallback] - received content, length: 136
2018-11-21 21:30:54.945 [DEBUG] [llback.AbstractUplinkCommandCallback] - HTTP response 302
2018-11-21 21:30:54.946 [DEBUG] [llback.AbstractUplinkCommandCallback] - onComplete()
Events log file shows this in Debug mode:
2018-11-21 21:30:20.016 [hingStatusInfoChangedEvent] - 'nibeuplink:f750:7db6ee82' changed from OFFLINE (COMMUNICATION_ERROR): Found to ONLINE: logged in
2018-11-21 21:30:24.892 [hingStatusInfoChangedEvent] - 'nibeuplink:f750:7db6ee82' changed from ONLINE: logged in to OFFLINE (COMMUNICATION_ERROR): Found
2018-11-21 21:30:30.064 [hingStatusInfoChangedEvent] - 'nibeuplink:f750:7db6ee82' changed from OFFLINE (COMMUNICATION_ERROR): Found to ONLINE: logged in
2018-11-21 21:30:44.942 [hingStatusInfoChangedEvent] - 'nibeuplink:f750:7db6ee82' changed from ONLINE: logged in to OFFLINE (COMMUNICATION_ERROR): Found
2018-11-21 21:30:50.001 [hingStatusInfoChangedEvent] - 'nibeuplink:f750:7db6ee82' changed from OFFLINE (COMMUNICATION_ERROR): Found to ONLINE: logged in
2018-11-21 21:30:54.948 [hingStatusInfoChangedEvent] - 'nibeuplink:f750:7db6ee82' changed from ONLINE: logged in to OFFLINE (COMMUNICATION_ERROR): Found
2018-11-21 21:31:00.177 [hingStatusInfoChangedEvent] - 'nibeuplink:f750:7db6ee82' changed from OFFLINE (COMMUNICATION_ERROR): Found to ONLINE: logged in
2018-11-21 21:31:05.135 [hingStatusInfoChangedEvent] - 'nibeuplink:f750:7db6ee82' changed from ONLINE: logged in to OFFLINE (COMMUNICATION_ERROR): Found
2018-11-21 21:31:10.108 [hingStatusInfoChangedEvent] - 'nibeuplink:f750:7db6ee82' changed from OFFLINE (COMMUNICATION_ERROR): Found to ONLINE: logged in
2018-11-21 21:31:15.207 [hingStatusInfoChangedEvent] - 'nibeuplink:f750:7db6ee82' changed from ONLINE: logged in to OFFLINE (COMMUNICATION_ERROR): Found
It would be great if someone could check what could be wrong
thanks!
Most likely your NibeId is wrong. I tried a wrong NibeId and could reproduce this behaviour.
Hi,
Iāve checked the serial number, itās correct. Iāve deleted my system at Nibe Uplink and created it again just too be sure Iām using correct serial number. Iāve created a new user at Nibe Uplink with only manager security level too be sure that the security level doesnāt fool me. Iāve deleted my Nibe system in my iOS app and connected it again.
When I added my system in the iOS app and on the Nibe Uplink web page I had to write the connection string in a field. Is there not a field for this in Nibe Uplink Binding?
Iām really lost here
Thanks in advance
Hm, I think that my Linux system or my OpenHab installation are somewhat ābrokenā!
I tried to add a binding for my Neato robot and guess what I can see in my logs
2018-11-22 19:55:38.598 [hingStatusInfoChangedEvent] - 'neato:vacuumcleaner:OPS09517-506583DEA870' changed from OFFLINE (COMMUNICATION_ERROR) to ONLINE
2018-11-22 19:55:38.599 [hingStatusInfoChangedEvent] - 'neato:vacuumcleaner:OPS09517-506583DEA870' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR)
2018-11-22 19:55:39.213 [hingStatusInfoChangedEvent] - 'neato:vacuumcleaner:OPS09517-506583DEA870' changed from OFFLINE (COMMUNICATION_ERROR) to ONLINE
2018-11-22 19:55:39.215 [hingStatusInfoChangedEvent] - 'neato:vacuumcleaner:OPS09517-506583DEA870' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR)
2018-11-22 19:55:40.433 [hingStatusInfoChangedEvent] - 'neato:vacuumcleaner:OPS09517-506583DEA870' changed from OFFLINE (COMMUNICATION_ERROR) to ONLINE
2018-11-22 19:55:40.434 [hingStatusInfoChangedEvent] - 'neato:vacuumcleaner:OPS09517-506583DEA870' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR)
It doesnāt help me but I donāt think the problem is related to the Nibe Uplink binding. Iām sorry for the inconvenience.
Hi Olivier,
I would suggest to put the three brine channels into group compressor, the other should be put into general. Group base is only for common channels which are available to all models.
BR Alex
Hi Alex
indeed that makes a lot of sense, but maybe a quick comment concerning #44270 and #43437. i see they are available in both the VVM310/VVM500 and VVM320/VVM325 models, and they are also available in F1145, so they are good candidates for the base group as they are very likely common to all models being directly related to heat supply. I see also that the parameter #43009 which is equivalent to #44270 (equivalent for the heating temperature target as opposed to the cooling temperature target) is already in the base group, so it could make more sense puting 44270 here as well.
The thing is that if going that way i would then need to remove these two parameters from VVM310/VVM500 and VVM320/VVM325 (currently in group general for these models), but no problem i could do that as well and could highlight this change in the change record for everyone to be aware.
what do you think?
Hi Olivier,
cooling is not supported by the F7XX models. Hence it does not make much sense to put #44270 into the base group because cooling is a model specific feature.
#43437 is indeed available at least for model F750 so I guess it is a general channel. You could put it into the base group then.
BR
Alex
[edit typo corrected F1155 -> F1245]
Hi Alex, ok fully clear, will do as you advised, to sum up:
F1145/F1245 config:
40015, 40016, 43439 --> compressor,
44270 and 43103 --> general
base: add 43437
VVM310/VVM500 and VVM320/VVM325 configs:
remove general#43437
talk soon when done