in the next window insert at top right your gateway data (ip-address, and password, port normally always is 20000) and click “connect”. the red dot must become green
you will then have to press the eg light-button of a light you want the address, it takes short time and then the (actor or dali) device should be found and listed in the right window. click the line and drag it to the middle window. then on the right window switch from “bus scanner” to “configuration” - then on the right window you see the actor with its modules, there you can see (and change) the adresses.
if you want to store a changed address select the device in the middle, with a right-click you can select “send configuration” to write it back to the device
Tip: You can save the scan results as a .plant file.
Then if you want to update something or just want to review the list you can open the .plant file instead of repeating the scanning. I have separate plant files for devices, MH202 scenarios and Screen10 setup. Devices show as green when the config has been sent successfully.
If you were having the same issue I had with MHS1 using unwanted addresses, I recommend you avoid changing the address via myhomesuit, as it didn’t work for me and caused issues.
Have read on this one
It has the step-by-step to force MyHomeServer1 to choose another address.
checkDateTimeDiff: Exception while sending set DateTime command: CMD is not connected
Time slaves do not update.
I have time sync enabled. It occurs after a router reboot (eg power cut) and is fixed by enabling and disabling the binding. I have now created a rule to do that.
I also noticed that the same error occurs when sending a command, using actions, to send an openwebnet frame to set the time slaves. eg *#13**#22*hr*min*sec*000*28*14*04*year##
I guess something gets disconnected in the binding and is not reconnected when everything is back up.
FYI >>>>
Also, I finally found the source of my time zone error when using the time sync option. Maybe it helps someone with this feature
linux timedatectl command response >>>>>
Local time: Sat 2026-08-15 09:25:44 CEST
Universal time: Sat 2026-08-15 07:25:44 UTC
RTC time: n/a
Time zone: Europe/Vienna (CEST, +0200)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
Correct, and openHAB settings also looked to be correct
I do not see this error, but this is because I do not have dateTimeSynch enabled. I have a python rule to set correct date and time and all bticino devices run in slave mode. This works for me.
It should work and it would be good if this binding feature was reliable for people who want life to be simple. A power cut stopped some scenarios running because the time of day was wrong when everything was back up. My MH202 scenario controller and Screen 10 are both set to be time slaves.
I have written a rule to display the BUS time and NTP time on my sitemap with a sitemap button to sync them on demand. I just need to write the part that automatically checks if there is a difference in time between BUS and openHAB, but first I wanted to monitor what circumstances causes the binding time sync option to fail.
How often does your python script check and sync the time and what allowed time difference is reasonable?
Indeed the feature should work if its implemented.
I already use my own code since a long time and it works how I like it: Always seven seconds after each full hour I send the date/time OWN. This ensures even after clock change (summer - winter) I always have the correct time on all my bticino screens and never have to care about it.
Hi Mark
What probably is happening is that in case of router restart (=no connectivity to the gateway), the time synch command fails to be sent to the gateway and this blocks the binding.
This should be solved as it makes useless the time synch feature.
Can you create a new issue in GitHub?
As always, is important to add to the issue the specific log section (activate DEBUG mode first both for binding and OWN lib).
The openhab binding connects to openwebnet bus via the the configured bus gateway thing. The binding reports in the logs when there are unsupported bus frames (who). Or if you really want to see all bus activity you could use the openwebnet client.
Via ethernet cable and IP address in the gateway. I have MH202 scenario conreoller and Screen10 touch screen panel amd either can act as a gateways; there are others too. Both have an IP address to which I can configure the openwebnet gateway thing to use. BUS frames are via the 24v power cables to connected devices. So, the BUS power supply links them all.
I know practically nothing about our setup. It was already there when we bought the house.
But since we’ve got two of those classe 100 devices, I can only assume there’s a BUS somewhere, including in the fuse box.
I’d be interested to see what could get retrieved from it, but wouldn’t know how to take the first step: get the BUS to some kind of connector and in a device.
Maybe this thread helps learn and there some links to more material. Also, it is where we talk about more general stuff rather than openHAB binding specific topics >>>