Hello
first of all, excuse me for my english, i'm french.
I try to use the sketch with the 10 relays, but nothing works on the buttons.
I tried with several resistance values using "analogread" to read the real values, but when I enter the values in the table nothing happens at the relay levels.
P.S: the relays work with jeedom.
can you give me the procedure to follow to properly "configure" the sketch?
cordially
@kiesel said in Battery: pro mini @ 1mhz vs booster:
@zboblamont
How do I know whether a booster introduces noise? I think so far I have been lucky with my three nodes because they work as expected. Or I don't know what to look for...
If you wanted to play it safe (aka defensive programming), you could use your booster to charge a capacitor that's large enough to provide interim power, turn off the booster prior to doing your radio communications, and then turn the booster on again when you're done with tx/rx. That would effectively remove your booster from the equation as an interference source.
Also, some boosters have a pass-through, so you can use your regular battery voltage for as long as it's high enough, and then when it no longer is, enable your booster, if that's what you want to do. Here's an example of one:
https://www.openhardware.io/view/285/33v-Boost-Converter-with-Pass-Through
For instance, CR2032's can have quite a voltage dip after volunteering some current, so this would be one way to keep wringing a useful voltage out of such a battery after its voltage may have temporarily dropped too low.
Some of the ARM MCU chips include boost converters that can boost from as little as 0.5v....
@Gerard-van-Seventer
I am using appdaemon for my automation and I wouldn't want to install node red just for the conversion. Or are there automations that node red can that appdaemon can't?
@monte said in Modular sketch to be configured with JSON (idea):
Imagine you have base firmwares for most sensor types, or it can be generated with NodeManager.
I don't see specific technical limitations to have this working. On the NodeManager side would be:
Include in the sketch all the sensors you want, which is already there
Have a logic to configure sensors remotely, which is mostly there through SensorConfiguration (https://github.com/mysensors/NodeManager/blob/master/sensors/SensorConfiguration.h). If then the configuration is through individual messages or json, it makes little difference. There might be some configuration settings missing since not all are available OTA
Implement a logic for configuring only specific sensors. Shouldn't be that difficult, probably best is to have a enable/disable switch for each sensor (https://github.com/mysensors/NodeManager/issues/500), having all the sensors disabled by default and then dynamically enabling them
Bottomline not something to put in place in a few minutes but all the building blocks are there. I do not have at this time spare cycle to spend unfortunately but feel free to start looking at it if you like.
user2684 created this issue in mysensors/NodeManager
open
Add option to enable/disable a sensor dynamically and remotely
#500
Actually I have to disagree with @rejoe2 about:
Will my network work without controller (only gateway + nodes)?
With an Ethernet gateway it is entirely possible.
One more thing. If you are interested in building RS485 network, maybe you should have a look at my project. Earlier today I created a post about it on this forum. Here it is
