[BTicino/OpenWebNet] New openHAB2 binding ready for testing

If you go in PaperUI > control tab, can you set your rollershutter to 0% from there?
If yes, then the problem should be in the integration between Alexa and openHAB , not with the binding…
M

Hi Massi,
you are right. In PaperUI it works. This is an Alexa Problem. Thank you for your reply and your help.

I thinking about testing this Binding.
Is there possibility to set different runtimes for each shutter?
LG Patrick

Yes, each shutter device has its own runtime parameter that can be set.
Massi

Thank u for the info :slight_smile:
I will test it at the weekiend :slight_smile:

I got an error, when i start the binding
I followed the tutorial at the beginning of this threat

openhab> bundle:start org.openhab.binding.openwebnet
Error executing command: Error executing command on bundles:
        Error starting bundle 209: Could not resolve module: org.openhab.binding.openwebnet [209]
  Unresolved requirement: Import-Package: org.eclipse.jdt.annotation; resolution:="optional"
  Unresolved requirement: Import-Package: org.jupnp.model.meta

you do not need to activate the binding unless you are upgrading it. It should be enough to put the JAR in the addons folder and activate manually some feature dependencies:

  1. go to Karaf console
  2. Type:
    feature:install openhab-transport-serial
  3. and if you are using openHAB 2.4.0-SNAPSHOT also type:
    feature:install esh-io-transport-upnp

at this point the binding should now be installed: check in PaperUI > Configuration > Bindings .

In case you still have problems set log level to DEBUG (see how in the thread) and send me a PM with the openhab.log along with your configuration (whcih BTicino gateway, IP address…)

Bye
massi

Dear @massi,
I’m using your great great binding with MyHome Server1 .

OpenHab2 thing is this

OpenWebNet BUS Gateway - openwebnet:bus_gateway:29b22252

and “Shutter run” is set to AUTO

My item config for this shutter is the following:

Rollershutter GF_Studio_Shutter “Avvolgibile finestra [%d %%]” (GF_Studio, gShutter) [ “Rollershutter” ] {channel=“openwebnet:bus_automation:29b22252:33:shutter”}

But I don’t see the textbox to set the percent% and use it.

My home was configured through MyHomeUp, also on the BTicino MyHomeUp app I do not have a way to set the percentage.

Have you any hint?

Many thanks!
Ivan

P.S.
I would like to give you support / help on your project, if you need it let me know.

Can you post a picture of your Coltrol tab in PaperUI? Your config looks ok so you should see the text box for position of the item seen form PaperUI …

Help in testing is always welcome.
Do you have thermostats in your BTicino system?

Massi

Thanks Massi.
Yes, I have thermostats in my BTcino system (five of them in various rooms).
Yesterday I changed the config of my Rollingshutter changing AUTO in 18000ms in “Shutter run”, now I’m able to see the percentage but I’m not still able to see a textbox and move them by percentage.
I’m using F411/U2 actuators.

sshot1

Many thanks

I enclose the “Thing config” sshot in this answe and also the Control sshot in the next (as a new user I can post only 1 image for each message)

sshot2

One more thing.

Creating a rule where I set:

GF_Studio_Shutter.sendCommand(10)

the shutter does not move.

Using the same but without the percentage:

GF_Studio_Shutter.sendCommand(DOWN)

it works. On the log side:

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

2018-07-08 08:52:26.943 [WARN ] [.handler.OpenWebNetAutomationHandler] - ==OWN:AutomationHandler== updateAutomationState() FRAME <21000#0*33##> NOT SUPPORTED for thing openwebnet:bus_automation:29b22252:33, ignoring it.

2018-07-08 08:52:26.994 [WARN ] [.handler.OpenWebNetAutomationHandler] - ==OWN:AutomationHandler== updateAutomationState() FRAME <21000#2*33##> NOT SUPPORTED for thing openwebnet:bus_automation:29b22252:33, ignoring it.

2018-07-08 08:52:32.812 [WARN ] [.handler.OpenWebNetAutomationHandler] - ==OWN:AutomationHandler== updateAutomationState() FRAME <21000#0*33##> NOT SUPPORTED for thing openwebnet:bus_automation:29b22252:33, ignoring it.

2018-07-08 08:52:39.377 [WARN ] [me.core.internal.events.EventHandler] - Dispatching event to subscriber ‘org.eclipse.smarthome.io.monitor.internal.EventLogger@16c309d’ takes more than 5000ms.

I don’t know if this helps.
Ivan

PS.
Rolling shutter motors produced by Elero (Nice), a German brand but produced in Italy (I think).

Hi,
I have also tested this. When i make some rules with UP/Stop and Down it works perfectly. When i send a command 30% the shutter drives to 100% :slight_smile:.

12:17:25.542 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'RolloWohnziLi' received command 30
12:17:25.581 [INFO ] [smarthome.event.RuleStatusInfoEvent  ] - ee930ef0-baf4-4d41-a57d-19349311862c updated: IDLE
12:17:25.624 [INFO ] [smarthome.event.ItemStateChangedEvent] - RolloWohnziLi changed from 0 to 30
12:17:25.669 [INFO ] [smarthome.event.ItemStateChangedEvent] - RolloWohnziLi changed from 30 to 1
12:17:33.759 [INFO ] [smarthome.event.ItemStateChangedEvent] - RolloWohnziLi changed from 1 to 40
12:17:49.184 [INFO ] [smarthome.event.ItemStateChangedEvent] - RolloWohnziLi changed from 40 to 100

The new binding in combination with expermential rule binding works great :smiley:

many thanks to the coders

In the README it is explained that for Position% to work a calibration must first be completed going all down (100%), then all up (0%), then to position (x%).
It looks like your calibration did non work.

Try first to set manually the shutterRun (see README) and if it works with manual calibration, try to set back to AUTO and do an auto calibration (see README) and then tell me if it works.

Bye
Massi

The Positionig with % works now only my MH202 connection is a bit unstable and i love this binding :). great job

Hi Patrick,

I saw , before the post was deleted, that you had some instability issues with MH202. I also have MH202 and found that the binding can cause the MH202 to reboot. It occurs every time I scan for devices with PaperUI. I know it does this becasue I have a MH202 scenario that only runs at MH202 restart (checked box in top right for Scenario config in MyHomeSuite). I wondered if your instability issues are the same and if you see the same issue.

I have also had repeated restarts for no apparent reason and restarts when Openhab is restarted. These are not consistent and at the moment they are not happening but the restart on actuator, switch scan always occurs.

I haven’t tried using the blind calibration feature but might give it a try tonight, if its raining and I can’t dig the big trench at the back of my house that I have been working on :slight_smile:

Hi,
the calibration of the shutter works :slight_smile:.
Good to hear that i’m not alone, it seems that the connection stop every time when i send a few commandos in a short time.
testing is every day at the evning possible :slight_smile:

bg

I have been helping Massi test preview versions before the beta release. So, I have to bear that in mind when we discuss or it will get confusing.

I also have the problem, that my MH202 restarts at irregular intervals, but - in my case - this is not related to the OpenHab binding (it runs over my webserver “F454”).

I really appreciate your efforts making this a GREAT binding, but since % positioning is difficult to achieve (obviously dued to hardware limitations), would it be possible to implement a time based positioning which could be used in control page and invoked in rules?
I mean a sort of timed-UP or timed-DOWN command.
Example:
UP for 5 seconds then STOP
or
DOWN for 10 seconds then STOP

IMHO this could achieve a really big semplification in scenarios (morning scenario = UP for 5 seconds all shutters then STOP).

…or maybe this is just a useless proposal…so ignore it :slight_smile:

…and just a question: is anyone experiencing lag in response when sending multiple UP/DOWN/STOP commands?