Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Send a request message using Mysensors bindings

andreground last edited by

Hi guys!

I’m happily using the openHAB connectors to control my sensors through both openhab1 and openhab2.

Today, while I was developing a new sketch, I realized that I needed to periodically send a request message to my sensor to receive back in updated value.

I didn’t find a way to sort this out!

Is there anything I can do to have either openhab1 or 2 managing this?

Thanks in advance!
Reply Quote 0
1 Reply Last reply
TimO Hero Member last edited by @andreground

Hi @andreground !

Have a look at expert mode in the OH2 binding:
https://github.com/tobof/openhab2-addons/wiki/Expert-mode-(rule-based)

This way you may send what you want.
Reply Quote 0
1 Reply Last reply
andreground last edited by @TimO

@TimO

Thanks!
This should fit for OH2!

Do you know if something similar exists also for OH1?
Reply Quote 0
1 Reply Last reply
TimO Hero Member last edited by TimO @andreground

@andreground

I can't help you there, sorry.
Reply Quote 0
1 Reply Last reply

4
Posts

1122
Views

Suggested Topics

OpenHAB MySensors binding 2.5: V_VAR1 and String values
OpenHAB • openhab • • syntacrsc

5

1
Votes

5
Posts

59
Views

I have tried this on my test system and i get the same results as you using the VAR1 -- VAR5 with the cover (RollerShutter) thing. However if you add CustomSensor thing to your node then using the VAR1-VAR5 work as expected with the mapping. With numbers to and from the node. things cover Mock_Cover [nodeId=254, childId=6 ] text Mock_info [nodeId=254, childId=7 ] Items Rollershutter Mock_Cover_State "Mock Cover State [%s]" <rollershutter> (test254) { channel = "mysensors:cover:gatewayWIFI3:Mock_Cover:cover" } Number Mock_Info_Var1 "Mock Info Variable 1 (number) [%s]" (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:var1" } String Mock_Info_Var1s "Mock Info Variable 1 (string) [%s]" (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:var1" } Number Mock_Info_Var1m "Mock Info Variable 1 (number) [MAP(curtains.map):%s]" (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:var1" } String Mock_Info_Var1sm "Mock Info Variable 1 (string map) [%s]" (test254) { channel="mysensors:text:gatewayWIFI3:Mock_Info:var1" [profile="transform:MAP", function="curtains.map"] } Number Mock_Info_Var2 "Mock Info Variable 2 (number) [%s]" (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:var2" } Number Mock_Info_Var3 "Mock Info Variable 3 (number) [%s]" (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:var3" } Number Mock_Info_Var4 "Mock Info Variable 4 (number) [%s]" (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:var4" } Number Mock_Info_Var5 "Mock Info Variable 5 (number) [%s]" (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:var5" } Node #define CHILD_ID_COVER 6 #define CHILD_ID_CUSTOM 7 present(CHILD_ID_COVER, S_COVER, "Roller Shutters"); present(CHILD_ID_CUSTOM, S_CUSTOM, "Reasons"); Or you if you want to send strings you could use String Mock_Info_Text "Mock Info text sting [%s] " (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:text" }
Rule to send message to Node
OpenHAB • • FredRoot

2

0
Votes

2
Posts

605
Views

I came across this post while looking for some information, and I realize this post is quite old, but I wanted to resurrect it for a couple reasons: It looks like OP made a few posts and then never came back since 2018, so maybe they gave up (I know I have been there, more than once). I have come across a lot of posts like this while looking things up and I always find it quite sad that they never so much as received a single reply. There are almost 600 views, so clearly I am not the only one looking for this information. Therefore, @FredRoot, if you read this, just curious if you ever got it sorted. And for anyone else reading, OpenHAB has changed a bit in the meantime, but I am pretty familiar with it, and so I could post a working example should anyone need it. Although this is really more of an OpenHAB question, and therefore perhaps more appropriate for their forums.
OpenhabBinding 2.5 and MQTT
OpenHAB • • Peter Loeffler

1

0
Votes

1
Posts

31
Views

No one has replied
OpenHAB 2.5 MySensors Serial Gateway - How to install
OpenHAB • • FlipFlap3

23

3
Votes

23
Posts

13600
Views

Updated to OpenHAB 2.5 with step-by-step instructions switched to Zulu Java
Openhab 2.5.5, raspberry pi 4 with usb boot ssd
OpenHAB • • CraigDubya

22

0
Votes

22
Posts

41
Views

That's great news! Now back to the fun part! I prefer to have a repeatable, definable failure mode, and then fix that, rather than an unknown success, but that's just me.
openHAB 2.5 binding and V_VARx
OpenHAB • • syntacrsc

4

1
Votes

4
Posts

34
Views

Solved it by changing the definition (typeId) of both V_VAR1 and V_VAR2 in the binding file for S_Cover (.XML file in folder /usr/share/openhab -> org.openhab.binding.mysensors-2.5.0-SNAPSHOT.jar -> ESH-INF/thing/S_Cover.xml) from "var1-channel" resp. "var2-channel" to "cover-channel" (see XML excerpt below). This allows me to setup two additional rollershutter items to control the tilt of the cover blade (V_VAR1 = single tilt and V_VAR2 = tripple tilt at a time) and to send back the position of the tilt blades stored in the node to openHAB. Items: Rollershutter BueroRalphJalousieAufAb "Auf/ab" { channel="mysensors:cover:gateway:BueroRalphJalousie:cover", Rollershutter BueroRalphJalousieTilt "Tilt" { channel="mysensors:cover:gateway:BueroRalphJalousie:var1" } Rollershutter BueroRalphJalousieTilt3X "3x Tilt" { channel="mysensors:cover:gateway:BueroRalphJalousie:var2" } **Binding .XML file in folder /usr/share/openhab -> org.openhab.binding.mysensors-2.5.0-SNAPSHOT.jar -> ESH-INF/thing/S_Cover.xml I changed from: <channel id="var1" typeId="var1-channel" /> <channel id="var2" typeId="var2-channel" />** to <channel id="var1" typeId="cover-channel" /> <channel id="var2" typeId="cover-channel" /> like this: <thing:thing-descriptions bindingId="mysensors" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0" xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0 https://openhab.org/schemas/thing-description-1.0.0.xsd"> <thing-type id="cover"> <supported-bridge-type-refs> <bridge-type-ref id="bridge-ser" /> <bridge-type-ref id="bridge-eth" /> <bridge-type-ref id="bridge-mqtt" /> </supported-bridge-type-refs> <label>RollerShutter</label> <description>RollerShutter</description> <channels> <channel id="cover" typeId="cover-channel" /> <channel id="var1" typeId="cover-channel" /> <channel id="var2" typeId="cover-channel" /> <channel id="var3" typeId="var3-channel" /> <channel id="var4" typeId="var4-channel" /> <channel id="var5" typeId="var5-channel" /> <channel id="battery" typeId="battery-channel" /> <channel id="lastupdate" typeId="lastupdate-channel" /> </channels> <config-description> <parameter name="nodeId" typ... mySensors code (excerpt): // Prepare Messages: Jalousien[i - 1].MessageStatusAufAb.setSensor(Jalousien[i - 1].RaumNummer); //ChildID Jalousien[i - 1].MessageStatusAufAb.setType(V_PERCENTAGE); //UpDown-Position Jalousien[i - 1].MessageStatusTilt.setSensor(Jalousien[i - 1].RaumNummer); //ChildID Jalousien[i - 1].MessageStatusTilt.setType(V_VAR1); //Tilt-Position Jalousien[i - 1].MessageStatusTilt3X.setSensor(Jalousien[i - 1].RaumNummer); //ChildID Jalousien[i - 1].MessageStatusTilt3X.setType(V_VAR2); //Tilt3x-Position ... ... // Neuen Zustand an Controller melden / Send cover and tilt positions back to controller: send(Jalousien[i - 1].MessageStatusTilt.set((Jalousien[i - 1].StatusTilt / Jalousien[i - 1].TiltSchritte), 2), false); send(Jalousien[i - 1].MessageStatusTilt3X.set((Jalousien[i - 1].StatusTilt / Jalousien[i - 1].TiltSchritte), 2), false); send(Jalousien[i - 1].MessageStatusAufAb.set(Jalousien[i - 1].StatusAufAb, 0), false); Make sure to send the V_PERCENTAGE last since V_VAR1 and V_VAR2 for some unknown reason (and as far as I feel totally unnecessarily) still updates V_PERCENTAGE! Result:
MySensors --> MQTT --> OpenHab 2.5
OpenHAB • • P72endragon

15

0
Votes

15
Posts

118
Views

@P72endragon said in MySensors --> MQTT --> OpenHab 2.5: Thanks for the additional information Well since you replied I took another scan over the thread. @P72endragon said in MySensors --> MQTT --> OpenHab 2.5: native OH MQTT I have been fairly involved over at OpenHAB forums (on and off; and I read a great deal in general) and the consensus amongst those in the know (last time I checked) seemed to be to use independent, outside MQTT broker. Personally I subscribe to "Unix philosophy" and since going the MQTT route have always run Mosquitto, but it was nice to see others confirming what I had suspected all along (that OpenHAB was trying to "do too much" with their built-in broker). @P72endragon said in MySensors --> MQTT --> OpenHab 2.5: I don't mind not having auto-discovery [...] (although I'm not sure I understand quite how it works yet, still a little unclear on Items, Channels, etc) Getting your head around theOpenHAB concepts is one thing. Just try to imagine what it would take if you were designing a system from the ground up to abstract away a bunch of different incompatible systems into one unified control system, and you will be well on your way to understanding it. Thankfully their docs are very good and their forums are very active, including lots of examples. But main thing I wanted to touch on was config in text files vs. PaperUI. If you don't care about auto-discovery I can highly recommend the former. IMO, the PaperUI hides too much stuff from you, and I don't like that. All entries in there actually go into some internal database which you cannot edit (other than through PaperUI) and exists in parallell to your text files (which you can have in addition). So, what happens 2 years from now when you go to upgrade or install on a new system? Yeah good luck remembering what you did in PaperUI that you now need to re-do, in addition to all your text files which you already have. I read a lot of forum threads along such lines, and/or broken stuff after upgrades, etc... So for me, this time around, I spent the extra time doing complete text file configuration from scratch. And now I have a completely reproducible set of text files that I keep in version control and backed up. I could wipe the system and re-install no problem. As another upside, you really get to know the ins and outs of the system that way. In closing I will say that my MySensors Ethernet/MQTT gateway -> OpenHAB has been working flawless, and so to me appears to be the way to go. Come on in, the water is fine! I actually even run the Mosquitto broker on a separate box from OpenHAB, it was designed from the ground up to be a network based architecture, so it really doesn't matter. In fact I don't even use MySensors binding in OpenHAB at all. Once you get over initial config (which is the challenging part) I believe it is actually the much better way to go. Which is another reason why I wanted to post this, as there is too much conflicting, old, and bad information out there on the Internet about this subject. That way no more relying on an outside party (MySensors binding developer(s)) for anything. They seem to me a bit overwhelmed (at least in the past). Not knocking them in the least, in fact I applaud their efforts. However personally I decided to remove that dependency from my system and it has proven to be a good decision. I would love to hear back from someone who is happy with their MySensors 2.5.x binding in OpenHAB. So if that is you, please speak up (and tell us your secrets! )! I personally haven't seen any of those posts though, unfortunately... Anyway, post back whenever you get to that point, and I will be happy to share some up to date config snippets (or anyone else reading along). I was going to post mine but I just looked at them and realized they need some cleaning up first. Sorry!
Is V_RGB Supported in OpenHAB?
OpenHAB • • Aloha

3

0
Votes

3
Posts

29
Views

Thank you @hard-shovel! It works. It doesn't store the value between reboots but I guess that's a different topic which I will look into. Cheers

Send a request message using Mysensors bindings

Suggested Topics

OpenHAB MySensors binding 2.5: V_VAR1 and String values
OpenHAB • openhab • • syntacrsc

Rule to send message to Node
OpenHAB • • FredRoot

OpenhabBinding 2.5 and MQTT
OpenHAB • • Peter Loeffler

OpenHAB 2.5 MySensors Serial Gateway - How to install
OpenHAB • • FlipFlap3

Openhab 2.5.5, raspberry pi 4 with usb boot ssd
OpenHAB • • CraigDubya

openHAB 2.5 binding and V_VARx
OpenHAB • • syntacrsc

MySensors --> MQTT --> OpenHab 2.5
OpenHAB • • P72endragon

Is V_RGB Supported in OpenHAB?
OpenHAB • • Aloha

170
Online

9.5k
Users

10.1k
Topics

105.2k
Posts

Send a request message using Mysensors bindings

Suggested Topics

OpenHAB MySensors binding 2.5: V_VAR1 and String values OpenHAB • openhab • • syntacrsc

Rule to send message to Node OpenHAB • • FredRoot

OpenhabBinding 2.5 and MQTT OpenHAB • • Peter Loeffler

OpenHAB 2.5 MySensors Serial Gateway - How to install OpenHAB • • FlipFlap3

Openhab 2.5.5, raspberry pi 4 with usb boot ssd OpenHAB • • CraigDubya

openHAB 2.5 binding and V_VARx OpenHAB • • syntacrsc

MySensors --> MQTT --> OpenHab 2.5 OpenHAB • • P72endragon

Is V_RGB Supported in OpenHAB? OpenHAB • • Aloha

170Online

9.5kUsers

10.1kTopics

105.2kPosts

OpenHAB MySensors binding 2.5: V_VAR1 and String values
OpenHAB • openhab • • syntacrsc

Rule to send message to Node
OpenHAB • • FredRoot

OpenhabBinding 2.5 and MQTT
OpenHAB • • Peter Loeffler

OpenHAB 2.5 MySensors Serial Gateway - How to install
OpenHAB • • FlipFlap3

Openhab 2.5.5, raspberry pi 4 with usb boot ssd
OpenHAB • • CraigDubya

openHAB 2.5 binding and V_VARx
OpenHAB • • syntacrsc

MySensors --> MQTT --> OpenHab 2.5
OpenHAB • • P72endragon

Is V_RGB Supported in OpenHAB?
OpenHAB • • Aloha

170
Online

9.5k
Users

10.1k
Topics

105.2k
Posts