@frapell did you replace the power supply of the gateway?

@Dave-Myers iirc nodes are supposed to perform the conversion themselves. I know at least the gateway does not take care of this.

@Newzwaver said in Ethernet Gateway Using PCBWAY board Fifisoft57:

!TSM:INIT:TSP FAIL

This indicates there's a communication issue with the radio module. Start your debugging there.

@Njwyborn sorry, I don't know. If the stack is called recursively, something is seriously wrong and behavior is undefined I guess.

@Njwyborn judging from the logs, i would suspect that you're at least suffering from this issue https://github.com/mysensors/MySensors/issues/1458, which unfortunately is still open.

@Serj-Sam there is a pull request included in that pr. Once this is merged it will be available in development, later in the next release.
If you just downgraded the core, that is persistent until you upgrade the core to 3.x again.

@Serj-Sam you could very well have run into the incompatibility of mysensors with the latest esp arduino core 3.x (see eg https://github.com/mysensors/MySensors/issues/1496)
Easiest solution is to downgrade the esp arduino core to 2.x

@benhub some sellers indeed have EU warehouses, which are now the preferred ordering locations for EU citizens. I also don't know how to easily find them on eg aliexpress. I kind of run into them by accident...
Additional benefit is shorter shipping times, but products stocked are limited in general.

@anderBAKE said in WeMos D1 Mini Gateway + Relay:

#define RELAY_PIN 1

That should be

#define RELAY_PIN D1

When something doesn't work it's best to strip a sketch to the bare minimum and get that to work first, eg setup the pin, then switch the relay on and off from the main loop(), without including mysensors or anything else.

@anderBAKE are you sure the code to actually toggle the relay gets executed? You could add some debug statements or toggle the led instead.
Btw. I would prefer

if (message.getBool() == true)

Or even

if (message.getBool())

@Serj-Sam logs are available through serial port. You mention esp8266 and esp32; which one is it?

@ben999 said in Raspberry as a node (bis):

Does it stay local within the LAN (and gets directly to my gateway) or does it have to travel through internet up to openhab and down again to my gateway (remember, my bell has to ring) ?

You run an MQTT broker ('server') somewhere in your local network (or even on your pi) that takes care of distributing the data.
Not saying you need MQTT, only that it works marvellous for me.

So last question just to be sure : it is not common practice to use RPi as a node ? And there is no "sketch" ready made that can be tweaked ?

Not to my knowledge, but as all platforms supported by mysensors can be turned into nodes, this should also work for a pi.

@ben999 said in Raspberry as a node (bis):

Raspberry will be connected to LAN to transfer picture to NAS, probaly via wifi (or wired if i decide to go down the PoE road...)

Ah! Thought you were slightly paranoid ;-)

But i also want the RPi to be connected to openHab in order to send notification of "front gate button pushed" via MySensors so i can get the doorbell to ring AND a broadcast message from openHab.

I personally would go the MQTT way for this and bypass MySensors completely. Probably there are many more ways supported by OpenHab to trigger something on a remote node or receive some data from it using a (wireless) ethernet connection.

@ben999 said in Raspberry as a node (bis):

Not posting doesn't that mean i've lost interest

It's been a while indeed. Welcome back :hugging_face:

can a Raspberry Pi be hooked to a NRF module and behave like a node

I would think so, but to send an image to your NAS the connection is way too slow.
Just use WiFi/ethernet to connect your pi to your LAN, and use that to transport images.

@Zwer2k my expectations seem correct. I created a bug report that also includes a rudimentary workaround.

https://github.com/mysensors/MySensors/issues/1496#issue-968399284

@Zwer2k mysensors replaces the arduino statup code, so you don't have to call setup and processing functions from your code.
Likely something changed in the esp arduino 3.x implementation that causes the mysensors code to no longer work.
If i can find some time I'll have a look.

@Zwer2k please don't crosspost!

@pw44 said in nRF24Doctor:

Is this undestanding correct?

Yes it is

@Njwyborn said in Is there a "standard" way to terminate a sleep time, after waking by an interrupt?:

Please note that I am still on V 2.2.0

You should have started there. I fixed some nasty race conditions in the sleep code, that iirc, were not included until 2.3.0.
Why don't you upgrade? These versions are on - air compatible anyway.

@Njwyborn said in Is there a "standard" way to terminate a sleep time, after waking by an interrupt?:

so if I just define the pin as INPUT_PULLUP, and not attach a interrupt, when I call sleep, passing the interrupt handler, it WILL call the handler?

You shall not pass the interrupt handler, but the interrupt number instead. Each pin that supports interrupts can trigger a certain interrupt. The interrupt number for a pin is returned when calling digitalPinToInterrupt(). You can read more on the topic here.
During the execution of the sleep() function, a new interrupt handler will be installed that is used to handle the wake-from-interrupt. It is detached again, before returning from sleep().

About the most minimalist implementation is the following, which compiles without errors:

#include <Arduino.h>

#define MY_RADIO_RF24
#include <MySensors.h>

#define MY_PIN         (3)
#define CHILD_ID       (0)
#define SLEEP_TIME_MS  (60000)
#define SKETCH_NAME    F("Test")
#define SKETCH_VERSION F("1.0")

void presentation()
{
    sendSketchInfo(SKETCH_NAME, SKETCH_VERSION);
    present(CHILD_ID, S_RAIN, F("Rain"));
}

void setup()
{
    pinMode(CHILD_ID, INPUT_PULLUP);
}

void loop()
{
    auto result = sleep(digitalPinToInterrupt(MY_PIN), RISING, SLEEP_TIME_MS);
    Serial.println(result);
}

How is it possible to utilise an interrupt on a otherwise sleeping node, WHEN it is awake?

I did not relealize before that you wanted to install your own interrupt handler for the same pin when the node is awake.
To achieve this, you can just attach your own handler after returning from sleep(), something like:

// .. same code as above ..
void RainINT(void)
{
  // .. handle the interrupt ..
}

void loop()
{
    auto result = sleep(digitalPinToInterrupt(MY_PIN), RISING, SLEEP_TIME_MS);
    attachInterrupt(digitalPinToInterrupt(MY_PIN), RainINT, FALLING);
    Serial.println(result);
}

Just be aware that the call to sleep() will overwrite your installed interrupt handler, so you need to reinstall it after returning from sleep().

separately, what is wrong with my watchdog implementation?

MySensors on AVR uses the watchdog to wake a sleeping node after a certain amount of time.
To achieve this, it reprograms the watchdog just as it does with the interrupt handler.
In most cases you will be just fine if you reprogram the watchdog settings when returning from sleep(), just as when reattaching the interrupt handler.

However, as MySensors hides you from a lot of nastiness by taking over hardware specifics, you must understand its limitations.
That's why I do not suggest most users to follow your solution but instead, don't use the watchdog or try to share interrupts.