@bgunnarb I like @eiten 's solution for you. Personally, I am not a fan of using cloud/public brokers. Thus I am curious about your system and there is something about it from which I can learn. I would like to understand why you cannot deploy your own mosquitto broker. I see your set up as 3 sensor groups defined by the channel used #define MY_RF24_CHANNEL ChannelOfSensorGroup Each sensor group has some number of sensors and one MQTT GW on ESP8266. On the MQTT side, do you distinguish between gateways by using a different host name? Something like: #define MY_MQTT_PUBLISH_TOPIC_PREFIX "mygateway-nOf3-out" #define MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "mygateway-nOf3-in" #define MY_MQTT_CLIENT_ID "mysensors-nOf3" #define MY_HOSTNAME "ESP8266_MQTT_GW_nOf3" //#define MY_CONTROLLER_IP_ADDRESS 192, 168, 178, 68 #define MY_CONTROLLER_URL_ADDRESS "test.mosquitto.org" #define MY_PORT 1883 I must assume your controller (aka Home Assistant) discriminates between through which gateway the data is to flow by way of the different topic names. If my "something like" is correct, then changing brokers is changing the IPaddress/URL in your gateways and in your controller (though if the controller is Home Assistant, it may be a bother because the device-id's may change which will make a mess of all the work you've done in HA. This is why I like @eiten 's solution.) I hope it's all working for you again. OSD

@OldSurferDude well, the ESP8266 is limited to 4 TCP clients in arduino IDE. This can't be really increased. I did som experiments and you can set it up to 15, but after the 5th client on my web server, I got a freeze. Maybe you got something wrong. #define MY_GATEWAY_MAX_CLIENTS 2 defines how many controllers (eg Home Assistant) can connect to the gateway, not how many sensors/MySensors devices. And yes, you can have multiple TCP gateways in HomeAssistant. I got an NRF24, an RFM95 long range and a RFM95 short range gateway (all based on ESP32) on the same Home Assistant. Regards, Edi

Still, there seems to be 'someting rotten in the state of Network' where my LAN is concerned. Although the Arduino serial monitor says: 13:03:55.821 -> connected with XXX, channel 6 13:03:55.868 -> ip:192.168.178.4,mask:255.255.255.0,gw:192.168.178.1 13:03:55.915 -> ip:192.168.178.4,mask:255.255.255.0,gw:192.168.178.1 13:04:04.826 -> pm open,type:2 0 when I ping the IP-address I get: Pinging 192.168.178.4 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.178.4: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), When I use the tool 'Wireless Network Watcher' I do see that a device is connected at 192.168.178.4 with the correct MAC address. However, when I look at the management page of my FritzBox 7490 modem/router no device is mentioned at 192.168.178.4. I remain at a loss here.

@kimot Thank you for your comment & tips.

Ok, no help here.

I think these look very interesting to do with small children may be able to stimulate their curiosity, the current video games are too much influence on children, occasionally the family together to do their own small games is a new experience.

First batch of devices arrived. Looks fine. I hope I will manage to install it in garden to the end of the week.

Advantage of this sensor is fast and easy installing by the non qualified personal. The sensor is designed for large agriculture facility with many greenhouses where is needed to be controlled temperature and humidity, the atmospheric pressure is for control the motor of air inlet and outlet. With help of the sensor installed outside the greenhouse provide information about positive/negative pressure inside the greenhouse. Finlay the software read accurate temp/humid value of the Si7021, and only atmospheric pressure of BMP180, the temperature sensor inside the BMP180 is used only by the sensor itself to provide accurate atmospheric pressure measurements. The sensor can be used also for home automation, and drone applications where is needed correction of the UAV barometric sensor compared to the ground barometric sensor, also humidity measurement can help the pilot to calculate more accurate flying time.

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

Hi, General description is available on english version. Sorry for bad translate.

Is this design for some existing enclosure?

what version of esp8266 definitions are you using?

After upgrading Wemos from 2.3.0 to 2.4.0-RC2 version, OTA works well know

@Alan-Minor said in Small nRF24L01+ Shield for ESP8266 Wemos D1 Mini: @NeverDie "Move" the trace to a different pin. AFAIK, yes.

Sorry. Disregard.

@gohan Indeed... See e.g. my experience here: https://forum.mysensors.org/topic/2890/chinese-rubbish-or-is-it

I am not able to install the Library . I am getting Error Invalid library found in C:\Documents and Settings\User\My Documents\Arduino\libraries\ESP8266MQTTMesh: C:\Documents and Settings\User\My Documents\Arduino\libraries\ESP8266MQTTMesh. I changed the name of the zipped file to ESP8266MQTTMesh as the name of .cpp file ESP8266MQTTMesh.cpp. Still it is saying Invalid Library found in .... What could be the problem.

@Roland-Wijnen Hi! Were you able to compile the available files? I tried, but there has been a lot of error!

Does it work also with I2C stuff connected to it?

good, give it a try

@hek That did it! I included the library with the Arduino IDE and it put it on the top. Didn't know that, thanks!

What are the parameters of this radio, I could not get it to work. Suspicions that he had no speed 250.

WOW!!! What a cool project!

@scalz in the second test i used that getting started code to test the radio modules with a library other than mysensors. and they worked. (That code is not mine, i suppose it use the maniacbug library). So i did investigate to find the differences between mysensors and that library. Only after replacing, in mysensors, the enablefeatures with that code, i got the communication gw-node.

I think I found the problem. I think it misbehaved because of an illegal character in the "HOSTNAME". Changed the hostname yesterday and It was still alive this morning even if I have not pinged it.

Qu3Uk, I did get a chance to test with a Fitbit recently. It technically worked, but not all that well. The thing is, the Fitbit only advertises every 2 seconds so latency is a bit high. But worse, its apps really want to be connected to it often to sync; and whenever it's connected, it stops advertising and the detector then can't pick it up. TommySharp, At this point I don't plan to modify the board much but having it read environmental sensors would be a cool feature! For that, would be nice to make little beacons that read sensors and advertise/broadcast the readings every few seconds. Then they could be very low-power, run on coin-cells for months, and could be placed anywhere instead of needing it to be hooked up to USB power like the main board is. Like these: https://sen.se/peanuts/ I'm curious if it could read them. As for enclosures, I know. I would love to have some nice ones but at this point I'm making too many boards to 3D print enclosures, but too few to afford injection-molding tooling to make a custom case.

The final version of the boards contains few notable improvements Removed the PCB under the ESP8266 antenna. The previous design had PCB + Ground Plane, which resulted in VERY low reception. It worked just few meters away from the router. Removed the Temperature Probe - On the one hand - it does not really measure real temperature, on the other hand it populates the Single Analog port, and makes it unavailable for other usages Added place for an optional LDR (in case the Analog port is not used - one could add an LDR for added value) The connection between GPIO 16 and RST (Deep Sleep) is not bridged via a 0603 0ohm resistor (jumper). Depending on application it may be enabled or not Added a Power 5V line. That is - controlled via a SOT232 mosfet and one GPIO. This way you can connect power hungry modules and then turn them on or off. There are small mosfets rated ~ 2-3 amps for couple of cents. The big 12mhz crystal for the CH340G was replaced by a small patch ceramic oscillator to save space Added an additional mounting hole Added additional test pads for the unused GPIOs Added one Diode in series with the power to the WS2812B LED. It turned out, when powered directly via a USB Battery bank, the voltage can be 5.30-5.40v. And apparently WS2812B, does not light if VIN is > 5.15V. So putting a generic small Diode would drop 0.3-0.4V Here is how the latest design looks like

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: Do you remember the discussion about multinode? So, it will be available soon))

@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 :))))

@Yveaux I have 34 of 80k RAM used for this sketch, so 128 bytes looks like "a bit more". You can not use progmem with ESP and mysensors now because PSTR redefined as PSTR(x) (x) so all strings are really in RAM

@DirkB19 Think you will get another advantage by changing as well - must be a lot easier to monitor the MQTT messages when topic clearly shows the difference.

yep. but sometimes, usb powered things are useful, in case of esp8266 which is not a lowpower thing

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

@vlad I am having the same issue. Where did you change keepalive timeout to a long time? Essentially, what file did you edit, what parameter and to how long?

@Yveaux I already did! https://github.com/mysensors/Arduino/pull/396