HD PowerView Binding Issue - openHAB 3.3.0

Add-ons Bindings
21

I’ve also already added the screenshots.

If there are any issues with this please let me know :slight_smile:

Many thanks! :slight_smile:

22

I have already created a PR with a fix of the bug (see below).
@Jeevs the new JAR file is embedded in one of the comments, so can you please test it?

1 Like
23

@AndrewFG Tried the new JAR file and all seems to be working as expected.

I do have automations from openHAB so will wait for them to happen tonight and post back :slight_smile:

Many thanks for getting a fix so quickly! It is most appreciated! :slight_smile:

24

@AndrewFG just a note, I’ve seen this warning in my logs and thought I’d share:

2022-06-28 22:21:26.901 [WARN ] [l.database.ShadeCapabilitiesDatabase] - The 'capabilities:-1' reported by shade 'type:6' don't match the database! => Please request developers to update the database!

Thanks :slight_smile:

25

Good catch. The hub v1 doesn’t report capabilities, which is why they don’t match. But I will find a way to fix the log message in your case.

1 Like
26

Amazing - thank you, look forward to an update :slight_smile:

27

@Jeevs the updated jar is on the same link as before. This should now suppress the logger warning.

1 Like
28

Many thanks will download and report back :slight_smile:

Really appreciate all the effort that has been put in! :heart:

1 Like
29

Hi,

I don’t want ti hijack the thread, but some of my errors look related.

I’ve just upgraded to OH 3.3.0-1 (via apt), and noticed I lost Vane control over my vertical blinds :slightly_frowning_face:

Looking at the startup I see the following message in the logs

The 'tiltAnywhereDetected:true' property actually reported by shade 'type:56' is different than expected from its 'capabilities:4' in the database! => Please request developers to update the database!
The 'tiltAnywhereDetected:true' property actually reported by shade 'type:55' is different than expected from its 'capabilities:4' in the database! => Please request developers to update the database!

And when trying to adjust the vane position, and running a TRACE log, the following appears:

2022-07-06 12:49:20.978 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'BlindsOfficeWindow_Vane' received command 38
2022-07-06 12:49:20.982 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'BlindsOfficeWindow_Vane' predicted to become 38
2022-07-06 12:49:20.988 [TRACE] [rview.internal.HDPowerViewWebTargets] - API command GET http://192.168.10.182/api/shades/20034
2022-07-06 12:49:20.996 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'BlindsOfficeWindow_Vane' changed from 81 to 38
2022-07-06 12:49:21.040 [TRACE] [rview.internal.HDPowerViewWebTargets] - JSON response = {"shade":{"id":20034,"type":55,"capabilities":4,"batteryKind":3,"smartPowerSupply":{"status":0,"id":0,"port":0},"batteryStatus":3,"batteryStrength":146,"roomId":39451,"name":"T2ZmaWNlIFdpbmRvdw==","groupId":39348,"firmware":{"revi
sion":1,"subRevision":8,"build":1944},"motor":{"revision":2,"subRevision":1,"build":0},"positions":{"posKind2":3,"position2":26565,"posKind1":1,"position1":26963},"signalStrength":4}}
2022-07-06 12:49:21.042 [TRACE] [powerview.internal.api.ShadePosition] - setPosition(): capabilities=Vertical (4), coords=VANE_TILT_POSITION, percent=38
2022-07-06 12:49:21.044 [TRACE] [rview.internal.HDPowerViewWebTargets] - API command PUT http://192.168.10.182/api/shades/20034
2022-07-06 12:49:21.045 [TRACE] [rview.internal.HDPowerViewWebTargets] - JSON command = {"shade":{"positions":{"posKind1":1,"position1":26963,"posKind2":3,"position2":26565}}}
2022-07-06 12:49:22.729 [TRACE] [rview.internal.HDPowerViewWebTargets] - JSON response = {"shade":{"id":20034,"type":55,"capabilities":4,"batteryKind":3,"smartPowerSupply":{"status":0,"id":0,"port":0},"batteryStatus":3,"batteryStrength":146,"roomId":39451,"name":"T2ZmaWNlIFdpbmRvdw==","groupId":39348,"firmware":{"revi
sion":1,"subRevision":8,"build":1944},"motor":{"revision":2,"subRevision":1,"build":0},"positions":{"posKind1":1,"position1":26963,"posKind2":3,"position2":26565},"signalStrength":4}}
2022-07-06 12:49:22.741 [TRACE] [powerview.internal.api.ShadePosition] - getState(): capabilities=Vertical (4), coords=PRIMARY_POSITION => result=59
2022-07-06 12:49:22.747 [TRACE] [powerview.internal.api.ShadePosition] - getState(): capabilities=Vertical (4), coords=VANE_TILT_POSITION => result=81
2022-07-06 12:49:22.751 [TRACE] [powerview.internal.api.ShadePosition] - getState(): capabilities=Vertical (4), coords=SECONDARY_POSITION => result=UNDEF
2022-07-06 12:49:22.759 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'BlindsOfficeWindow_Vane' changed from 38 to 81

Adjusting the vane position from within the PowerView app still works as expected.

Any idea what is causing this?

Side note: I noticed that the Signal Strength is expected to be a number, but shows as a string “excellent”, is this a hidden transformation, or a bug?

Thanks in advance for taking a look, and the fine binding :slight_smile:

^ Marcus

30

Many thanks for reporting this. I will study your logs, and get back asap with a solution.

31

:+1: thanks! Let me know if you want me to test anything, or supply API output. I am happy to help.

32

How/where do you see this? It must be a feature, since the system signal strength channel type is used. I have a Number item configured, and it shows as a number in a sitemap.

33

I suspect this must be some transformation in the UI then. Though I have no clue where or how this is applied :face_with_raised_eyebrow:

This is how my main ui looks like:

image
image1293×1610 111 KB

I’ve just checked the CLI for the item status, and indeed its a number:

openhab> openhab:status BlindsSideWindow_SignalStrength
4
34

Now I’m also wondering, because I see this:

Screenshot_2022-07-11-08-03-11-60_40deb401b9ffe8e1df2f1cc5ba480b12
Screenshot_2022-07-11-08-03-11-60_40deb401b9ffe8e1df2f1cc5ba480b121080×1961 91.3 KB

35

Looks like a bit of magic in the OpenHAB core, which applies to channels of type signal-strength.

I notice your item is a point instead of a measurement of level, does that change the representation on your side?

Doing the digging, I now also start to wonder why I don’t have the command channel on my shades :sweat_smile:

1 Like
36

Did you install any snapshot/milestone versions during 3.3? This was a breaking change within that milestone:

In this case you probably need to recreate your thing (if managed).

1 Like
37

Ah, yes, deleting and recreating a shade thing does make the command channel show up.

I however did not run any snapshot or milestone versions during the 3.3 release. I’ve installed the binding while on 3.2.0-1, tested my blinds (and confirmed the vane was working), and days after, the 3.3.0-1 release came out to which I upgraded.

38

Thanks, one more thing to be aware of as long as we don’t have an automated migration mechanism for managed things after changes in thing definitions. While this one is not breaking, it’s certainly annoying having to recreate things in order to discover new channels.

39

@AndrewFG is there any way to downgrade to the older binding version? I’d happily trade the new command channels for vane control :sweat_smile:

40

I really don’t understand your question. What kind of vane control are you missing? What has changed for you from prior versions? What new command channels are you talking about? What actually are you asking for? What type of shades do you have?