I verified a variable named Voltage DOES get created and is set on the Vera arduino node device if I create MyMessage with:
- MyMessage voltageMsg(255, V_VOLTAGE);
and send value with:
- send(voltageMsg.set(12.1, 1));
I verified a variable named Voltage DOES get created and is set on the Vera arduino node device if I create MyMessage with:
and send value with:
No response - I feel like Jeb Bush when he said "clap please"
Re: gw.send( ) and transmission errors,
@rickmontana83 suggests "...you might consider adding a "resync" timer that sends the current state regardless of changes every so often. So even if something is dropped you have a bounded amount of time where things are in the wrong state".
I like this idea but it got me thinking - instead of periodically resending current state of a sensor val, why not periodically do request(<childid>, <valuetype>) for that value instead and then in arduino receive() method check the returned value for difference from current local value. if diff, resend with send(). The particular sketch I'd do this for never turns off the radio so I should get most GW messages.
I realize you'd be more than doubling the number of messages between node and GW. Instead of a single send() you're doing request() followed by callback to receive() followed by send() if the values are different. The reason this is attractive to me is - I would only do a send() for a value change, either the original change or detection that send() of the original change was lost. This means I should always have the correct, or nearly correct, date stamp associated with the value in Vera so I get better status as to when a sensor value actually changed.
Any thoughts?
I verified a variable named Voltage DOES get created and is set on the Vera arduino node device if I create MyMessage with:
and send value with:
Yeah, I realize that is preferred way but in this case, since battery percentage is already going to the arduino node device in vera, why not set voltage there as well?
On the other hand, I realize I used the wrong sensor device type S_POWER when I should have used S_MULTIMETER. I will switch this and
hopefully voltage will show up in the vera UI directly for that sensor device without having to drill down to view variables.
Did more searching and found Push Data to Vera Node
where @hek reveals one can use child id 255 for the arduino node so I may try this as well.
I searched the forums but can't seem to find this addressed anywhere.
I am currently setting battery percentage by calling sendBatterlyLevel(), this sets a a variable BatteryLevel variable on my arduino node device on Vera Edge.
I also created a sensor to set a voltage variable on a sensor device for this arduino node:
This works fine but all I care about is voltage so would be nice if I could simply set a voltage variable on the arduino node device in vera and dispense and have one less sensor device (the S_POWER sensor device).
If I assign a specific node id NODE_ID to my arduino node device could I do something like:
FYI - the reason I want voltage in addition to battery percentage is to get something more specific AND because I've chosen to limit battery percentage range to vals corresponding to 0 - 12.5 volts (typical for my battery when NOT charging) while the voltages I see actually go well over that when my solar system is charging.
Thanks
@hek said:
No, never had time to finish my rain gauge this summer.
But it should be doable. But the big pcb in there has to be modified, or even better is probably to move the reed switch directly to the sensebender.
ok thanks
@hek said:
Received my off the shelf tipping bucket sensor today. http://www.ebay.com/itm/331525977548?rmvSB=true
To my surprise it contained a dummy 2xAAA battery compartment. It might be possible to squeeze in a sensebender and nrf-radio (with some slight modification).
@hek
Did you ever wire this up with sensebender & radio squeezed in?
I have this same guage I want to use with sensebender