you could use this under the bed:
It works like an infrared sensor (same three pins), but it does not need a line of sight. It just reacts to movement as this results in a disturbance in the emitted radio signal. Works very well on my clock 
The "high" value when movement is detected is not a full 5V, so I test the Out pin as an analog pin. Anything above 2.5V is an activation due to movement.
@mfalkvidd I set it to 1000ms, but the jumps are sometimes 3 - 4 seconds. I was hoping that shutdownTransport() would do the trick. But that does not seem to help. It looks like I need to define a hardware_shutdown button or something.
I'm building a MySensors aware clock. However, I need to provide for the situation that the netwerk is down (gateway without power, or not installed). Or there could be a problem with the radio. In all cases I want the clock to still start up and run without apparent slowdown.
What I found was, that when I do not install a radio, the MySensors library is aware of this (a FALSE result from isTransportReady() ), but the MySensors code seems to take it's time and hog the processor by trying to reconnect.
This is visible on my clock, because the time on the display seems to "freeze" for some seconds. As I use a real RTC, this not really a big problem, but it is visible none the less. And being a perfectionist, I do not want a clock which seems to jump a few seconds now and then.
So the question is how to skip these processor intensive parts if the user accepts that the clock should work without MySensors integration.
Any suggestion is fine
Is there a way to completely shutdown all MySensors code via code (not via compile defines, but a decision made in code) ?
@neverdie that is a nice pattern. I found that these things need time to draw. If anyone has a DXF file, I would love to try it.
is there a #define symbol for the first really free EEPROM address ?
From the .h file I gather that EEPROM_LOCAL_CONFIG_ADDRESS and higher are free of my own use ???
@neverdie I will publish the project once it has advanced a bit more (still need to design the PCB for this box).
@neverdie nope, but it is inspired by oriental frames, I just made that based on what I saw on one of my cabinets (which I bought while living in Singapore).
One of three ongoing projects:
lasercut box
atmega1284p based
DS3231 rtc (very accurate and 2 alarms!)
LDR
20 by 4 LCD, two sizes of numbers, menu driven setup
buzzer
leds for moodlighting
doppler for proximity detection
encoder for scrolling through values (for setting time)
buttons with LED feedback for interactivity
mp3 player
most interface objects MySensorised
This entry is to boost my energy, because we are still a long way from home (pcb is still not made, focus is now on prototype and software).
@mfalkvidd
Nope, I probably got this from a forum message somewhere. I’m not sure where I got the suggestion to use the define.
The thing is, it is very nice to have this #define, but as @Neverdie said, it would be nice to avoid that a node “hangs” if the gateway is unavailable. As far as I can see, there is no DEBUG message if the network is not reachable. And for a new MySensors user a hanging node is really confusing (it is sometimes for me as well). So this #define will now be part of me ‘default’ template until the standard behaviour is adapted.
