Troubleshooting

@scalz That may well help even if I'll struggle to understand it. At least your setup combines similar basic principles to my objective. Since the OP, have nailed "sensors.begin()" which causes problems as a Dallas library call, and as your sketch does not employ that library, perhaps a glimmer of a solution.... Many thanks for that. Cheers...

@mfalkvidd Thanks, that solution worked and sorry I should have found that posting myself of course. FYI, for loading the ESP8266 Board definitions the usual URL https://arduino.esp8266.com/stable/package_esp8266com_index.json did not work for me anymore. Instead I had to use https://github.com/esp8266/Arduino/releases/download/2.4.2/package_esp8266com_index.json

@mfalkvidd Solved, it was my mistake on wiring. Thanks.

@pl_rekin It's great when the 'penny drops' - Learning is not so bad when you can admit not knowing something and move on with enhanced knowledge! :)

This is exactly why the Candle Manager always flashes the MySensors clear sketch before flashing the actual code.

@petr-nosek sure with the 2nd power supply it looks different. However mine were all in-wall and there is just not enough space for this.

@rafael156 oh crap ... I put in that lowFuse as FF .. ( I read you had it for 8 MHz INTERNAL .. but nooo you wrote external ... ooops ... is there any way to force write it back without connecting an 8 MHz oscillator to the chip .. I only got 16 MHz oscillators .. or am I screwed for that chip until I go and get one?

@badmannen @Yveaux You're absolutely right. I was lazy, only changed a symbol and gave a bad advice. My response should be changed to <=4. Still I don't understand what the original question was.

If you really enjoy fiddling with connection problems and gateways freezing you should try using the gsm gateway. At first it froze up every day or two. I now run a second mcu just to check connectivity to mycontroller and resetting the gateway when it fails. This sometimes happen a couple of times a day.

@markjgabb "..cut back all unneccicary steps and really locked down what was going on.." was indeed the idea. What I went on to explain is than you are reporting the state of D3 which goes HIGH/LOW/HIGH via the button, not the light. The critical difference between @skywatch and your install is movement detection maintains a value, your button does not. If you create a variable before the loop, say boolean lightswitch=false; (presuming that the light is ON when you program it) this variable will be changed and reported to Domoticz in the loop. Top of the loop you toggle the "lightswitch" value, first time it will switch false to true, report in the "lightswitch" value then go to sleep. Bottom of the loop your " sleep(digitalPinToInterrupt(DIGITAL_INPUT_SENSOR), CHANGE, SLEEP_TIME); should trigger on a LOW, as this is the momentary state of D3 ONLY when the button is pressed. Your next button press activates the loop, toggles "lightswitch", reports and goes back to sleep, at least two years on a pair of AA cells. Were it I doing this there would be a mains powered indicator on the switch plate which cuts out when the light is on, A- To find the switch in the dark, B-To provide an indicator which can be used to verify the actual state of the light to ensure it stays in sync (Murphy's Law). I don't see the point of using heartbeat as it is not a security device, and only fire the battery reading mosfet every X loops.

@kurtsejr Good to hear that ! :)

@encrypt said in Signing fails due to NACKed messages: I can't enable radio logging easily but I suspect it could be caused by the auto-adjusting RSSI feature... I'm afraid, but without additional debug information it's gonna stay a guessing game. If possible, enable #define MY_DEBUG_VERBOSE_SIGNING #define MY_DEBUG_VERBOSE_RFM69 for additional info. Also, please post the node sketch to interpret the log in the right context.

@keldandorin You'll need to install the development version of MySensors, or downgrade the esp board definitions. See https://forum.mysensors.org/post/92176 for more details.

Thanks for the feedback @zboblamont! I was probably overthinking the whole thing :P

@gundark2 a long usb cable, or something like https://www.aliexpress.com/item/32959138610.html or https://www.openhardware.io/view/532/The-Logger-Machine-Short-and-long-term-serial-logging

@user2684 There's a lot of info regarding flashing ESP devices on this site: https://github.com/arendst/Tasmota/wiki/Flashing and https://github.com/arendst/Tasmota/wiki/supported-devices You could also consider running Tasmota on your Sonoff devices, as it contains much more functionality compared to MySensors MQTT gateway.

For plan A (Raspi gateway) I am still waiting for the new radio modules. I'm not scrapping this plan yet... Regarding plan B (ethernet gateway), I am still confused regarding which pins to use and how to make it in the sketch: [image: 1573035936777-9b5536d2-b03a-4006-a9d0-76be91d841a5-image.png] On the left are the pins used in the Ethernet Gateway page, with a nano, a W5100 and the NRF24L01+ radio. Also, the MY_RF24 and MY_SOFT_SPI commands in the original sketch. On the right, the RF-NANO, W5500 and the NRF24L01+ radio I am trying to use. The pins of the radio are fixed, as both are in the same module: [image: 1573037434981-93afe9f7-f4e6-4071-8ba6-c4d1d93a9bd3-image.png] Is the following correct? (#1) the MY_RF24_CS_PIN is now pin 9 while MY_RF24_CE_PIN is the default one of the nano (pin 10, SS?) so it can be ommited (?). (#2) the W5500 pins are the ones that have to be moved now. MISO, MOSI and SCK are going to pins 16, 15 and 14 with MY_SOFT_SPI (I am assuming the W5500 supports software SPI, I read yesterday that not all modules do) (#3) where and how goes the SS pin of the W5500??? MY_SOFT_SPI_CE_PIN exists? Is this what you mean with your comment, @neverdie? All this is really exciting, but I still have a lot to learn. Apologies again for the 'dumb' questions...

I guess i found it now, Looks like that V_LEVEL and V_LIGHT_LEVEL are both not behaving as expected, I have changed these now to V_TEXT after that the sensors was finaly working within domoticz. Also i had some cabeling issues, looks like the sensor doesnt like an cable length off 2 meter on 4x 0,44mm2 wire.. Tommorow i am going to place the arduino closer to the weather station and i guess everything would be fine again then ! Here my latest sketch: #define MY_DEBUG #define MY_RS485 #define MY_RS485_DE_PIN 2 #define MY_RS485_BAUD_RATE 19200 #define MY_RS485_HWSERIAL Serial #define MY_NODE_ID 5 #include <MySensors.h> #include <BH1750.h> #include <Wire.h> #define CHILD_ID_LIGHT 25 unsigned long SLEEP_TIME = 25000; // Sleep time between reads (in milliseconds) BH1750 lightSensor; // V_LIGHT_LEVEL should only be used for uncalibrated light level 0-100%. // If your controller supports the new V_LEVEL variable, use this instead for // transmitting LUX light level. // MyMessage msg(CHILD_ID_LIGHT, V_LIGHT_LEVEL); MyMessage msg(CHILD_ID_LIGHT, V_TEXT); uint16_t lastlux; void setup() { lightSensor.begin(); } void presentation() { // Send the sketch version information to the gateway and Controller sendSketchInfo("Node 5", "1.0"); // Register all sensors to gateway (they will be created as child devices) present(CHILD_ID_LIGHT, S_BINARY); } void loop() { uint16_t lux = lightSensor.readLightLevel();// Get Lux value // Serial.println(lux); // if (lux != lastlux) { send(msg.set(lux)); // lastlux = lux; // } wait(SLEEP_TIME); } @Nca78 Thanks for your help !