[OpenWebNet] Thermoregulation support in openHAB3 ready for testing

just installed and tested, great!
for me it seems everything is working as expected: i can change the setpoint-temp now and the changes are also set in the termo-zone. if zone was in mode “automatic” it changes to “manual” as soon as i change the temp.
when i change back to mode “automatic” (actually not possible in openhab) the setpoint temp changes to the temp that is set for the automatic.

Thank you so much for your great work!!!
It seems to me that the binding is working as expected. I can change the setpoint temperatures in “Manual” mode and the binding and the thermo-zone are always aligned (checked with an F454 gateway). When I put a thermo-zone in “Auto” mode from OFF or Protection, the behavior is the one expected: the mode in the binding is changed to “Manual” and the corresponding setpoint temperature is set to the last one associated to the themo-zone (the one associated to the auto mode or manual mode, according to the last configuration of the themo-zone itself). This is the same behavior you can experience using an F454 gateway. The only two comments I have (but actually I don’t know if already covered by the current development, so in case please ignore them) are:

  • Thermo-zone in Protection mode: the setpoint temperature in the binding is not updated to 7 degree (see following figures).
  • Thermo-zone in Off mode: the setpoint temperature in the binding is not empty (see following figures).

In both cases the setpoint temperatures continue to point to the last setpoint temperature (manual or auto) associated to the thermo-zone (8 degree in the following figures, “Temp. Soppalco (M)” field).

thermo-zone


thermo-zone3

Seen just now and sounds great… goint to make some test shortly and provide feedback.
Thanks Andrea

Made some testing, few feedbacks hereafter:

  • As expeceted manual dependency install from Console to let the binding work (Transport and Upnp)
  • Central Unit not supported warning shown in the logs:

newDiscoveryResult() deviceType=SCS_THERMO_CENTRAL_UNIT is not supported yet (WHERE=w:#0)

  • If thermo is Off, setting of Zone Temp is correctly triggering the switch into Manual status, Function to Heating and Thermo is Turned On
  • If thermo is already On, unfortunately setting of Zone status Off is not triggering Thermo switching to Off

Hi guys,
I’m currently using the official openwebnet binding but interested in the thermo central unit (99 zone) feature. Are there plans about merging this feature in the official binding? Thanks a lot

Hi @Brando, see this post: [OpenWebNet] Support for central units in thermoregulation

We’re working on it!

1 Like

Many thanks Andrea and Massi. I’ll keep checking the news on the community!

Updating heat set point to central unit works well for me too. (I got a 99 temp zone unit)
To help other as it was not straightfoward to me : you need to uninstall your bticino binding then upload the latest alpha jar from

Releases · aconte80/openhab-addons · GitHub

to

/usr/share/openhab

I did restart the openhab service, I don’t know if it was needed though;

you should no longer need to do that because meahnwhile the thermo feature (only display temp without integration of 99 temp zone) is integrated in the official distribution binding (stable release 3.2.0)

Hi @bastler , that’s weird, because I juste reverted to the official binding and it does not work anymore.
I stopped the openhab service, removed the jar, started the service, installed the official binding through the web interface, I did not restart and all my items are back. But I cannot change the heat setpoint.
What could I do to troubleshoot that?

Hi guys,
I’ve just published an updated release of the binding for central unit (ALPHA-2)
As always, feedbacks will be appreciated!

More details on GitHUB:

1 Like

I get following error when it try’s to enable the auto discovered central unit,
may you can have a look.
Tested with openHAB 3.3.0 / Build #2694

2022-01-15 11:22:03.685 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method 'ThingHandler.initialize()' on 'org.openhab.binding.openwebnet.internal.handler.OpenWebNetThermoregulationHandler@d48976': null

java.lang.NullPointerException: null

at org.openhab.binding.openwebnet.internal.handler.OpenWebNetThermoregulationHandler.initialize(OpenWebNetThermoregulationHandler.java:99) ~[?:?]

at jdk.internal.reflect.GeneratedMethodAccessor67.invoke(Unknown Source) ~[?:?]

at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]

at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]

at org.openhab.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:154) [bundleFile:?]

at org.openhab.core.internal.common.Invocation.call(Invocation.java:52) [bundleFile:?]

at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]

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

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

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

2022-01-15 11:22:03.689 [ERROR] [core.thing.internal.ThingManagerImpl] - Exception occurred while initializing handler of thing 'openwebnet:bus_thermo_cu:Bticino_F454:0': null

java.lang.NullPointerException: null

at org.openhab.binding.openwebnet.internal.handler.OpenWebNetThermoregulationHandler.initialize(OpenWebNetThermoregulationHandler.java:99) ~[?:?]

at jdk.internal.reflect.GeneratedMethodAccessor67.invoke(Unknown Source) ~[?:?]

at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]

at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]

at org.openhab.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:154) [bundleFile:?]

at org.openhab.core.internal.common.Invocation.call(Invocation.java:52) [bundleFile:?]

at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]

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

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

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

yes, I know. Discovery is one of open points.
You should add CU manually as described in the readme.

Thanks for the hint, missed that, but may you add in the readme that also the bridge need to be defined textual otherwise it gives the same error as when it get discovered.

i just tried the addon, most things seem to work as expected. the only thing i realized till now:
when i change the modes to programm (i suppose “programm” meams “automatic”) sometimes it immediately switches back to manual

example (done in webbrowser):

2022-01-16 15:33:32.259 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'iBuero_Heizung_Mode' changed from MANUAL to PROTECTION

2022-01-16 15:33:32.519 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'iBuero_Heizung' changed from 21.3 °C to 21.4 °C

2022-01-16 15:33:32.612 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'iBuero_Heizung_Set' changed from 21 °C to 7 °C

2022-01-16 15:33:38.750 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'iBuero_Heizung_Set' changed from 7 °C to 21 °C

2022-01-16 15:34:01.477 [DEBUG] [ernal.handler.OpenWebNetThingHandler] - handleCommand() (command=PROGRAM - channel=openwebnet:bus_thermo_zone:bticino:Buero_Heizung:mode)

2022-01-16 15:34:01.463 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'iBuero_Heizung_Mode' received command PROGRAM

2022-01-16 15:34:01.469 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'iBuero_Heizung_Mode' predicted to become PROGRAM

2022-01-16 15:34:01.472 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'iBuero_Heizung_Mode' changed from PROTECTION to PROGRAM

2022-01-16 15:34:02.292 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'iBuero_Heizung_Mode' changed from PROGRAM to MANUAL

@bastler where do you set “programm” ? maybe in the c.u. menu?

the items for controlling the cu i did not setup and test till now.

i only had the items for the local zones setup, for example one room:

Number:Temperature iBuero_Heizung "Büro Ist-Temperatur[%.1f %unit%]" <temperature> (iG_Heizung) { channel="openwebnet:bus_thermo_zone:bticino:Buero_Heizung:temperature" }
Number:Temperature iBuero_Heizung_Set "Soll-Temperatur[%.1f %unit%]" <heating> { channel="openwebnet:bus_thermo_zone:bticino:Buero_Heizung:setpointTemperature" }
String iBuero_Heizung_Mode "Modus" <settings> { channel="openwebnet:bus_thermo_zone:bticino:Buero_Heizung:mode" }
String iBuero_Heizung_Aktor "Heizung heizt![]" <radiator> { channel="openwebnet:bus_thermo_zone:bticino:Buero_Heizung:actuators" }

now at the moment i setup the items for the central, now i see when i set the mode from a local zone to OFF and then back to programm in the log:

2022-01-16 17:06:50.229 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'iBuero_Heizung_Mode' received command OFF

2022-01-16 17:06:50.244 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'iBuero_Heizung_Mode' predicted to become OFF

2022-01-16 17:06:50.252 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'iBuero_Heizung_Mode' changed from MANUAL to OFF

2022-01-16 17:06:51.484 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'iZentrale_3550_Mode' changed from MANUAL to WEEKLY_1

2022-01-16 17:06:51.520 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'iZentrale_3550_Mode' changed from WEEKLY_1 to MANUAL

2022-01-16 17:07:40.642 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'iBuero_Heizung_Mode' received command PROGRAM

2022-01-16 17:07:40.649 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'iBuero_Heizung_Mode' predicted to become PROGRAM

2022-01-16 17:07:40.655 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'iBuero_Heizung_Mode' changed from OFF to PROGRAM

2022-01-16 17:07:41.535 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'iBuero_Heizung_Mode' changed from PROGRAM to MANUAL

2022-01-16 17:07:41.914 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'iZentrale_3550_Mode' changed from MANUAL to WEEKLY_1

2022-01-16 17:07:41.933 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'iZentrale_3550_Mode' changed from WEEKLY_1 to MANUAL

I am testing
org.openhab.binding.openwebnet-3.3.0.M1.beta2.bootsynch-thermocu.jar

fresh openhabian install OH3.2 RPi4b

heatingValves still not working… Item is now string type and Valves not Valve according to snapshot readme

No errors seen with default log level

Thing bus_thermo_zone 6 "Office" [ where="6" ] 
String Office_HeatingValve "Office heating" <radiator> {channel="openwebnet:bus_thermo_zone:gateway:6:heatingValves"}

to be honest i never used the channel heatingValves
i use the channel actuators that tells me if my valve from the underfloor heating is ON or OFF

I tried them all and all null

String Office_Actuator "Office actuator" <radiator> {channel="openwebnet:bus_thermo_zone:gateway:6:actuator"}
String Office_ConditioningValve "Office conditiong valve" <radiator> {channel="openwebnet:bus_thermo_zone:gateway:6:conditioningValves"}

Heatingvalves used to work with OH2.5 and with OH3.2 the marketplace binding worked at boot but items were not updated after that.

I am using the 99zone control unit

Here is what I see after increasing the thermostat

and decreasing