Isn't it so, that this code block makes the node unresponsive for UPDATE_INTERVAL 60 s? The only exception would be the digital input 3 (PIR pin).
// Sleep for a while to save energy
sleep(digitalPinToInterrupt(DIGITAL_INPUT_SENSOR), CHANGE, UPDATE_INTERVAL); nsert Code Here
@hek said:
Hard to say anything about quality, but the following is at least in proper casing.
Have bought couple of similar ones. They are veeery noisy.... just something (depending on the use case) that might require extra components to compensate.
Excellent project. However, have you considered any possibility of condensation of humid air in the attic? At least where I live, that would become a problem.
To give a definite answer would require investigating the signals with an oscilloscope! Noisy signals can be seen quite easily, and also the effects of adding caps.
Note, that often a combination of a larger and smaller cap is needed to solve these issues. Think that larger one smooths out the slower changes (in the power line) while smaller ones smooth out higher frequency components.
I've ended up in some cases, depending on the power supply and the rest of the circuit, having a number of caps all over the circuit. Not pretty, not pro, but needed to stabilize the node sometimes..
These are most often related to noise of the power supply or other transient noise/spikes in the circuit (due to a relay for example).
To be more specific, I'd first remove the relay from the circuit and just use a led instead. If the node works then without problems for longer time, the reason indicates it's a noise issue from the relay section.
Similar examples can be found, e.g. http://forum.arduino.cc/index.php?topic=186879.15
Generally these are solved by separating the power supplies, or 'de-coupling'. A good read illustrating the situation, please read it through: http://www.thebox.myzen.co.uk/Tutorial/De-coupling.html
I have bunch of nodes that are troublesome. So fat it's been due to noisy somewhere in the circuit. Also, noticed that some nodes start to malfunction after few years due to low quality capacitors. And that is painful to cure...
In some cases it is also useful to force the NodeId of the repeater to be the parent (obvious, still took some time to understand it)
@Fat-Fly Nice, interested to try this also.
Any idea how long the batteries will last? Electricity meters tend to blink quite often, so not that much sleep..
Out of curiosity....what is your use case for this? [just thinking new ways to expand my system]
Ahh, thanks!
I have ack set to false (the last installed sensor version), so this rules out the search function, I assume!
Hi there!
Been struggling with my mailbox sensor radio coverage for a while (tried various radios, antenna modifications etc the normal route to insanity while having lots of fun).
Now wondering how the radio initialization routine works: if parentNodeId setting is AUTO (the default), does the node find the 'best' parent every time the node is reset/rebooted, or is it merely a one time process?