[openWebNet/BTicino] openHAB4 ... old thread

This thread is for discussions concerning the openwebnet binding.

This thread was automatically closed.
Please use the new thread

Please check the readme docs for capabilities, configuration information and configuration examples.
ReadMe github
ReadMe openhab addons

For general discussions, information, links and help with BTicino/Legrand home automation please use this thread >>>
https://community.openhab.org/t/bticino-legrand-home-automation-general-discussions-openwebnet-protocol/131485

It’s a lot easier for your end users/testers if you publish this to the marketplace: Bundles - openHAB Community

That lets your users install it same as the “official” add-ons.

Thanks Rich,

You need to address that to @massi . I am only an end user/tester and not the programmer/developer.

This thread is dedicated to the OH4 version of a binding that is already part of OH
So no need to publish on the marketplace.

In fact there is also a Beta version of it on the marketplace, but I will unpublish it for now as it does not provide any new feature comparted to the official version.

Hi everyone, I have been happily using Binding 4.0 for a few months now.

Everything is working properly:

  • Lights
  • Thermo 99 Zone
  • Alarm
  • Aux/Cen/Cen+

I have tried the new function on the gateway for time sync and it works correctly. I have 2 GW, a MH200N and a Touch 10". The second one is master of the system but not used as GW in OH. I didn’t quite understand when a time update goes through on the Bus but, if any device send the time, the nice thing is that the Master also updates saving me having to change the time for solar and legal time.

The new timeSynch feature looks for time events on the bus (these should be sent regularly by the master device ).
If the time event seen on the bus differs for more than 60s from the OH machine time (which usually in turn is in synch to internet time servers) then time is adjusted to OH time.
This should be useful when BUS gateways do not update themselves for summer time or in case of power failures.

Hi there,

how can I trigger scenarios from the graphical UI?
just done it by files right now, but what I need to do in the UI?

Switch item=RollEGoeffnen label="Rolläden EG öffnen"  icon="movecontrol" mappings=[ON="Start"]

but when I do this, nothing happens.

Even by entering SHORT_PRESS or START_PRESS or Activate,…


What do I need to do to get a list where my Scenarios are listed and if they are pressed or a start button touched to make then work?

thanks in advance
kind regards
Christian

not sure but i suppose this may not be possible because cen are channels that need a rule to be started. as in the description of the binding shown you only can set a proxy item that triggers a rule, the proxy item then can be switched in the ui, at least this is the way i do it.

I’m doing this like shown here if it is file based and it works like a charm.

in items:

String          RollEGoeffnen                 "Rolläden EG öffnen"               <network>         (gSzenarien)                                         //   {channel="openwebnet:bus_cen_scenario_control:mybridge:99:button#8" }

in sitemap:

Switch item=RollEGoeffnen label="Rolläden EG öffnen"  icon="movecontrol" mappings=[ON="Start"]

yes,you’re right

rule "Regel Rolläden EG öffnen"
when
    Item RollEGoeffnen received command
then
    val actions = getActions("openwebnet","openwebnet:bus_cen_scenario_control:mybridge:CEN_Control")
    actions.virtualPress("START_PRESS", 8)
end

there’s a rule :slight_smile:

But I can’t get it work if all is UI based without config files.

sorry i dont understand. now you have a textual config

  • perhaps a thing with your cen command (only needed when you want to listen to incoming cen command eg from a phys switch)
  • a switch item to send command ON
  • a dsl rule to proccess the on command from the switch to send a cen command to the bux

try to go step by step to see when it does not work. first remove the switch item from the textual config and create it in main-ui and see if it still works

then remove the code from rules dsl and create it in the main-ui. i cannot imagine why this could not work then but i never tried to create a rule in main-ui so i dont know. perhaps check a file created rule how it looks in main-ui to see how you have to set it up.

I’ve made some testing and probably found why I was confused, probably a bug.

Test executed:

  1. Touch screen GW is the master and date time is “current time” (e.g. 12:00).
  2. From Touch Screen set date time = now + 1h (e.g. 13:00)
  3. All the device on the bus got time updated but, Binding during timecheck report difference is 2 sec and doesn’t perform any adjustment.
  4. From Touch Screen set date time = now + 50min (e.g. 12:50)
  5. All the device on the bus got time updated but, Binding during timecheck find a difference and set date time correctly according to OpenHab date time.
checkDateTimeDiff: difference is more than 60s: 3304s
synch DateTime to: 2023-07-29T12:01:57.020284552+02:00[Europe/Berlin]

Is the timcheck function considering Hour and Minutes or only Minutes?

Marco

Time check is computed on absolute time, even considering the time zone (you could have set two different TZ on OH and on BUS GW).

To check what is happening in your case, I would need the DEBUG level log from when you change the time on the BUS GW until the Binding declares that the difference is not enough to trigger a time synch.

I have now also moved from OH 3.4.0 to 4.0.1, and so far it seems everything is working! Thanks @massi for the work on the new version!

I’ve made some test but I probably need more time and to use My Home Suite to double check which device is set as master and if having the Touch Screen configured in OH as GW but without other subthings is making any difference.

I don’t think it’s a matter of time zone and I verified that diff works on absolute time.

When I change the time (+1h) from the Touch Screen the Thermo and Alarm got the time update but, in OH log I still get the old time on the bus probably coming from the other GW (MH200N that should be slave). But after receiving the message with the old time Thermo and Alarm maintein the wrong +1h.

When I do a second change on Touch Screen (tried +1h and 10minutes e.g.) the binding react and reset all the device time to the Openhab ones…

You need to sure what is set to master or slave. More than one master would be confusing. Master or slave are set via my home suite.

I have mh202 and screen10. My 99 zone therm unit doesn’t have the option but will act as slave but also transmits its time on the bus every 30sec. I did a test again with oh4 disconnected form the network and then using the openwebnet client was able to change the slaves time to a false one. After reconnecting oh4 to my network the slave time was corrected to my local time… All behavior is as expected for me.

I have both OH4 and OH3.4 running, a RPi for each. OH4 is my test server almost nothing on it, no rules, no items, etc except for the openwebnet binding and gateway thing.

For OH4 I see these errors in the log


[WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*1##

and 

[WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*0##

OH3 reports doesn’t show any errors.

It seems to be related to 3477 contacts sensor. F428 contacts sensors do not generate errors.

Is anyone else seeing this ?

this frame: *#13**3*1## is releated to WHO=13 (Gateway Management). However in the official OWN specs documentation, DIM=3 is not documented so I cannot really tell what this message is related to.

Strange.

I had OH3 using Screen10 as gateway and all things and items configured in files. For my OH4 test server I used MH202 as gateway and almost no things and itenms conifgured. I did configure the contacts 3477 sensor using the UI just to confirm in the log which BUS device was causing the issue.

==> /var/log/openhab/events.log <==

2023-09-07 07:11:57.147 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorClosed' changed from OFF to ON

2023-09-07 07:11:57.197 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorMoving' changed from ON to OFF

==> /var/log/openhab/openhab.log <==

2023-09-07 07:11:58.837 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*1##

2023-09-07 07:11:58.879 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*1##

==> /var/log/openhab/events.log <==

2023-09-07 07:11:58.328 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorMoving' changed from OFF to ON

2023-09-07 07:11:58.457 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorMoving' changed from ON to OFF

==> /var/log/openhab/openhab.log <==

2023-09-07 07:15:01.617 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*1##

2023-09-07 07:15:06.548 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*1##

==> /var/log/openhab/events.log <==

2023-09-07 18:45:45.120 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorMoving' changed from OFF to ON

==> /var/log/openhab/openhab.log <==

2023-09-07 18:45:45.619 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*0##

2023-09-07 18:45:45.661 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*0##

==> /var/log/openhab/events.log <==

2023-09-07 18:45:45.429 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorClosed' changed from ON to OFF

2023-09-07 18:46:15.006 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorMoving' changed from ON to OFF

==> /var/log/openhab/openhab.log <==

2023-09-07 18:46:43.266 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*0##

==> /var/log/openhab/events.log <==

2023-09-07 18:46:42.795 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorMoving' changed from OFF to ON

==> /var/log/openhab/openhab.log <==

2023-09-07 18:46:43.328 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*0##

2023-09-07 18:47:22.607 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*0##

==> /var/log/openhab/events.log <==

2023-09-07 18:47:22.332 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorClosed' changed from OFF to ON

2023-09-07 18:47:22.392 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorMoving' changed from ON to OFF

==> /var/log/openhab/openhab.log <==

2023-09-07 18:47:24.027 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*0##

2023-09-07 18:47:24.056 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*0##

==> /var/log/openhab/events.log <==

2023-09-07 18:47:23.522 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorMoving' changed from OFF to ON

2023-09-07 18:47:23.652 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorMoving' changed from ON to OFF

==> /var/log/openhab/openhab.log <==

2023-09-07 20:57:48.187 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*0##

2023-09-07 20:57:48.217 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*0##

==> /var/log/openhab/events.log <==

2023-09-07 20:57:47.674 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorMoving' changed from OFF to ON

2023-09-07 20:57:48.053 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorClosed' changed from ON to OFF

2023-09-07 20:58:16.910 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorMoving' changed from ON to OFF

2023-09-07 20:58:35.368 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorMoving' changed from OFF to ON

==> /var/log/openhab/openhab.log <==

2023-09-07 20:58:35.855 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*0##

2023-09-07 20:58:35.873 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*0##

2023-09-07 20:59:15.227 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*0##

==> /var/log/openhab/events.log <==

2023-09-07 20:59:14.952 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorClosed' changed from OFF to ON

2023-09-07 20:59:15.014 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorMoving' changed from ON to OFF

==> /var/log/openhab/openhab.log <==

2023-09-07 20:59:16.658 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*0##

==> /var/log/openhab/events.log <==

2023-09-07 20:59:16.142 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorMoving' changed from OFF to ON

2023-09-07 20:59:16.273 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorMoving' changed from ON to OFF

==> /var/log/openhab/openhab.log <==

2023-09-07 20:59:16.683 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*0##

2023-09-07 21:38:54.854 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*0##

2023-09-07 21:38:54.912 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*0##

==> /var/log/openhab/events.log <==

2023-09-07 21:38:54.340 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorMoving' changed from OFF to ON

2023-09-07 21:38:54.770 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorClosed' changed from ON to OFF

2023-09-07 21:39:23.616 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorMoving' changed from ON to OFF

==> /var/log/openhab/openhab.log <==

2023-09-07 21:39:59.784 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*0##

2023-09-07 21:39:59.803 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*0##

==> /var/log/openhab/events.log <==

2023-09-07 21:39:59.179 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GarageDoorMoving' changed from OFF to ON

==> /var/log/openhab/openhab.log <==

2023-09-07 21:40:39.076 [WARN ] [openwebnet4j.message.BaseOpenMessage] - Unsupported DIM: 3 - frame *#13**3*0##

I then changed OH4 to use Screen10 as gateway and so far I have not seen the error again.

I will do some testing to get some details on the events and the gateway. Sometimes I see #13**30## and other times #13**31##

OH4

  • MH202 as gateway: 3477 contact sensor activated >>> error in log. Deactivates >>> no error
  • Screen10 as gateway: No errors

OH3.4

  • MH202 as gateway: No errors
  • Screen10 as gateway:No errors

I’m currently using OH4 with MH200N, no errors… Touch screen 10 is configured with no items.