@mfalkvidd Thanks! Just give me a couple of days and I will try to make a new tutorial for mysensors+openhab.

I think you are right. I have misinterpreted +-3 as +-3% of the value. It seems that is +-3 absolute %RH.

Thanks a lot.

@mfalkvidd said in Ethernet MQTT Gateway Slow to connect:

@guillermo-schimmel wouldn't it be a bit surprising if there is a delay that is only active on your system?

Sure. I'm not meaning that. Sometimes not being an english speaker is tough.

I mean that some combination of settings that I may have done (wrongly?) perhaps generated that delay.

@mfalkvidd that's really great. I'll try. Thank you very much.

@fredswed As far as I know, there isn't a better way. A thing is indeed a phisycal object, and a node groups several of them.

Can I ask you which kind of connection/gateway are you using? I'm strugling with the mqtt gateway and the binding.

Thanks

The combination openhab (2.3)+mqtt (mosquitto)+mqtt gateway+mysensor nodes works perfect end to end.

The rollershutter node, with a small addition to report position works perfect just as-is.

I wouldn't try to do the comms other way than nrf24 (perhaps nrf5x in the future). It's cheap and easy.

If you have some specific question I will be glad to help you. I'm convinced OpenHAB is the best home automation controller, but sometimes can be a little difficult to start things up.

@guillermo-schimmel Well, solved.

Good brands not means good quality.

Replaced my Cisco switch for a unbranded one:

0 MCO:BGN:INIT GW,CP=RNNGA---,REL=255,VER=2.3.1
4 TSM:INIT
5 TSF:WUR:MS=0
11 TSM:INIT:TSP OK
13 TSM:INIT:GW MODE
15 TSM:READY:ID=0,PAR=0,DIS=0
17 MCO:REG:NOT NEEDED
w5100 init
w5100.cpp: detect W5200 chip
Wiznet soft reset
mr=0
w5100.cpp: detect W5500 chip
Wiznet soft reset
mr=0
w5100.cpp: detect W5100 chip
Wiznet soft reset
mr=0
chip is W5100
590 GWT:TPC:IP=192.168.1.200
1598 MCO:BGN:STP
1600 MCO:BGN:INIT OK,TSP=1
1603 GWT:TPC:IP=192.168.1.200
2606 GWT:RMQ:MQTT RECONNECT
2615 GWT:RMQ:MQTT CONNECTED

Connected at the first attempt.

Thank you guys a lot for your time.

It is indeed a little more complex than other solutions, but on the long run I like it because it is so powerfull and stable.

That is another advantadge of MQTT also. You can kind of isolate your devices from the controller. So if I in the future I get tired of openhab, or -hope not- they abandon the development, I could just integrate all the devices over mqtt.

But whatever works its the best solution! Good luck with domoticz!

P.S. if you want to take a look, here is my vacuum cleaner interface, I'm sure it works perfectly for domoticz

https://github.com/guillebot/openhab-sucks

@jimmy-loyens said in openHAB 2.2 binding:

Hello, I just started to use the mysensors binding 2.2 (moving from serial gateway to ethernet gateway to accomadate MYSController) and I have some (maybe stupid) questions I cant find the answers to (I have been poking around the forum though).

First off, I have a whole bunch of the same type nodes: child0=battery/child1=humidity/child2=temperature/child3=lightintensity/child4-9 are digital inputs for doors and windows. Are such nodes supported by the binding, and how to configure them? I can find temperature, humidity and lightlevel nodes in the list (paperUI) but how can i combine these?

Second, can the nodes be automaticly discovered by the binding? In my case i have to add them all manually.

Yes they can. Use the openhab-mysensors-2.4.0-snapshot binding and they will appear.

Third, what are the var1-5 channels for? (is this the answer to my first question?)

Good question. I wonder that myself. When you know it please tell me.

Fourth, what is the difference between the two variable1 channels? in the channel name one says "var1" the other one says "custom"?

Fifth, is there a comprehencive tutorial out there on how to configure the nodes? (I have looked but cant seem to find one)

No there isn't. I think it would be a great idea to write something.

Sixed, when i add any sensor manualy i get a status for it of "UNINITIALIZED - HANDLER_INITIALIZING_ERROR ". The node ID/child ID is online sending data though.

I resolved a lot of those messages by restarting the complete OpenHAB. Not cool, but works.

am i using the latest stable version of the binding? I downloaded it a few weeks ago from eclipse market.

Use this:

http://www.oberfoell.com/openhab2/org.openhab.binding.mysensors-2.4.0-SNAPSHOT.jar

Any help would be appreciated

Absolutely great work! Just discovering the extent of the work done with mysensors. Amazing. Thanks

And of course you should know that the comunication is via "serial protocol", which is defined here:

https://www.mysensors.org/download/serial_api_20

@Guillermo-Schimmel said in Selecting a Controller:

@3nibble https://pypi.org/project/pymysensors/ is a nice starting point.

@3nibble https://pypi.org/project/pymysensors/ is a nice starting point.

@3nibble yes, you can talk directly to the ethernet gateway or, more easily, to the MQTT gateway. I tend to unify all my sensors, mysensors or not, over MQTT.

@Klabbe great! perhaps I'll go back to ethernet gateway. Do you think is better option over mqtt gateway?

I think so. I have a lot of battery powered nodes heavily using smartsleep and they work just fine with MQTT.

@Klabbe great to know. Thanks

Well it seems that there isn't and ther won't be a mysensors binding anymore. It was abandoned by the developer.

So as of december 2020, with OpenHAB 3, the way to go is plain MQTT.

I can't say I disagree really. MQTT is simple and works.

I'm going to start from scratch and try to document my experience here.

@rejoe2 said in sending an image without wifi / envoi d'une image hors wifi:

@Guillermo-Schimmel It indeed should not be to difficult, but still there are some questions to be addressed:

• Is there any common standard (e.g. mark start and end of transmissions with keywords like "START" or "END") in stream messages (other than OTA)?

Not that I know of. I'm afraid you are on uncharted territory now.

• How about multi stream options (different ChildIDs).

Afaik the ony sample transfer code ist this one. Using that as a base, I recently built a (not yet tested) version that most likely will be part of the FHEM integration, so I'd really appreciate some common approach to that topic to not propose a somehow "strange" implementation.

This is a nice implementation.

If it were me, I would try to seek compatibility with MQTT, I mean send the images in some form that they could be decoded by any subscriber to my broker.

But regarding header, start/stop and child id I'm afraid you are going to make your own.

Thanks a lot for this effort, I think it would be useful for a lot of us.

But no answer on that question until now.

@Oitzu Great work. Looking forward to use it. I have a use for this (some remote roof drain that gets clogged with leaves). Thanks!