@Nathan-Matos Clearly you are a quick study and have made great progress in a short time. Let us know if you need anything else.

@Koresh I do like it, i just worry for people that use their main PC as a controller. Easily knockable/damageable unless they use a rear socket.

Yes, a release is coming. But we haven't set any date yet. Suggest you install it manually.

@atilla-y Orange Pi is a controller and not a gateway. If you are suggesting you want to use the 5v adapter to power both controller and gateway I can not answer you. It might work but in the same time it might be to weak or to much interference. Try! If you get alof of random freezes and/or bad network communication you might want to seperate them It might work - but using the nrf24l01+ amplified requiers some more juice than then pro mini/uno/nano can handle so I suggest using a power in with a good voltage regulator (that can provide high current) and then split of to each unit.

Hi @berkseo. Thanks for the suggestion, but could you describe in more detail? As for my TODO list, there is already a task to add 485 interface to the gateway. My latest device "xRoom" have this interface. ps/ Where have you gone? I have been working on "xRoom" shield. A small announce: [image: 1562049826169-5e44feda-bb1e-4a93-b30a-0bc99a201ee5-image-resized.png] Do you remember the discussion about multinode? So, it will be available soon))

@EddyG PCB received and tested, new version (v1.1) available here and on github.

Okay, finally got the original nrf24l01 SMD modules with the square chip visible... As exptected, things work just fine now, so the culprit of my issues was really the incompatible/fake "nrf24l01" SMD modules with the epoxy blob. If you want to use normal nrf24l01+ modules together with this smd gateway, DO NOT USE the smd module with the epoxy blob, as they won't work. Using only the fake SMD modules might work, too, but mixing the fake modules with real ones does not work.

@micah said: @sundberg84 said: Hard to say. St:fail generally means that you don't get ack from the receiver. This is normally range, power or hardware. There is not a general fix for this but you need to try and learn... i admit its strange I worked for some days. Maybe a radio fried ? Don't have the radios to close to eachother. Try a.couple of meters. Sorry I'm out of more solid ideas. Hey sundberg84, quick question for you. If you look at my debug logs above it looks like the gateway is infact receiving the message but the node thinks it fails. Con you confirm my interpretation of the following two lines? NODE DEBUG send: 42-42-0-0 s=1,c=1,t=0,pt=7,l=5,sg=0,st=fail:20.0 GATEWAY DEBUG 0;255;3;0;9;read: 42-42-0 s=1,c=1,t=0,pt=7,l=5,sg=0:20.0 If that's correct, could that change what the issue might be? Yes, I saw that - it seems to work one way but the ack (return) does not reach back. So its on the edge. But this should update the value in your controller.

@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.

@hek That was very visible, please excuse my ignorance. Even though I have looked at this page I managed to leave the change unnoticed.

Now the RPi based on a new install of Raspbian Jessie, OpenHab 1.8.0 and Mosquitto is up and running and the ESP8266 MQTT client does connect without any problems. I have not changed anything in the code but Mosquitto is now based on the RPi repository for Jessie and not the mosquito_wheezy one. That seems to have fixed it so those versions are likely different but I have not put any time into checking this.

@Tmaster You give each sensor a child id (0-254) in the node.

I'll update the PDF once I get to my own computer (which should be Sunday evening)

Understand it might be annoying.. We run the latest version of the notif-plugin mentioned above (0.3.1). So it seems they still have some issues. They had an issue (which is closed) that sound like the things you experience. I can't seem to find any related user setting in my account either. https://github.com/psychobunny/nodebb-plugin-desktop-notifications/issues/19

thx for reply :smile: yes dragino HE works like yun I think. for linkit as the product seems new, there is a little bit less docs. but I will see, price was so interesting that it was too much tempting lol. I will tell you what I can get... for fun, I have not presented yet, but I have a board in progress for raildin : 8x relays + 8inputs for yun and I added ethernet connector+hub usb chip

@marceltrapman when you change the BAUD rate setting in the source/config file to something lower/other you can also use 3.3V Arduinos as (Serial)Gateway. Of cause your controller needs also to be told about the lower BAUD rate. Check out http://wormfood.net/avrbaudcalc.php?postbitrate=9600&postclock=8 for an overview of Clockspeeds (usually 8MHz for 3.3V and 16MHz for 5V types) and coresponding BAUD rates.

I think the something about order of initialisation was changed that fixed this problem. Try 1.4.1