Drayton Wiser Thermostat Binding

Use the previous version of the binding :+1:

Good advice. There is a bug in the latest version that causes the binding to tie up all of the handlers which affects not only itself but can impact on other bindings too. In my case, it stopped Astro and Network from working.

Can someone help me to get my thermostat humidity to show.

Everything else works fine I have an entry is my items file as;

Number:Humidity Landing_humidity “Humidity [%.0f %%]” (GF_Landing) [“Humidity”] {channel=“draytonwiser:room:HeatHub:Landing:currentHumidity”}
and it appears as a channel in PaperUI for both the room Landing and Landing Thermostat however when I go to make a link there is no entry for anything relating to humidity.

Thanks

Hello everybody,

I want to combine the windowsensor with the wiser-system. I’m looking for an funktion oder methode to set the Setpoint down if the window is open (status= false) and reset to the normal value if the window is closed (status=true).

KR

Kevin

I have a Number item that looks the same as yours.
Number downstairs_humidity “Downstairs Humidity [%.0f %%]” [“Humidity”] {channel=“draytonwiser:room:HeatHub:downstairs:currentHumidity”}

This is what I see in PaperUI.

Although I use text configuration, I often copy the channel reference from PaperUI

Hi All
Hope that this is useful as I managed to get the hub secret without leaving the sofa or changing the hub to an AP or rooting my phone. I installed Packet Capture from the Play Store. Run it with the play1 button at the top and select the Wiser Heat app. Then launch the Wiser App. Go back to the Packet capture and click stop. when you inspect the packets you will find the secret in the GET request.

I saved the request to a file copied it to the PC and then did a cut and paste of the secret into the binding configuration, instantly worked.

I have the same problem. Open HAB was installed in the last week, on the surface all looks well, but I noticed several times when I have walked past the Wiser Hub, it was RED. It is certainly related to the OH being connected. Before I started using OH I had never seen the hub go RED except when the router was being rebooted.

I am wondering if the hub gets defensive when a message exchange does not complete in time and OH is not responding quickly enough and so goes off line and resets the WIFI, this give rise to the entries in the log.

2020-05-25 22:07:11.776 [hingStatusInfoChangedEvent] - 'draytonwiser:room:WiserHeat02851D:hall' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
2020-05-25 22:07:11.781 [hingStatusInfoChangedEvent] - 'draytonwiser:boiler-controller:WiserHeat02851D:controller' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
2020-05-25 22:07:11.784 [hingStatusInfoChangedEvent] - 'draytonwiser:itrv:WiserHeat02851D:90FD9FFFFEC37F74' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
2020-05-25 22:07:11.787 [hingStatusInfoChangedEvent] - 'draytonwiser:hotwater:WiserHeat02851D:controller' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE

Mine still does this I am almost at point of giving up with Open HAB. Drayton Wiser binding was the only reason for selecting OpenHAB. It is a shame that this great work seems to have not quite crossed the finish line for some.

In order for the binding being merged I made some changes to the binding code and also reorganized some of it’s internals to be a bit more robust. The kar file can be found here: https://github.com/Hilbrand/openhab-addons/releases/tag/draytonwiser You can drop the file in the addons folder to test. If you will test it I can work on any issues to get the binding completed.

Thanks for the reply, I will drop the code in tonight and run it up over the next few days and keep an eye on the Wiser hub to see if it has improved.

I dropped in the new kar file to see if it would improve the “red-lighting” of the heathub.

With the new kar file just getting cast errors instead.

Openhab v2.5.5
Wiser binding v2.5.6.202006102129

Have switched back for now

Thank you for your help on this.

Thanks for testing. I fixed the issue and uploaded a new kar file.

No Problem happy to help if it gets the job done.

Loaded a fresh openhabian onto a SD card last night so the start is clean for today. I used the kar file i downloaded yesterday as a starting point. I will download the latest and use that once I have checked everything is there on this clean install, no other bindings will be added.

Observations on binding-draytonwiser - 2.5.6.SNAPSHOT so far:

  1. The hub was detected but the search for things was not automatic as before
  2. Before I had even had chance to manually add things this is in the event log
2020-06-12 11:09:48.128 [hingStatusInfoChangedEvent] - 'draytonwiser:heathub:WiserHeat02851D' changed from UNINITIALIZED (HANDLER_CONFIGURATION_PENDING) to INITIALIZING
2020-06-12 11:09:48.213 [hingStatusInfoChangedEvent] - 'draytonwiser:heathub:WiserHeat02851D' changed from INITIALIZING to UNKNOWN
2020-06-12 11:09:49.942 [hingStatusInfoChangedEvent] - 'draytonwiser:heathub:WiserHeat02851D' changed from UNKNOWN to ONLINE
2020-06-12 11:09:49.948 [me.event.ThingUpdatedEvent] - Thing 'draytonwiser:heathub:WiserHeat02851D' has been updated.
2020-06-12 11:20:16.002 [hingStatusInfoChangedEvent] - 'draytonwiser:boiler-controller:92516180' changed from UNINITIALIZED to INITIALIZING
2020-06-12 11:20:16.035 [hingStatusInfoChangedEvent] - 'draytonwiser:boiler-controller:92516180' changed from INITIALIZING to UNKNOWN
2020-06-12 11:20:16.162 [hingStatusInfoChangedEvent] - 'draytonwiser:heathub:WiserHeat02851D' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Cannot cast org.eclipse.smarthome.core.thing.internal.ThingImpl to org.openhab.binding.draytonwiser.internal.DraytonWiserRefreshListener
2020-06-12 11:20:16.165 [hingStatusInfoChangedEvent] - 'draytonwiser:boiler-controller:92516180' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2020-06-12 11:20:54.561 [hingStatusInfoChangedEvent] - 'draytonwiser:heathub:WiserHeat02851D' changed from OFFLINE (COMMUNICATION_ERROR): Cannot cast org.eclipse.smarthome.core.thing.internal.ThingImpl to org.openhab.binding.draytonwiser.internal.DraytonWiserRefreshListener to ONLINE
2020-06-12 11:20:54.567 [hingStatusInfoChangedEvent] - 'draytonwiser:boiler-controller:92516180' changed from OFFLINE (BRIDGE_OFFLINE) to UNKNOWN
2020-06-12 11:20:54.571 [hingStatusInfoChangedEvent] - 'draytonwiser:heathub:WiserHeat02851D' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Cannot cast org.eclipse.smarthome.core.thing.internal.ThingImpl to org.openhab.binding.draytonwiser.internal.DraytonWiserRefreshListener
2020-06-12 11:20:54.575 [hingStatusInfoChangedEvent] - 'draytonwiser:boiler-controller:92516180' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2020-06-12 11:21:55.257 [hingStatusInfoChangedEvent] - 'draytonwiser:heathub:WiserHeat02851D' changed from OFFLINE (COMMUNICATION_ERROR): Cannot cast org.eclipse.smarthome.core.thing.internal.ThingImpl to org.openhab.binding.draytonwiser.internal.DraytonWiserRefreshListener to ONLINE
2020-06-12 11:21:55.261 [hingStatusInfoChangedEvent] - 'draytonwiser:boiler-controller:92516180' changed from OFFLINE (BRIDGE_OFFLINE) to UNKNOWN
2020-06-12 11:21:55.264 [hingStatusInfoChangedEvent] - 'draytonwiser:heathub:WiserHeat02851D' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Cannot cast org.eclipse.smarthome.core.thing.internal.ThingImpl to org.openhab.binding.draytonwiser.internal.DraytonWiserRefreshListener
2020-06-12 11:21:55.268 [hingStatusInfoChangedEvent] - 'draytonwiser:boiler-controller:92516180' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2020-06-12 11:22:54.907 [hingStatusInfoChangedEvent] - 'draytonwiser:heathub:WiserHeat02851D' changed from OFFLINE (COMMUNICATION_ERROR): Cannot cast org.eclipse.smarthome.core.thing.internal.ThingImpl to org.openhab.binding.draytonwiser.internal.DraytonWiserRefreshListener to ONLINE
2020-06-12 11:22:54.910 [hingStatusInfoChangedEvent] - 'draytonwiser:boiler-controller:92516180' changed from OFFLINE (BRIDGE_OFFLINE) to UNKNOWN
2020-06-12 11:22:54.913 [hingStatusInfoChangedEvent] - 'draytonwiser:heathub:WiserHeat02851D' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Cannot cast org.eclipse.smarthome.core.thing.internal.ThingImpl to org.openhab.binding.draytonwiser.internal.DraytonWiserRefreshListener
2020-06-12 11:22:54.915 [hingStatusInfoChangedEvent] - 'draytonwiser:boiler-controller:92516180' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2020-06-12 11:23:55.801 [hingStatusInfoChangedEvent] - 'draytonwiser:heathub:WiserHeat02851D' changed from OFFLINE (COMMUNICATION_ERROR): Cannot cast org.eclipse.smarthome.core.thing.internal.ThingImpl to org.openhab.binding.draytonwiser.internal.DraytonWiserRefreshListener to ONLINE
2020-06-12 11:23:55.804 [hingStatusInfoChangedEvent] - 'draytonwiser:boiler-controller:92516180' changed from OFFLINE (BRIDGE_OFFLINE) to UNKNOWN
2020-06-12 11:23:55.808 [hingStatusInfoChangedEvent] - 'draytonwiser:heathub:WiserHeat02851D' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Cannot cast org.eclipse.smarthome.core.thing.internal.ThingImpl to org.openhab.binding.draytonwiser.internal.DraytonWiserRefreshListener
2020-06-12 11:23:55.810 [hingStatusInfoChangedEvent] - 'draytonwiser:boiler-controller:92516180' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)```

When uninstalling the binding, it fails to cleanly uninstall leaving the binding visible and the wait icon just circling on the addons/binding page of paperui. Here are the new lines added to the event log

2020-06-12 11:31:21.195 [hingStatusInfoChangedEvent] - 'draytonwiser:boiler-controller:92516180' changed from REMOVING to REMOVED
2020-06-12 11:31:21.211 [hingStatusInfoChangedEvent] - 'draytonwiser:boiler-controller:92516180' changed from REMOVED to UNINITIALIZED
2020-06-12 11:31:21.253 [hingStatusInfoChangedEvent] - 'draytonwiser:boiler-controller:92516180' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2020-06-12 11:31:27.914 [hingStatusInfoChangedEvent] - 'draytonwiser:heathub:WiserHeat02851D' changed from OFFLINE (COMMUNICATION_ERROR): Cannot cast org.eclipse.smarthome.core.thing.internal.ThingImpl to org.openhab.binding.draytonwiser.internal.DraytonWiserRefreshListener to REMOVING
2020-06-12 11:31:27.921 [hingStatusInfoChangedEvent] - 'draytonwiser:heathub:WiserHeat02851D' changed from REMOVING to REMOVED
2020-06-12 11:31:27.927 [hingStatusInfoChangedEvent] - 'draytonwiser:heathub:WiserHeat02851D' changed from REMOVED to UNINITIALIZED
2020-06-12 11:31:27.960 [hingStatusInfoChangedEvent] - 'draytonwiser:heathub:WiserHeat02851D' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)```

Yes please use the latest version. The log you added shows the specific bug I fixed.

It is in and so far running. I am getting a communications error to a Room, but to be fair, the room has been defined as per the wiser app, but does not have any TRV assigned as I do not have the serial number to hand. The auto detection solved this issue, is this a bug or has auto detect been removed?

Can you post the error.

Auto detection has not been removed. I’ve added some debug logging to the binding and uploaded a new kar file. If you enable debug level (log:set DEBUG org.openhab.binding.draytonwiser) and trigger discovery you should see it should find devices.

The room now has the TRV assigned and I can see the TRV fine. The Room is showing in the control panel and has temperatures, but remains as OFFLINE (COMMUNICATION_ERROR) in the Thing panel.


2020-06-12 13:07:49.069 [me.event.ThingUpdatedEvent] - Thing 'draytonwiser:room:692c25a1' has been updated.

2020-06-12 13:07:50.092 [hingStatusInfoChangedEvent] - 'draytonwiser:room:692c25a1' changed from UNKNOWN to OFFLINE (COMMUNICATION_ERROR)

Where do I enable the debug? And what is the cleanest way to load the new kar file? uninstall/reinstall or just copy it in and restart?

Thanks for your help it is starting to look a little more promising.

You can enable debug in the karaf console.

Enabling debug should also give more information about the off line problem of the room.

Remove the file and check the log it has been uninstalled. And then you can put in the new kar file. It should not be needed to restart. Although sometimes when working with updated files manually cleaning cache and tmp and restart might be the safest. But you can always try that if at one point a updated kar file causes errors.