@doctor64 it is enough, I can replicate it. Thanks for reporting this issue :smile: . You can keep track of it here: https://github.com/tobof/openhab2-addons/issues/97

Hi @doctor64, could you please post your things configuration file?

@mick you aren't the first asking that :sweat_smile: . I opened a new issue on GitHub (https://github.com/tobof/openhab2-addons/issues/95) to discuss about adding it to the binding.

@philro @nofox
We are discussing this issue on GitHub. Probably we have found the problem and a possible, temporary, solution. If you can try it it would be useful, thanks! :blush:

@RVMRVM

Did you run feature:install openhab-transport-serial, on OH console?

Just few posts before 😉

@TimO said in openHAB 2.0 binding:

@Nicklas-Starkel Well no, MQTT Gateway is not yet supported. :-(
I got distracted by my current hardware project and need to catch up on the binding. First tests of the MQTT addition to the binding look very promising and I'll include it soon.

The current release is this one: http://www.oberfoell.com/openhab2/org.openhab.binding.mysensors-2.1.0-SNAPSHOT.jar

While preparing the code to be included in OpenHAB2 I'm currently changing some things that will break the current configuration / things files. But I will give some information about that with the release of the next version.

Hi @gonzalonal :smiley:

In the new version of binding we have implemented a (beta-)function that allows you to send heartbeat message at certain interval without the need to write your own rules.

Please take a lock at this gateway-parameter (you must have set enableNetworkSanCheck=true and sanityCheckerInterval).

With sanCheckSendHeartbeat parameter set you could also use this node-parameter to put your nodes offline after a certain number of failure.

I hope this function will help you!

@Alpoy check this discussion on GitHub. The question is still open.

@antonholmstedt reconnection is currently implemented in binding (look here). Feel free to open an issue if you experience reconnection fails in your environment :smiley:

@AndrewZ things file update trigger a reload of all binding declared inside it, nothing strange. ;) Follow the above link to keep track of the status of this issue.

Hi @AndrewZ , yes this is a known issue (I just openend an issue here) with the binding. Just out of curiosity, have you changed something in things file?

Hi @LastSamurai , currently Timo is working on MQTT gateway but I don't know precisely when it will be available to all.

@TimO said in openHAB 2.0 binding:

@Fabien Thank you for your feedback!
And: I've waited for that question according firmware updates to come up. :-D

I've looked into it and I'm very interested but till now there is only the implementation in the library, I've not seen an implementation in a binding. I'll continue to look at it, but with low priority. :-)

Current priority list is:

1. Include binding in OH2 repository.
2. Test and include the big refactoring from @andreacioni .
3. Add MQTT gateway (proof of concept working, full integration after refactoring).
4. Add little feature requests, add sensors ...

Hi @carlyler :)

what version of JVM are you using? 1.7 or 1.8?

Hi @Gustafsson,

Have you read the readme? Readme . Probably you have not configured things? See the readme on how to do that :)

Hi @gonzalonal

The implementation of the binding create a thing for every channel of a single node. So the solution result is what you can see in the log. We can do a little bit more to prevent a single message to fire every 'lastupdate' channel of every thing that have the same node ID. But I think it is not a good idea.

@Denke yes acknowledge is actually implemented in binding :)

Hi @kolaf, yes this is how to do it. But my idea is to integrate the datetime channel into the binding in order to automatically update that value when updates are received. I think is better than have to do rules into OH config for each devices. What do you think?

Hi @TimO ! I want to tell you an idea for the OH2 binding. What do you think about adding a date time channel to every thing that hold the last communication of the thing with the gateway? For example, it will be useful if you want to notify user that some sensors have become unavailable. Tell me what do you think! :)

Hi @TimO, me and @undee have tested everything (thanks again!). I'll push a little PR on github to fix a problem found in I_TIME response.

@kolaf Perfect! ;)

@kolaf Could you try link the serial port to another name (ln -s /dev/mysensorsUSB /dev/ttyS80)