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" }

@TimO Yes, but without this message: 2020-01-07 16:23:52.050 [INFO ] [rsAbstractConnection$MySensorsWriter] - ACK received for message: 0;0;1;1;2;1

By creating the file org.eclipse.smarthome.mqttbroker.cfg in the service folder (/usr/local/etc/openhab2/services in my case, chown to openhab), with the contents name=mosquitto host=192.168.1.69 secure=false port=1883 username= password= retain=true I was able to just create the MySensors MQTT gateway (using paperui) and it stayed online (no mqtt broker defined, but its addon is installed). I had the impressions that with the latest versions it should be possible to do everything in the PaperUI, and that the broker would use the mqtt2 addon (but in paper ui, service, config, mqtt tab, mqtt system broker connection, manage->plus button -> expert mode, I get to see the contents of the cfg file above) But unfortunately, it seems that the discovery services enters a endless loop (maybe I need to update my arduinos sketch to the latest mysensors code?) and I don't get any auto discovered things. If I trigger a new discovery it will stop the previous one and start again. Finally, I was able to manually create a thing, and link items on it. Eventually my battery level and humidity were displayed in the paper ui control page (after some weird delay, not updating once it shows in the log. the temperature didn't show up though). Not sure if my understanding is off (or paperui is limited in this sense) but in the "thing" creation page I only get to specify one child id. Then my multi sensors/value nodes would need to be define in multiple things? As I can't properly define channels for each child id, and I'm not sure what var1-5 are all about. I'll try defining things/channels/items directly in files in the following days, because so far I couldn't enjoy most of the benefits of this new version (auto discovery, logical grouping of physical device in "things", questionable "do-it-all in paper ui"), and I'm almost considering using mqtt1 binding in the new install :(

Hi @neelam, welcome to the forum! The dimmer example should work. If you want to use only the esp8266 with wifi (no nrf/rfm or other radio), you'll also need to add gateway settings from https://www.mysensors.org/build/esp8266_gateway

@gohan thanks, however the issue i'm having is not in the HVAC implementation, but in the messaging..

@George-Laynes said in OpenHAB 2.1 keeps showing light level as 0 with BH1750 and V_LEVEL: Any idea on how soon it'll be available for general public? Very soon. The next release is finished in the next days. But it will not be backwards compatible because there was a change in the naming of the parameters, for example: skipStartupCheck is now named startupCheckEnabled, so I need to think about migration options.

Nice. Didn't know that. But still it would be a great feature for the gateway to give every one the feature of smartSleep despite the controller.

I'd say it is the same but it would you will need to do more coding I guess. There is a node-red Google group if you want to ask there also.

I liked domoticz (was very easy to set up and use). Together with dzVents scripting wasn't that difficult either. But I also had some problem with it lately, so I was actually thinking about switching to openhab (2).

Hi and welcome to the MySensors community @augusthalverson ! In general, you just set the color in your controller. It works the same way regardless of which type of gateway you are using, so there is nothing specific about mqtt. You might be able to get some inspiration from https://forum.mysensors.org/topic/4934/wall-mounted-mood-light-v2

@Eric-Buhring I found that changing the line in the my sensors program that sends the message as below allowed me to use a Contact rather than a Switch if (value != sentValue2) { // Value has changed from last transmission, send the updated value send(msg2.set(value==HIGH?"OPEN":"CLOSED")); sentValue2 = value; }

@Eric-Buhring great to hear that you managed to get it working. I have used solution like this (arduino+eth. shield+rf24) for some time. Now I have switched to esp8266+rf24(version with antenna) as a gateway, it is a cool (and smaller) solution

@epierre said: I had the contact with this seller, but an international money transfer was needed and is expensive... yeah, they also have a minimum order quantity and ship with DHL only, so you have to pay import taxes to EU so it only makes sense if you order a big quantitiy and then try to resell it somehow :) all in all a hobby that at least has some return on investment, compared to other ones i had :)) You're courageous th have gone on kickstarter, from memory seeedstudio nearly went down because of an error on a crowdfunding project and had to produce and ship (the more expensive par of it) a remlacement for the first batches... ahh .. i didnt know this about them... and in their scale - i can undertand it happened to me as well but in my scale it was rather a paid lesson :))))

@micah said in Can't get OpenHAB2 to see my MQTT messages: I'm still not sure if the second and third line in the mqtt-eventbus.cfg is correct. I don't have MyMQTT anywhere else, so I think I may try different combinations to see what works. MyMQTT should be replaced with brokername (mysensors in this example). openhab will then publish the event to the mqtt broker on its topics (useful if you use f.eks. node-red for openhab rules)

@UglyKidJoe I have been using OpenHAB and MQTT for a number of years now. The reason for using MQTT and not just a serial connection from the MySensors GW is partly the flexibility as many have stated previously here. Easy to test, using e.g. the mqtt.fx tool. If you want to know what is going on you simply connect to the MQTT stream and "snoop" on the messages. Another reason is that I am running three geographical sites on one OH installation. OH is running on a NUC at my home. There is also an MQTT GW here. Two other My Sensors MQTT-GW are running remotely in two summer houses. The three GW connect over internet to a cloud-based MQTT broker and OH connects to the same broker. In that way I do not have to open any ports into my home network for access should I have had a local MQTT-broker at home.