Thanks a lot for all the work.
Just got an Amazon Echo dot and I would like to send command using voice.
I started to install OpenHab2 2.3.0 on a ubuntu linux.
I have the bticino F454 with firmware 2.0.5. No password is required on the gateway from host on the same subnet.
I followed the readme file to install the addons but the binding cannot connect to my F454
==OWN== BridgeHandler creating new gatewayBus with config properties: 192.168.6.42:20000, 140681
2018-07-01 18:55:41.074 [DEBUG] [g.openwebnet.bus.MyHomeJavaConnector] - ##gw-openwebnet-connector## Created MyHomeJavaConnector 192.168.6.42:20000 pwd=140681
2018-07-01 18:55:41.077 [DEBUG] [bnet.handler.OpenWebNetBridgeHandler] - ==OWN== BridgeHandler Trying to connect gateway…
2018-07-01 18:55:41.078 [ERROR] [org.openwebnet.AbstractOpenGateway ] - ERROR IN Java $MODULE$: connection cannot be established
2018-07-01 18:56:01.079 [INFO ] [bnet.handler.OpenWebNetBridgeHandler] - ==OWN== BridgeHandler still unknown. Setting device=openwebnet:bus_gateway:3f676829 to OFFLINE
The debug mode does not give me more details.
I tried a telnet from the linux VM but I have not issue to connect to the host.
telnet 192.168.6.42 20000
Trying 192.168.6.42…
Connected to 192.168.6.42.
Escape character is ‘^]’.
F455 Gateway now works perfect for me. Still having problems with rollershutters but no time at the moment to lokk at it. Command “Set xxx to 100%” works perfect for going down but “Set xxx to 0%” does not effect the rollershutter. The echo says “OK” but nothing happens. Any suggestions?
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
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:
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…)
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?
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.
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)
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).
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.