openHAB 2.0 binding

andreacioni

This kind of problem (as I've read online) in this release of OH seems to be not only related to this binding. One suggestion that I found is here: https://github.com/openhab/openhab-distro/issues/82 (last comment) or here: https://github.com/openhab/openhab-distro/issues/81

I've tested it without success but I don't know if I've done it right. I've also try to build myself a rfxcom binding (this one use gnu.io) and it has the same issue

hope this help

EDIT: this work for me, run on OSGI console: feature:install openhab-transport-serial and restart OH

gonzalonal

@andreacioni said:

This kind of problem (as I've read online) in this release of OH seems to be not only related to this binding. One suggestion that I found is here: https://github.com/openhab/openhab-distro/issues/82 (last comment) or here: https://github.com/openhab/openhab-distro/issues/81

I've tested it without success but I don't know if I've done it right. I've also try to build myself a rfxcom binding (this one use gnu.io) and it has the same issue

hope this help

EDIT: this work for me, run on OSGI console: feature:install openhab-transport-serial and restart OH

Hi @andreacioni.

You saved the day. It worked for me.
Here the steps I did to make it work.

1- Download latest snapshot from https://openhab.ci.cloudbees.com/job/openHAB-Distribution/ (Download offline version)
2- Unzip the file.
3- Run start_debug.sh
4- In console write "feature:install openhab-runtime-compat1x"
5- Ctrl-D to exit/shutdown OpenHAB
6- Once exited, copy MySensors binding to addons folder.
7- Start againg OpenHAB-
8- Thats it. It should work

Remember to copy your serial thing to things folder.
Regards!
Gonzalo

TimO

@andreacioni: Absolultly amazing! Thanks!

I don't understand why this helps though because the changes in the code I have to do have nothing to do with OH1 (compability).

I hope to provide an adjusted version today or tomorrow along with a clean and working repository.

Thanks for your patience! :-)

andreacioni

@TimO I'think the OH1 compatibility is not the problem. It seems that OH2 beta1 have not installed transport feature and so it has no definition for the gno.io pakage, so I'think there's nothing to do on your code :D

PS tell me when the new repo is OK that I download it and try to add the baudrate config ;) Thanks!!

TimO

So, I would like to show you my current status. I've tested it against my mini MySensors environment and it looks good so far. Feel free to test.

Download latest snapshot from cloudbees: https://openhab.ci.cloudbees.com/job/openHAB-Distribution/lastSuccessfulBuild/artifact/distributions/openhab-offline/target/openhab-offline-2.0.0-SNAPSHOT.zip
Unzip file (into a directory like oh2).
Download the current binding from Binding and place it in the addons directory under oh2.
Configure addons, things, items and sitemap. Example?! addons.cfg, demo.things , demo.items, demo.sitemap
Start "start_debug.sh", "start_debug.bat" ...
In the karaf console enter: "feature:install openhab-transport-serial".
MySensors Plugin "should" start. ;-)

8: "log:set debug" + "log:tail" to see debug output.

Github and documentation will follow, please refer to the "old" Readme and the examples.

andreacioni

@TimO Hi Tim, for debugging outupt of the binding I need to write: log:set DEBUG org.openhab.binding.mysensors, without this I cannot see anything about binding logs

gonzalonal

@andreacioni Hi andreacioni. Same issue with debug mode with me. Thanks for the tip!

@TimO: V_STOP for Rollershutter sensors, is a MySensors binding limitation, or it is not implemented in OH2 yet?

Another thing I've noticed is that every item added, despite being a regular switch or a rollershutter, is is being added as:

Battery Level
mysensors:cover:gateway:Cover_1_0:battery
MySensors Battery Channel

Is this the intended behavior for every node of my sensor, despite having or not a battery?

Regards.
Gonzalo.

TimO

@gonzalonal said:

V_STOP for Rollershutter sensors, is a MySensors binding limitation, or it is not implemented in OH2 yet?

It is a limitation of OH2 and I don't understand the limitation. It is very confusing, because with the "RollerShutter" widget in OH2 I get three buttons: UP, DOWN and STOP. UP and down calls the handler in which I generate the MySensors message. STOP don't call the handler and therefore I can't do anything. I need to dig deeper.

Battery Level
mysensors:cover:gateway:Cover_1_0:battery
MySensors Battery Channel

Is this the intended behavior for every node of my sensor, despite having or not a battery?

This is intended behavior. The battery status is send via an internal message and there is no presentation if a sensor has a battery or not.
I've therefore added the battery channel to every item. In Paper UI you are able to simply disable the channel by clicking the blue circle next to the battery channel or in the configuration file you have to specify the channel, if you want to use it. If the battery channel is not defined for a thing it won't receive the battery status.

For the future: maybe there is a way to hide the channel as long as there was no battery status received and display it only when used. But currently I don't see an easy way to implement that.

Greetings!
Tim

gonzalonal

@TimO
Great TimO. Thanks for clarifying this topic.
Regards.
Gonzalo

TimO

@gonzalonal : I found a solution for V_STOP! It will be available soon.

But more important: @andreacioni is doing some great work improving the stability and performance of the binding!!

I just wanted to let you know, that the binding is currently under heavy development. :+1:

gonzalonal

@TimO
Great news TimO. Really nice to hear that.
Regarding STOP functionality for the binding, I have read somewhere that the supported commands by OpenHAB, for RollerShutter items, are Up, Down and StopMove. Have yoy tried something like this?

Regards
Gonzalo.

TimO

@gonzalonal said:

Regarding STOP functionality for the binding, I have read somewhere that the supported commands by OpenHAB, for RollerShutter items, are Up, Down and StopMove. Have yoy tried something like this?

Yeah, my problem till yesterday was, that I was not able to cast the given state to StopMoveType in case of Stop, while casting the state to UpDownType for Up and Down was no problem. :-)

I changed the way how the binding handles this type of message and it works now.

Sebastián Zaffarano

@TimO
Can we clone the latest source code from this binding? I think that your github repository is outdated and I want to work this weekend with it, 'cause I would like to integrate the mysensors 2.0-beta "smartSleep" feature with your binding in my home sensors setup (ESP8266 Ethernet GW).

Also, if there are any ISSUE y your TODO list in which I can help you, please tell me.

Regards

andreacioni

@Sebastián-Zaffarano

Hi Sebastián, what repository have you checked? Currently the development is not on the old https://github.com/wishmoooop/openhab2/tree/master/addons/binding/org.openhab.binding.mysensors but was moved here: https://github.com/tobof/openhab2-addons/tree/MySensors/addons/binding/org.openhab.binding.mysensors

Hope this help :)

Sebastián Zaffarano

@andreacioni said:

@Sebastián-Zaffarano

Hi Sebastián, what repository have you checked? Currently the development is not on the old https://github.com/wishmoooop/openhab2/tree/master/addons/binding/org.openhab.binding.mysensors but was moved here: https://github.com/tobof/openhab2-addons/tree/MySensors/addons/binding/org.openhab.binding.mysensors

Hope this help :)

Thanks @andreacioni
I was working on the old repo! :)

TimO

I've updated the first posting in this thread. You'll find the current repo there (also). ;-)

I've added a Wiki to the repo and made a brief description of the installation and configuration process.

https://github.com/tobof/openhab2-addons/wiki

The current binding (jar) is also in the repo now. You'll find the link in the wiki under "Installation".

Modifications in the current version:

RollerShutter now supports STOP
Performance of the binding improved. Big thanks to @andreacioni !!
Stability improved. Also big thanks to @andreacioni
Error handling on connection loss improved
The baud rate of the serial gateway is now adjustable. (@andreacioni again!)
some code cleanup: removed not needed debug output etc.

Please let me know if you found the time to test the binding and what the results are. :-)

Sebastián Zaffarano

@TimO said:

I've updated the first posting in this thread. You'll find the current repo there (also). ;-)

I've added a Wiki to the repo and made a brief description of the installation and configuration process.

https://github.com/tobof/openhab2-addons/wiki

The current binding (jar) is also in the repo now. You'll find the link in the wiki under "Installation".

Modifications in the current version:

RollerShutter now supports STOP

Performance of the binding improved. Big thanks to @andreacioni !!

Stability improved. Also big thanks to @andreacioni

Error handling on connection loss improved

The baud rate of the serial gateway is now adjustable. (@andreacioni again!)

some code cleanup: removed not needed debug output etc.

Please let me know if you found the time to test the binding and what the results are. :-)

Thank you @TimO !
This weekend I started migrating from my OH1.8 + mqtt GW setup to OH 2 beta + your binding. At the moment all is working fine, I spent some time learning about OH2 / Eclipse smartHome and watching your code, because I want to implement the smartSleep feature (https://github.com/mysensors/Arduino/pull/271) in the mysensors binding.

My idea is: when the handler don't receive an ACK from a message, it store the message for a while, waiting a heartbeat from a node, and, if the binding has some message stored for this node, then send it again. I don't know if this is correct, or if you thinks there is a better solution.

Regards

TimO

@Sebastián-Zaffarano said:

This weekend I started migrating from my OH1.8 + mqtt GW setup to OH 2 beta + your binding. At the moment all is working fine, I spent some time learning about OH2 / Eclipse smartHome and watching your code, because I want to implement the smartSleep feature (https://github.com/mysensors/Arduino/pull/271) in the mysensors binding.

My idea is: when the handler don't receive an ACK from a message, it store the message for a while, waiting a heartbeat from a node, and, if the binding has some message stored for this node, then send it again. I don't know if this is correct, or if you thinks there is a better solution.

That sounds like a good plan. The binding already uses a queue where messages that should be send are buffered and you are able to specify how long a message is hold in the queue (when it is time to send again).

I've already implemented a mechanism to request for an ACK message. This mechanism sends a message to the node, but holds this message in the queue and increments the number of retries (currently 4 retries, with different/longer delays). If the node responds with an ACK or the number of retries exceeds 4 the message is removed from queue. So you could indicate, with a configuration setting, that the node is an smartSleep node and thus only send the message once and if no ACK is received store the message for 10 minutes (for example) in the queue.

Here is the implementation: https://github.com/tobof/openhab2-addons/blob/MySensors/addons/binding/org.openhab.binding.mysensors/src/main/java/org/openhab/binding/mysensors/protocol/MySensorsWriter.java

BUT: The reader and the writer are working in different threads (asynchronus), so we have to sync the threads (the queue), if we receive an ACK and remove a message from the queue. I'm still struggling with that and that is the reason why the request for ACK should not be used at the moment and this will be a problem for smartSleep too.

According to the ACK feature: if the binding don't receive an ACK after 4 timeouts it will revert the status of the thing to the last value. So if you for example try to switch on your light and the message is not acknowledged, the binding will revert the switch state to off. I've removed the code for this, because of the issue above, but will add it again in the future.

AndrewZ

Hello everyone

I'm testing MySensor Ethernet gateway with a relay code on it. My understanding that Gateway stores the current state of the relay (or GPIO port) in it's EPROM. Can the binding periodically check the state of the port or should I rely on OH persistence functionality? Please advise what is the right way to keep the states synced between the Gateway and OH.

Thanks
Andrew

TimO

Hi Andrew!

Good question. Polling is currently not supported by the binding itself, but what you could do is: send a message from the node to the gateway, when the node restarts (the moment after you read the EEPROM and set the output of the pin).

Greetings
Tim

openHAB 2.0 binding

16

11.7k

11.2k

113.0k