Admin

@Mister_ik You're not missing anything. It wasn't designed to do what you're describing. That is an interesting idea that I never thought of though! It shouldn't be too hard to implement if you wanted to try. I'm not sure which device types are available in Domoticz but I would think you would want to use some sort of momentary button press (rather than an on/off switch) in Domoticz. You could then send that to the sensor and when it receives the command it could trigger the relay. Have a look at the relay actuator code if you haven't done this before. https://github.com/mysensors/MySensors/blob/development/examples/RelayActuator/RelayActuator.ino#L82

This works for me
sketch.ino

#define MY_RADIO_NRF24

#define MY_USE_ADC_FILTER
#define MY_ADC_PIN

#include "RPlibs.h"

RPlibs.h:

#ifdef MY_USE_ADC_FILTER
#error "Define ADC set!"
#else
#error "Define ADC not set!"
#endif

With the define, the build process outputs

In file included from C:\Users\Micke\AppData\Local\Temp\arduino_modified_sketch_472392\sketch_sep20a.ino:6:0:

RPlibs.h:2: error: #error "Define ADC set!"

 #error "Define ADC set!"

and without the define it outputs

In file included from C:\Users\Micke\AppData\Local\Temp\arduino_modified_sketch_303778\sketch_sep20a.ino:6:0:

RPlibs.h:4: error: #error "Define ADC not set!"

 #error "Define ADC not set!"

@Robinek70 are the defines in the sketch before including the library? That should be sufficient. If they already are, could you share your code?

@gohan

I think it is this one https://github.com/tbowmo/energyPulseCounter (haven't touched for a couple of years now..)

node-red mangles the incoming data, and emits it as a mysensor "node" towards domoticz.

@arraWX

I use the SD card for influx databases, haven't moved on to using an external hdd yet, but have it in my plans.. Problem is that it just runs without problems right now, so I do not dare to mess with it

@ceech I'll be happy to update the guide if you could be a bit more specific.

@ceech yes and no. Skipping the test step is a bad idea. If that step is skipped, people have to resort to asking questions in the forum

@NeverDie it depends on the value of MY_TRANSPORT_WAIT_READY_MS
See https://github.com/mysensors/MySensors/issues/927 for a discussion on what happens when - we're trying to clarify the documentation.

mfalkvidd created this issue in mysensors/MySensors

open Update examples to use logical order for methods #927

@itbeyond Like @mfalkvidd pointed out eeprom writes are done to multiple locations so it actually gets 120 hours before the same eeprom location is used. So, 120 X 100,000 is over 1,000 years (if my math is right). That should be enough

The good thing about using eeprom is that you won't loose any data if your gateway is down or the communication is lost for some reason.

I think you are correct debugging other areas like the DHT. Also, is there a chance your arduino got wet? That could also cause issues.

@ceech I think I have located the error.

Domoticz wants to connect to the gateway, but in the configure command --my-controller-ip-address was used. This means that the gateway will connect to the controller, which Domoticz does not support.

So drop --my-controller-ip-address, run the configure command again, run make and start up again.

When I run sudo ./bin/mysgw -d with your configuration I get lots of these:

pi@raspi1:~/MySensors $ sudo ./bin/mysgw -d
mysgw: Starting gateway...
mysgw: Protocol version - 2.1.1
mysgw: MCO:BGN:INIT GW,CP=R-NG---,VER=2.1.1
mysgw: connect: Connection refused
mysgw: failed to connect
mysgw: Eth: connect
mysgw: connect: Connection refused
mysgw: failed to connect

which shows that the gateway is unable to connect to the controller.