@Arvie_Mamayson It was fixed a couple of weeks ago. I just tested and works for me

I concur with @TheoL, though I understand the desire to have better control over your interface. The MySensors serial interface is well documented. You might consider MQTT as a transport mechanism. MQTT Explorer allows you to view the data which makes debugging easier. Good luck with your project.

If you’re already using MySensors, Home Assistant is definitely worth a look - great community, lots of integrations, and works really well with DIY setups. OpenHAB is another solid option if you prefer something more configurable.

@David-Jenkins Hi, good evening!! I can't find these examples. Can you share the link to the sketches? Thank you so much!

Hah! Been there, done that. Well done on finding the source of your issue and sharing the solution so others might benefit! Kudos.

My guess is that the the leakage power captured can only supply that amount of current (at the specified voltage)

That is a great clarification on the use of #define MY_PASSIVE_NODE! Knowing that it works by simply letting the node skip all the 'normal' stuff (which wasn't needed anyway) and that there are no major disadvantages for this specific use case is super useful.

@ben999 Yes I have 3 gateways 1 nfrf and 1 rm for production. And 1 nrf gw for test. The test gw is on a separare PI I might run a 4th gw. Also an rfm on the test machine.

Sorry to necro but, you may be interested to hear that someone published a solution to controlling Neato locally on GitHub. Unfortunately it requires a hardware modification in form of an ESP32 or similar board, but with it you should be able to use your Neato with Home Assistant, for example. I haven't yet tested this myself, but the solution looks worth a look and the instructions seem clear enough. https://github.com/Philip2809/neato-connected As I've received the dreaded shutdown email, I'll be looking into this once I have more time to tinker.

@dbemowsk said in MySensors node not working with Alexa on my Vera: Is there anyone that either still uses a Vera controller or knowssomething about how they work with Alexa? My issue is that my thermostat bridge had the Arduino Pro Mini die and I had to flash a new one. When I did this I had to re-discover it with MySensors in Vera. I then had to delete the node from Alexa to add the new one, but when I go to the list of discoverable devices it doesn't show up. I can control it fin on the Vera but can't add it to Alexa. Sounds tricky! If Vera controls it fine, the issue is likely with the Alexa integration, sometimes a full “refresh” or restarting the Alexa app after re-adding the device in Vera helps it show up.

I’ve had similar trouble with the LGT RF Nano — the radio part is a bit picky. What fixed it for me was lowering the data rate in the sketch and giving it a proper capacitor on VCC (even a small 4.7µF helped a lot). Also worth trying a different CE/CSN pin setup; these clones don’t always match the “standard” wiring perfectly. After that mine started talking to the gateway without any drama.

I learned my lessons about bread boards. Slowly replacing my cheap AliExpress ones with good quality ones. I blew up 2 nano's and 1 nrf this week because of a bad breadboard

Well it's nice that it can help people who want it. Maybe not all.

@skywatch @sindrome73 This is what I do, too. Note that it is wait(), which is a MySensors function and not delay(), an Arduino function. wait() checks for MySensors messages, delay() halts all process, thus a message might be missed.

Added some 3d sketches so you can see what I'm trying to accomplish. Unless ofc someone will tell me this is a bad idea

@mfalkvidd A while ago I tinkered with Media Wiki running on a docker. If I remember correctly you can set access for authors moderators etc. But I forgot, I need to spin that docker up any time soon anyway. Because it contains my network documentation and I need to update it. I'll let you know.

@OldSurferDude So if I get my circuit to work, that would by 22 times less (on average). Well I'm doing too many things at the same time. :)

You don't check for which sensor the message is send - message.getSensor() - and in both cases you set the relays both on Like Skywatch said. So you could do something like: if ( message.type == V_STATUS ) { // check if GW send a status change if ( message.getSensor() == sensor 1 ) { // handles sensor 1 } else if ( message.getSensor() == sensor 2 ) { // handles sensor 1 } ... etc }