MyUplink binding?

Add-ons Bindings
101

Hi everyone,
Previously, when I was using the NibeUplink binding, I had access to the 43084 channel, which showed the current power usage of the electrical add-on heater for my F750. However, after switching to the MyUplink binding, it seems that this channel is no longer available.

I’d greatly appreciate any advice or suggestions on how to access this information with the new binding.

Thanks in advance!

102

I miss this channel too, it seems it’s completely removed by Nibe (you cannot see those values on the my uplink website either). The only hope to get this added is to contact Nibe, but I guess it would require a firmware update to enable it.

1 Like
103

Thanks for the information @pacive

104

Same here for VVM320. Since my electricial add-on heater is limited to the minimum power I do not really need this as you can get the active status from other channels, too.

BTW: The binding is now merged and will be part of openHAB 4.3.0. It is already included in the latest milstone 4.3.0.M5

3 Likes
105

Nope. OH3 has reached end of life and this binding contains a lot of code that requires Java 17 or later while OH3 is based on an older version of JAVA. This would require some efforts I am not willing to spend.

You could either upgrade to the latest milstone build 4.3.0.M5 which already contains the new binding or you could use the 4.2.4-SNAPSHOT version which should be compatible with any 4.2.x release.

106

I just updated to 4.3.M5 and installed the binding from the distribution, but I noticed some channels were not created that I had before. The parameters are still there when querying the API, but no channels are created for them. Did something change in the logic there during the PR approval?

One possible cause is that of the 4 channels I noticed are missing 3 of them haven’t a unit ("parameterUnit": ""), and one have seconds for the unit ("parameterUnit": "s").

Edit: Never mind, they had just ended up as “advanced” channels, since the statically defined channel-types is set to be that. Is there a particular reason for that?
For the parameter with unit s I believe there’s a bug though, the binding only sets channel type time if the unit is h. I can prepare a PR for that.

107

Hi @AlexF,

im updated to 4.3.0 stable and the input error with negative numbers still occurs.

Log:

2024-12-21 15:27:00.684 [WARN ] [link.internal.connector.WebInterface] - command execution ended with exception:

org.openhab.binding.myuplink.internal.model.ValidationException: channel (40940) could not be updated due to a validation error

	at org.openhab.binding.myuplink.internal.command.AbstractWriteCommand.prepareRequest(AbstractWriteCommand.java:133) ~[bundleFile:?]

	at org.openhab.binding.myuplink.internal.command.AbstractCommand.performAction(AbstractCommand.java:289) ~[bundleFile:?]

	at org.openhab.binding.myuplink.internal.connector.WebInterface$WebRequestExecutor.executeCommand(WebInterface.java:241) ~[bundleFile:?]

	at org.openhab.binding.myuplink.internal.connector.WebInterface$WebRequestExecutor.run(WebInterface.java:192) [bundleFile:?]

	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?]

	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [?:?]

	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [?:?]

	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]

	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]

	at java.lang.Thread.run(Thread.java:840) [?:?]
108

Well channel “40940” does not allow negative numbers.
Channel “command” was changed to accept also negative numbers.
At the moment for all other channels a default validation rule is applied which is

[0-9]+

A later version could define more specific validation but that would cause quite a lot of effort. A quick fix could of course also be less restrictive but still generic like this one:

-?[0-9]+(\.[0-9])?
1 Like
109

Hi,
specific question regarding the REST API, after updating to latest FW for VVM320E:

Do you still get values for 47737 (ventilation/fan setting)?
If I query via Swagger UI and /v2/devices/{deviceId}/points the json content does not contain 47737 any more as it did before.
Using /v3/ also didn’t help.

BTW: Setting this value via PATCH still works. But how to retrieve/get this setting?
(The setting is still shown correctly with the myUplink app via menu 1.3.3, Fan schedule 1: activated or not activated - radio button. Means there is a possibility to get the value via API)

Any hint appreciated :slight_smile: