@fets So far, I have only built the 5x5 board (but the others should be schematically identical). The only issue I have found so far is that I cannot get the ISP port to work. But I have checked and I have an identical setup on the 1.0 board and that worked, so I suspect the programmer is too weak to drive the net on this one. So it is not a board-issue per se, and might only be an issue on the 5x5 board as routing is the most complex on that one due to the size.
@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
@NeverDie Yes, you are correct - it is based on ATMega1284P. So not relevant
My point is that I'd rather stick to the datasheet rather than overclock, but that's just me. And yes I realise that Moteino is overclocking, but the size, voltage and flash are really appealing to me.
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.
@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.
Hi all,
Should anyone face the same problem, I found the root cause: brownout threshold. I burned a new bootloader (Optiboot 8.0) without such trigger and the node has been working with used batteries (~2.7V) since May.
Hope this helps.
