Hi2All!
Surprising is here. After about 24hours I refresh HA and suddenly my motion sensor was integrated.
There is also second entity > battery : 0 , have to look deeper into that for understanding.
Need to change little in the sketch, because don't want every short time 'no movement' so only when there is motion and maybe once a hour indication sensor is alive.
Meantime I found 3 other good threats:
https://forum.mysensors.org/topic/11200/finally-progress-evidence-based-radio-testing-method-and-capacitors
https://forum.mysensors.org/topic/1664/which-are-the-best-nrf24l01-modules/27
https://forum.mysensors.org/topic/9550/build-a-reliable-power-supply-chain
Very usefull for me also finally progress because of lacking time in the past.
Great jobs are done here!
Thanks for this all of you guys or girls!
Could be power I suppose. You say that it reboots OK with other sketches. Do both the relay and temp sensor single-sensor sketches reboot OK?
I was assuming so, which is why I was thinking something software rather than hardware, but assuming is what gets us stuck, debug wise.
Have a look at the sensebender sketch http://www.mysensors.org/hardware/micro#example-sketch
if ((measureCount == 5) && highfreq)
{
clock_prescale_set(clock_div_8); // Switch to 1Mhz for the reminder of the sketch, save power.
highfreq = false;
}
The clock frequency is scaled down by software.
SO an update, I connected a 10Mohm Resistor and my current draw is only 3.1-3.2uA when the switch is engaged and 2.7-2.8uA when the switch is removed. I think that is really livable numbers. So far not getting any false positives which is great. :)
Ok, I figured it out. My issue was related to the change with respect to the message callback which has been introduced with 1.5. I had the callback method registered in the call to the begin method of the gateway node but also called it directly in the loop function as well.
So this one has been fixed. Sorry, bothering you.
@joshmosh
When a node presents it's sensors it sends out child id's. So the controller knows which child id's exist. When values are send to the controller this is in combination with the sensor child id. So the controller knows which value belongs to which child id's exist.
If you then look at it pure from controller perspective it just sees multiple sensors. You can even put all your values within the same child id as long as the V_* types are unique used with that child id (do not use two V_TEMP values with the same child id).
I made a night light for my son and just used V_VARs
I used the fastLED library And this code to decode from 255,255,255 that I was sending from the controller
https://codebender.cc/sketch:90239
Last time it came up http://forum.mysensors.org/topic/1148/need-help-with-turning-a-led-on-off-with-openhab-and-mqtt/4
