A related thread: https://forum.mysensors.org/topic/6843/re-request-presentation

How can we send a I_PRESENT or I_REBOOT command using the HA / MySensors API? If there's a way, then an automation be be hard-coded to request each node to reboot.

Howdy,

Is it possible to rename MySensor nodes in Home Assistant? I've noticed that I can't use the normal method to rename by clicking on the cog in the Developer States window.

Cheers,
Simon.

Hi All,

Just knocked up a case for @sundberg84 's Newbie PCB with Dimmer module. Thanks to @sundberg84 for the great PCB's.

This is the first version, and the clearances are rather generous which makes the case bigger than it needs to be. Further revisions will try and get this down to make the overall size smaller.

As you can see in the photos, the print around the aperture is a little scabby, but I think that has more to do with my poor placement of supports rather than the model itself.

The case is a press fit with snap clasps.

Files over on thingiverse here: https://www.thingiverse.com/thing:3135667

Enjoy!

!

In your next rev, perhaps you increase the spacing between the voltage regulator and the MOFSET to accommodate heat sinks? The minimum would be 2.54mm.

Howdy,

I'm loving the NodeManager for my temperature, humidity and repeater nodes. I've just built a battery power meter node and noticed some weird behavior. I'm using the latest version 1.7.

The pulse sensor can interrupt < 1 second. That is to say, the pulse frequency can be less than 1 second at certain periods of the day. I find that I can't get the sensor to report because the node interrupts and then sleeps and then interrupts again before the sleep expires and wakes to send the report. So in the debug, all you see is the interrupt processing and never a send.

Just for debug, I've set both the sleep and report interval to 1 second and I've seen this behavior. What I would like to do is to set the sleep and report interval to 5 minutes, but I don't think that it would ever report.

Any thoughts?

Hi All,

Thanks Sundberg84 for creating a board where I can knock out sensors in the matter of minutes instead of hours.

That being said, I actually spent many hours on the weekend trying to get my first board to work so I thought that I'd share so it could benefit others.

I was setting up a 3v3 board with 2 x AA batteries with the battery pad jumpered and using the 3v3 booster. I triple checked the board for continuity.

I was suffering from !TSM:FPAR:FAIL messages when firing up the node using the FTDI adaptor. I found that the board didn't work when both the battery and FTDI were supplying power.

Here are my lessons:

• You need to have a battery connected. This is required to power the radio, as it radio isn't powered by the FTDI adapter
• You need to remove power from the FTDI adapter. I couldn't disable power on my FTDI adapter so I had to use jumper wires for CTS, DTR, RXD, TXD, and GND between the adapter and the ProMini.

Thanks again, and I look forward to knocking out some nodes super quick.

Cheers,
Simon.

Awesome...thanks.

@Nca78

Ok....That sounds reasonable. I am assuming that is set with the #define MY_RF24_CHANNEL?

Howdy,

Title says it all. I'd like to have the ability to build and debug sensors with a test gateway and have a way to present to the production gateway when they've been tested.

I am mostly using SenseBenders in my production setup, with a few Nano's as repeaters.

Any ideas on how to be able to run up a sensor without it presenting to the production gateway?

Why do I want to do this? I've had issues when using HomeAssistant keeping the state of test child sensors that change while I'm still working and debugging the sketch. I'd like to run a test HomeAssistant with the test gateway.

Thanks,
Simon.

I'm an idiot.......

I just noticed a binary_sensor.nodemanager_113_3 was created in the dev-state page.