The AI's CAN be helpful.. but I have also seen things where working with the AI and constantly feeding back the errors actually takes longer and sets off down the wrong path. So there are places where it will obviously excel and those places it has LOTS of information on. Working on things it doesn't have lots of public knowledge on it will just throw stuff out that it thinks is right regardless of if it would work at all.
@OldSurferDude I use this. https://www.homedepot.com/p/Orbit-Solenoid-for-Battery-Operated-Timer-57861/203151515
Instead of having to hold the valve open, i can just pulse it. I use a simple motor controller to pulse it and when i need to close it, pulse it in "reverse". That way I could use a battery and if it only opens once or twice a day it's only a half a second or so of draw off the battery.
What components are you using for the charge controller and the battery?
For the 3dprinted enclosure, what are you planning to do to keep it water tight?
I had a similar project last year but instead of the soil moisture sensor, I was using it to turn the water on/off to water the garden. That one needed a little more juice to trigger the locking solenoid valve so I had to do a 2s 18650 setup.
I see in your notes in the code that smartsleep didn't work for you?
I actually thought smartsleep with home assistant worked pretty well. What did you run in to?
Not sure if this helps or if anything jumps out, but here is the node and gateway side by side. Node does find parent request, gateway sees it, responds with 0. But node never gets it.
@skywatch unfortunately no. This is for a sprinkler valve that I haven't set up any automations for yet since the questionable reliability at the moment would flood my yard lol
@mfalkvidd said in smart sleep inconsistent?:
Btw, are you using MySensors 2.3 on the node and the gateway?
Correct 2.3 on node and gateway.
Got some more info. Here is some debug log off the gateway. The node in question is node 18
22:02:47.582 -> 28832653 TSF:MSG:SEND,0-0-18-18,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
22:03:51.377 -> 28896448 TSF:MSG:READ,18-18-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
22:03:51.422 -> 28896512 TSF:MSG:BC
22:03:51.422 -> 28896533 TSF:MSG:FPAR REQ,ID=18
22:03:51.468 -> 28896566 TSF:PNG:SEND,TO=0
22:03:51.513 -> 28896594 TSF:CKU:OK
22:03:51.513 -> 28896615 TSF:MSG:GWL OK
22:03:51.967 -> 28897026 TSF:MSG:SEND,0-0-18-18,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
22:05:01.405 -> 28966464 GWT:IMQ:TOPIC=mygateway1-in/10/1/1/0/40, MSG RECEIVED
22:05:01.497 -> 28966569 !TSF:MSG:SEND,0-0-53-10,s=1,c=1,t=40,pt=0,l=6,sg=0,ft=0,st=NACK:FFFFFF
22:07:04.200 -> 29089296 TSF:MSG:READ,18-18-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
22:07:04.246 -> 29089359 TSF:MSG:BC
22:07:04.292 -> 29089380 TSF:MSG:FPAR REQ,ID=18
22:07:04.337 -> 29089414 TSF:PNG:SEND,TO=0
22:07:04.337 -> 29089442 TSF:CKU:OK
22:07:04.382 -> 29089463 TSF:MSG:GWL OK
22:07:05.152 -> 29090214 TSF:MSG:SEND,0-0-18-18,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
22:10:01.430 -> 29266499 GWT:IMQ:TOPIC=mygateway1-in/10/1/1/0/40, MSG RECEIVED
22:10:01.521 -> 29266604 !TSF:MSG:SEND,0-0-53-10,s=1,c=1,t=40,pt=0,l=6,sg=0,ft=0,st=NACK:FFFFFF
22:10:59.660 -> 29324730 TSF:MSG:READ,38-38-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
22:10:59.706 -> 29324794 TSF:MSG:BC
22:10:59.706 -> 29324815 TSF:MSG:FPAR REQ,ID=38
22:10:59.751 -> 29324848 TSF:PNG:SEND,TO=0
22:10:59.797 -> 29324877 TSF:CKU:OK
22:10:59.797 -> 29324897 TSF:MSG:GWL OK
22:11:00.523 -> 29325594 !TSF:MSG:SEND,0-0-38-38,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
Running it through the log parser it would appear the gateway is responding to the find parent request.
BUT. The node it self seems to be failing to find parent periodically. Like it's not getting the message back from the gateway.
22:12:10.465 -> Going to sleep
22:12:10.465 -> 44562 MCO:SLP:MS=30000,SMS=1,I1=255,M1=255,I2=255,M2=255
22:12:10.465 -> 44572 !MCO:SLP:TNR
22:12:20.399 -> 54491 TSM:FAIL:RE-INIT
22:12:20.399 -> 54493 TSM:INIT
22:12:20.399 -> 54499 !TSM:INIT:TSP FAIL
22:12:20.444 -> 54501 TSM:FAIL:CNT=5
22:12:20.444 -> 54503 TSM:FAIL:DIS
22:12:20.444 -> 54505 TSF:TDI:TSL
22:12:20.489 -> 54575 MCO:SLP:MS=19999
22:12:20.489 -> 54577 !TSF:SND:TNR
22:12:21.035 -> 55080 TSF:TDI:TSL
22:12:42.255 -> 55083 MCO:SLP:WUP=-1
22:12:42.301 -> 55085 TSF:TRI:TSB
22:12:42.301 -> 55091 !TSF:SND:TNR
22:12:42.301 -> Awake Now
22:12:42.301 -> 1010
22:12:42.301 -> 3.29
22:12:42.301 -> Battery Voltage: 7.98 V
22:12:42.301 -> Battery percent: 94 %
22:12:42.301 -> sensorValue:1010
22:12:42.301 -> Going to sleep
22:12:42.301 -> 55099 MCO:SLP:MS=30000,SMS=1,I1=255,M1=255,I2=255,M2=255
22:12:42.301 -> 55109 !MCO:SLP:TNR
22:12:51.744 -> 64509 TSM:FAIL:RE-INIT
22:12:51.744 -> 64512 TSM:INIT
22:12:51.744 -> 64518 !TSM:INIT:TSP FAIL
22:12:51.744 -> 64520 TSM:FAIL:CNT=6
22:12:51.744 -> 64522 TSM:FAIL:DIS
22:12:51.744 -> 64524 TSF:TDI:TSL
22:12:52.330 -> 65112 MCO:SLP:MS=19999
22:12:52.330 -> 65114 !TSF:SND:TNR
22:12:52.829 -> 65617 TSF:TDI:TSL
@skywatch said in smart sleep inconsistent?:
#define MY_RF24_PA_LEVEL RF24_PA_HIGH
I have the node and gateway on my desk now for testing, so I am going to reflash with this now! Fingers crossed it helps. 
@skywatch said in smart sleep inconsistent?:
Looking at the code, send_status_message only ever sends 1 - is this what you want? It seems to never send anything else (like 0)....
battery is only sent when there is a change in the voltage.
@skywatch said in smart sleep inconsistent?:
Looking at the code, send_status_message only ever sends 1 - is this what you want? It seems to never send anything else (like 0)....
Where do you see that? i get 1 and 0 reported as needed based on the state.
@skywatch said in smart sleep inconsistent?:
Also you are using sleep but have a receive function - what happens to messages when the node is asleep?
That is what smartsleep does. It tells my controller (homeassistant) to queue up the messages. Which works fine, as long as the node wakes up.
@skywatch said in smart sleep inconsistent?:
Have you modified the pro mini as per the battery page on this site? Have you added capacitors to the radio module?
Correct, modified for battery use, and capacitors to the radio module.
@skywatch said in smart sleep inconsistent?:
directionControl seems like it will always turn off both digital pins regardless of the message as //disable are the last statements to be actioned?
This is correct, this is a directional H-bridge controller to pulse a latching solenoid valve, so I do not need them on but very briefly.
Another quick update. I hooked my gateway up to my computer to get some debug logs off it. I am not seeing ANYTHING coming from that node using smartsleep at all. So it does appear the issue is specifically with that node.
Since it's battery powered i am going to see if i can get serial connected up without a reset and see what's it saying but i have a feeling it's going to be what ive seen before and it's having a hard time finding a parent for some reason. Not sure how to fix that.
The 30 seconds is what is passed to the smart sleep function based on the smartsleep() documentation. In this case SLEEP_TIME = 30000. The other stuff in the code around the millis() check i understand would be halted, but I believe the smart_sleep is different based on the documentation.
#ifdef MY_DEBUG
Serial.println("Going to sleep");
#endif
smartSleep(SLEEP_TIME);
#ifdef MY_DEBUG
Serial.println("Awake Now");
#endif
@mfalkvidd sketch is here. I don't have the debug logs off the gateway, but ill hook up serial to it this weekend and get some logs. (i need to just make one of those bluetooth to ftdi adapters lol)
hardware is 3.3v arduino pro mini for the node and wemos d1 mini for the gateway.
/*
* The MySensors Arduino library handles the wireless radio link and protocol
* between your home built sensors/actuators and HA controller of choice.
* The sensors forms a self healing radio network with optional repeaters. Each
* repeater and gateway builds a routing tables in EEPROM which keeps track of the
* network topology allowing messages to be routed to nodes.
*
* Created by Henrik Ekblad <henrik.ekblad@mysensors.org>
* Copyright (C) 2013-2019 Sensnology AB
* Full contributor list: https://github.com/mysensors/MySensors/graphs/contributors
*
* Documentation: http://www.mysensors.org
* Support Forum: http://forum.mysensors.org
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License
* version 2 as published by the Free Software Foundation.
*
*******************************
*
* REVISION HISTORY
* Version 1.0 - Henrik Ekblad
*
* DESCRIPTION
* Example sketch showing how to control physical relays.
* This example will remember relay state after power failure.
* http://www.mysensors.org/build/relay
*/
// Enable debug prints to serial monitor
#define MY_DEBUG
// Enable and select radio type attached
#define MY_RADIO_RF24
//#define MY_RADIO_NRF5_ESB
//#define MY_RADIO_RFM69
//#define MY_RADIO_RFM95
#define MY_NODE_ID 18
int BATTERY_SENSE_PIN = A0;
// Enable repeater functionality for this node
//#define MY_REPEATER_FEATURE
#define CHILD_ID_HOSE 0
#define CHILD_ID_VOLT 1
uint32_t SLEEP_TIME = 30000;
#include <MySensors.h>
MyMessage msg(CHILD_ID_HOSE, V_STATUS);
MyMessage msgVolt(CHILD_ID_VOLT, V_VOLTAGE);
#define HOSE_ON 1 // GPIO value to write to turn on attached relay
#define HOSE_OFF 0 // GPIO value to write to turn off attached relay
int oldBatteryPcnt = 0;
int in1 = 5;
int in2 = 6;
unsigned long start_time;
unsigned long timed_event = 1000;
unsigned long current_time;
void before()
{
pinMode(in1, OUTPUT);
pinMode(in2, OUTPUT);
}
void setup()
{
#if defined(__AVR_ATmega2560__)
analogReference(INTERNAL1V1);
#else
analogReference(INTERNAL);
#endif
SendBatteryUpdate();
directionControl(HOSE_ON);
delay(100);
directionControl(HOSE_OFF);
}
void presentation()
{
// Send the sketch version information to the gateway and Controller
sendSketchInfo("Garden Soaker Hose Control", "1.0");
present(CHILD_ID_HOSE,S_BINARY);
present(CHILD_ID_VOLT, S_MULTIMETER);
digitalWrite(in1, LOW);
digitalWrite(in2, LOW);
current_time = millis();
start_time = current_time;
}
void loop()
{
static bool first_message_sent = false;
if ( first_message_sent == false ) {
Serial.println( "Sending initial state..." );
send_status_message();
first_message_sent = true;
}
current_time = millis(); // update the timer every cycle
if (current_time - start_time >= timed_event) {
SendBatteryUpdate();
start_time = current_time; // reset the timer
}
#ifdef MY_DEBUG
Serial.println("Going to sleep");
#endif
smartSleep(SLEEP_TIME);
#ifdef MY_DEBUG
Serial.println("Awake Now");
#endif
}
void SendBatteryUpdate()
{
// get the battery Voltage
int runningTotal=0;
for (int x=0;x<10;x++)
{
runningTotal=runningTotal+analogRead(BATTERY_SENSE_PIN);
}
int sensorValue=runningTotal / 10;
//int sensorValue = analogRead(BATTERY_SENSE_PIN);
#ifdef MY_DEBUG
Serial.println(sensorValue);
//973 = 4.05v
#endif
#ifdef MY_DEBUG
float batteryV = (sensorValue * 3.34) / 1024;
Serial.println(batteryV);
batteryV = batteryV / 0.7802721088435374;
//batteryV = batteryV / 0.4857457520453115;
batteryV = batteryV / 0.5291330073696145;
int batteryPcnt = (batteryV / 8.4) * 100;
Serial.print("Battery Voltage: ");
Serial.print(batteryV);
Serial.println(" V");
Serial.print("Battery percent: ");
Serial.print(batteryPcnt);
Serial.println(" %");
#endif
if (oldBatteryPcnt != batteryPcnt) {
// Power up radio after sleep
sendBatteryLevel(batteryPcnt);
send(msgVolt.set(batteryV,1));
oldBatteryPcnt = batteryPcnt;
}
Serial.print("sensorValue:");
Serial.println(sensorValue);
}
void receive(const MyMessage &message)
{
// We only expect one type of message from controller. But we better check anyway.
if (message.getType()==V_STATUS) {
// Change relay state
directionControl(message.getBool()?HOSE_ON:HOSE_OFF);
//digitalWrite(message.getSensor()-1+RELAY_PIN, message.getBool()?RELAY_ON:RELAY_OFF);
// Store state in eeprom
saveState(message.getSensor(), message.getBool());
// Write some debug info
Serial.print("Incoming change for sensor:");
Serial.print(message.getSensor());
Serial.print(", New status: ");
Serial.println(message.getBool());
}
}
void send_status_message()
{
send(msg.set(1));
}
void directionControl(int ONOFF) {
// Set motors to maximum speed
// For PWM maximum possible values are 0 to 255
// Turn flip circuit on for 1/4 second
if (ONOFF == HOSE_ON)
{
Serial.print("turning hose: ");
Serial.println(ONOFF);
digitalWrite(in1, HIGH);
digitalWrite(in2, LOW);
delay(250);
send(msg.set(HOSE_ON));
}
else
{
// turn off circuit for 1/4 second
digitalWrite(in1, LOW);
digitalWrite(in2, HIGH);
delay(250);
send(msg.set(HOSE_OFF));
}
// disable
digitalWrite(in1, LOW);
digitalWrite(in2, LOW);
}
additional information:
I have a node I setup and configured for smart sleep. It's set to check in every 30 seconds. But it's not consistent. I understand without a real time clock ect that it may not be 100% on the wake up procedure... but i am getting BIG gaps of time where it just isn't reporting in. The below graph is monitoring my mqtt broker and you can see big gaps and that is just over the last hour. 1 gap was for 12 minutes then ok for a bit, then a gap for 15. I monitored during my last meeting so i could confirm it wasn't me messing with something.
This has been going on for a couple weeks. The only thing I can think of is maybe it's doing the FPAR like I saw awhile back. I have changed out the arduino, changed the radio, changed to another radio from a different batch.
Not sure if anyone has any experience with the smart sleep, but so far it doesn't seem super reliable. Not enough so for me to be willing to have it not turn off my water for a couple hours till it decides to wake up after flooding my neighbors drive way.... not speaking from experience or anything lol
Small update. I switched to a radio from different batch and seemed like that fixed it. Saw the smart sleep message in mqtt until I went to bed. But around 4:30am it stopped again. Im going to go pull it again and see what it's outputting. I feel like I need to hook up a bluetooth hc-05 or something so i can just connect over bluetooth at this point to get the serial data lol
Well. I swapped the radio. No change. Reset the arduino. No change. So may be time to swap the arduino.
I was able to get the module inside without powering it off and serial connected. So I was able to get some logging from while it's in it's broken state!!
2541717 MCO:SLP:MS=30000,SMS=1,I1=255,M1=255,I2=255,M2=255
2541725 !MCO:SLP:TNR
2543659 TSM:FAIL:RE-INIT
2543661 TSM:INIT
2543669 TSM:INIT:TSP OK
2543671 TSM:INIT:STATID=18
2543673 TSF:SID:OK,ID=18
2543677 TSM:FPAR
2543679 ?TSF:MSG:SEND,18-18-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2545688 !TSM:FPAR:NO REPLY
2545690 TSM:FPAR
2545694 ?TSF:MSG:SEND,18-18-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2547703 !TSM:FPAR:NO REPLY
2547705 TSM:FPAR
2547709 ?TSF:MSG:SEND,18-18-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2549719 !TSM:FPAR:NO REPLY
2549721 TSM:FPAR
2549725 ?TSF:MSG:SEND,18-18-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2551730 MCO:SLP:MS=19999
2551732 !TSF:SND:TNR
2551736 !TSM:FPAR:FAIL
2551738 TSM:FAIL:CNT=7
2551740 TSM:FAIL:DIS
2551742 TSF:TDI:TSL
2552236 TSF:TDI:TSL
2552238 MCO:SLP:WUP=-1
2552240 TSF:TRI:TSB
2552248 !TSF:SND:TNR
Awake Now
1002
3.27
Battery Voltage: 7.92 V
Battery percent: 94 %
sensorValue:1002
Going to sleep
2552256 MCO:SLP:MS=30000,SMS=1,I1=255,M1=255,I2=255,M2=255
2552264 !MCO:SLP:TNR
2562269 MCO:SLP:MS=19999
2562271 !TSF:SND:TNR
2562775 TSF:TDI:TSL
Based on the parser. It seems it can't find a parent. I even plugged in my repeater and it's still saying the same thing. Haven't reset it at all yet, but kind of seems like maybe it's a problem with the radio?
Thanks Yeah super odd it just kind of stops. I can see the special "smart sleep" messages telling HA to go to sleep and then they just stop. I even took a repeater out of the equation to see if it was the repeater and the other nodes were going directly to the gateway, so now I only have the gateway and no change. Very strange.
For the debug i would need to pull the node apart and bring inside and hook serial pins up to the computer. I can and will. Just need to wait for my meeting to end so I can leave my desk.
For the sketch. Here it is.
// Enable debug prints to serial monitor
#define MY_DEBUG
// Enable and select radio type attached
#define MY_RADIO_RF24
//#define MY_RADIO_NRF5_ESB
//#define MY_RADIO_RFM69
//#define MY_RADIO_RFM95
#define MY_NODE_ID 18
int BATTERY_SENSE_PIN = A0;
// Enable repeater functionality for this node
//#define MY_REPEATER_FEATURE
#define CHILD_ID_HOSE 0
#define CHILD_ID_VOLT 1
uint32_t SLEEP_TIME = 30000;
#include <MySensors.h>
MyMessage msg(CHILD_ID_HOSE, V_STATUS);
MyMessage msgVolt(CHILD_ID_VOLT, V_VOLTAGE);
#define HOSE_ON 1 // GPIO value to write to turn on attached relay
#define HOSE_OFF 0 // GPIO value to write to turn off attached relay
int oldBatteryPcnt = 0;
int in1 = 5;
int in2 = 6;
unsigned long start_time;
unsigned long timed_event = 1000;
unsigned long current_time;
void before()
{
pinMode(in1, OUTPUT);
pinMode(in2, OUTPUT);
}
void setup()
{
#if defined(__AVR_ATmega2560__)
analogReference(INTERNAL1V1);
#else
analogReference(INTERNAL);
#endif
SendBatteryUpdate();
}
void presentation()
{
// Send the sketch version information to the gateway and Controller
sendSketchInfo("Garden Soaker Hose Control", "1.0");
present(CHILD_ID_HOSE,S_BINARY);
present(CHILD_ID_VOLT, S_MULTIMETER);
digitalWrite(in1, LOW);
digitalWrite(in2, LOW);
current_time = millis();
start_time = current_time;
}
void loop()
{
static bool first_message_sent = false;
if ( first_message_sent == false ) {
Serial.println( "Sending initial state..." );
send_status_message();
first_message_sent = true;
}
current_time = millis(); // update the timer every cycle
if (current_time - start_time >= timed_event) {
SendBatteryUpdate();
start_time = current_time; // reset the timer
}
#ifdef MY_DEBUG
Serial.println("Going to sleep");
#endif
smartSleep(SLEEP_TIME);
#ifdef MY_DEBUG
Serial.println("Awake Now");
#endif
}
void SendBatteryUpdate()
{
// get the battery Voltage
int runningTotal=0;
for (int x=0;x<10;x++)
{
runningTotal=runningTotal+analogRead(BATTERY_SENSE_PIN);
}
int sensorValue=runningTotal / 10;
//int sensorValue = analogRead(BATTERY_SENSE_PIN);
#ifdef MY_DEBUG
Serial.println(sensorValue);
//973 = 4.05v
#endif
#ifdef MY_DEBUG
float batteryV = (sensorValue * 3.34) / 1024;
Serial.println(batteryV);
batteryV = batteryV / 0.7802721088435374;
//batteryV = batteryV / 0.4857457520453115;
batteryV = batteryV / 0.5291330073696145;
int batteryPcnt = (batteryV / 8.4) * 100;
Serial.print("Battery Voltage: ");
Serial.print(batteryV);
Serial.println(" V");
Serial.print("Battery percent: ");
Serial.print(batteryPcnt);
Serial.println(" %");
#endif
if (oldBatteryPcnt != batteryPcnt) {
// Power up radio after sleep
sendBatteryLevel(batteryPcnt);
send(msgVolt.set(batteryV,1));
oldBatteryPcnt = batteryPcnt;
}
Serial.print("sensorValue:");
Serial.println(sensorValue);
}
void receive(const MyMessage &message)
{
// We only expect one type of message from controller. But we better check anyway.
if (message.getType()==V_STATUS) {
// Change relay state
directionControl(message.getBool()?HOSE_ON:HOSE_OFF);
//digitalWrite(message.getSensor()-1+RELAY_PIN, message.getBool()?RELAY_ON:RELAY_OFF);
// Store state in eeprom
saveState(message.getSensor(), message.getBool());
// Write some debug info
Serial.print("Incoming change for sensor:");
Serial.print(message.getSensor());
Serial.print(", New status: ");
Serial.println(message.getBool());
}
}
void send_status_message()
{
send(msg.set(1));
}
void directionControl(int ONOFF) {
// Set motors to maximum speed
// For PWM maximum possible values are 0 to 255
// Turn flip circuit on for 1/4 second
if (ONOFF == HOSE_ON)
{
Serial.print("turning hose: ");
Serial.println(ONOFF);
digitalWrite(in1, HIGH);
digitalWrite(in2, LOW);
delay(250);
send(msg.set(HOSE_ON));
}
else
{
// turn off circuit for 1/4 second
digitalWrite(in1, LOW);
digitalWrite(in2, HIGH);
delay(250);
send(msg.set(HOSE_OFF));
}
// disable
digitalWrite(in1, LOW);
digitalWrite(in2, LOW);
}
Thanks for taking a peek!!
I have a small battery powered node I am using with smartsleep. For some reason though, it seems that after either a certain timeframe or certain number of iterations it just stops waking up and sending the pre/post smartsleep messages.
I reset it and was watching the mqtt topic. You can see it's consistently reporting in roughly every 30 seconds or so. Just as expected. But then it just stops dead. I sent a state change command via home assistant and the state never changed, the node just seems to be stopping dead after X amount of time/iterations. Oddly enough I saw over the last few days, it will eventually wake up. I had it wake up yesterday morning at 1:46am and today at 4:36am. But when I have it configured to wake up every 30 seconds, doing once a day isn't going to work (im going to flood my yard that way) lol
I am running mqtt esp gateway, all my other nodes and everything are still functional, so i do not believe it to be the gateway or mqtt. I am running 2.3.2 on the gateway and node in question. Using the easypcb/newbie board with a pro mini and all the necessary capacitors.
Any thoughts or suggestions?
@ejlane Correct. 7 nodes = 7 machines. BUT, the 7 current machines are 7 raspberry pi 4 (8gig Ram) modules. it is 1/2 of what my goal is. Eventually it will be a full 14 node cluster.
I had been doing something similar with the pi satellites. I found that if you tell it to use a UDP broadcast to localhost for the wakeword/recording then it doesn't send the audio frames to the mqtt broker.
if you want to play with some ws2812 stuff. i HIGHLY recommend looking at the wled project from aircookie. uses a wemos d1 mini. flash the firmware and off you go. integrates into EVERYTHING. tons of built in lighting effects and some crazy extras like supporting e1.31 protocol so you can add your led strips to christmas light shows using stuff like xlights, vixen2 and falcon pi player.
I haven't really tested pico but I would guess there is a way to use it as a drop in just like i have with my current marytts.
As far as the kubernetes, the reason I use that is 2 main reasons.
github would be awesome!!
I commented in the other thread too
I have been playing with Rhasspy on and off since the snips debacle. I recently got a little more in to it and have a neat little setup so far.
I have an instance of rhasspy running on a pi3 with a docker container. That container will soon be moved to something more powerful, but for now it's working quite well. That pi just has a set of simple speakers and an old playstation eye webcam (for the microphone).
Then I have a small pi zero w with a respeaker 2 mic hat and a tiny like 2 inch "mini loud speaker". That pi obviously has little power, but I have all the heavy lifting being done by the other pi. So the zero is doing the wake word detection, audio record, speech to text (for the moment) and audio playback.
The other pi is doing the same things but also intent analysis and intent handling. Both pi's are sharing an mqtt broker on my network. So the pi3 is actually processing intents and intent handling for itself AND my little satellite module.
My text to speech is currently using a docker container of marytts running on yet another machine and handles the tts for both pis.
For anyone that knows me and my setup, I am a big kubernetes guy, so stuff like the marytts, intent handling, intent analysis all those things are being moved into my cluster. Then all my pi's can basically share the same "brain" as it were.
My whole system for this just like my home automation is designed to run local. Which is why I am not using google's speech to text or amazon polly or something like that. I know those are more natural sounding and realistically if I need to switch it later it's easy.
Rhasspy has DEFINITELY made it nice to swap pieces in and out and made it very modular.
Alright... you got me... im interested. Have some questions lol.
Not sure if you have looked into the rhasspy project for your smart speakers. I am currently working on that myself. I have my first one built and testing satellites with a main "brain" running on a beefier piece of equipment.
has anyone thrown this in a docker yet?
Ah nice. Thanks for the response. I used to get environmental fluctuation's with my ultrasonic sensor I used. I couldn't tell if it was from the air temp between the sensor and the top of the water changing or the barrels themselves heating up and slightly expanding and contracting in the sun through the day or both.
But it was small like you said so I wasn't concerned. I have 4x55 gallon drums (around 832 liters) total. So I am wondering if maybe pressure sensor would work..
Thanks for the idea. Definitely interested in testing it. I have ball valves already on the barrels so it won't be difficult to make a little connector rig to test
@CrankyCoder ok. so i made myself go learn something new. Water Pressure Depends Only on Depth, Not Container Shape – 14:57
— G Chang
So IF I used a pressure sensor like the one mentioned above the pressure of 1 barrel half full is the same as 4 half full connected. So... It would seem that I COULD do measure my volume with 1 sensor and taking in to account how many barrels are open. (I have shut off valves so I can disconnect to repair/clean as needed)
Random question. I have 4 rain barrels all connected via connectors. Would a pressure sensor like this work for measuring the liquid in that? Not sure how that would affect the reading.
I have done some digging around and and I am not 100% sure or not but I do not recall if the relay module in the node is optoisolated, so that could be part of the interference if you think that could be the issue. I am pretty sure the 5v power for the relay module and the arduino are coming from the same 5v psu BUT I am 99.99% sure I do not have a cap across the 5v/gnd on the relay module, so I guess I could pull that module out and see about replacing it with an optoisolated one (if it's not isolated) and put a decoupling capacitor on the relay module itself.
Just some thoughts.
I would need to leave something connected all the time wouldn't I? Hooking laptop to the arduino would cause the reset?
The relay module is a purchased 2 relay board for the arduino, 5v logic.
I have a 2 relay node in my master bedroom running 2.3.2. Gateway is pi gateway running the same version. Node is built with the easy/newbie board. It’s a decent distance away from the gateway, periodically something happen and I guess it stops being able to communicate. But oddly enough, it never seems to try to reconnect. I thought the built in watchdog should get it to go back to find parent or something.
If I unplug the module and plug back in, reconnect, all is well.
Just wondering if anyone has any advice for getting nodes to retry to connect to gateway better. I feel I’m missing something simple in the stability aspect here.
I am finally getting around to trying this out. I was playing with just trying to see if i can get the pulses. First thing i did was take an old compass and put it beside the meter and had someone turn on the water. I could definitely see the compass needle pull a little as the water was flowing. So I assumed that pull was enough to be detectable with my hall effect sensor. I have tried a couple, and just can't seem to get it to pick up.
If i use a magnet, simple code will detect the pulse and the green led on the sensor lights up.
But no matter where I put that sensor near the meter it just doesn't seem to detect it. Not quite sure what's happening.
The meter i have is this one.
https://www.badgermeter.com/resources/add29b88-1ffb-49c9-80ab-bb8697bd6d1a/absolute digital encoder product data sheet ade-ds-00183-en.pdf/
Not sure if anyone has any recommendation on which hall effect sensor would be the best for this but ill take suggestions lol
My sensor I am testing with is
3144E Hall Effect Sensor
Doesn't have a sensitivity dial but the recommended one on this build page didn't either.
I second this. I went the mqtt route as well. Auto discovery is cool, but i wanted some additional control. My openhab 2.5 I don't use the UI at all. I just all flat files. This is a preference for me. I also use the VSCode extension for openhab and it works BEAUTIFULLY!
Do you have any install documentation for it? Any docs for integrating into existing snips setup?
I am going to be checking this out. I have been working with snips on some other stuff, so this could be very interesting.
@zboblamont actually it was more of a "not completed" type of thing. i didn't finish the connection between the bottom part that houses the sensor and the top cap. so it got knocked over and water soaked in. so i will be redoing it and will just complete it this time
I made a sensor like this myself. i took a non-water proof one and drilled holes to match the sensor in some plexiglass. and sealed around it with silicone. This worked until florida tried to drowned me out and flooded my entire sensor housing lol
I ended up setting up some monitoring that if by some chance it does go belly up my monitoring will do a recovery action. But it does still happen from time to time, which is strange.
I recently had alot of issues with my pi gw too. One of the things I found REALLY helped was on my switch I set the speed and duplex to 100mb FULL. In my syslog around the time my GW stopped responding, I was seeing messages about the "carrier lost" on the nic. Not sure what caused that, but it seems like it was taking quite some time to renegotiate. Now that I have it set to 100 FULL my issues have gone from 1-2 a day to only once in 3 weeks.
Also, make sure you have plenty of power for your PI. I have noticed one of the first things that seems to flake out on me when i have a sub par power supply for the PI is the network.
Not sure it my experience will help but figured I would try
So here's the latest.
I checked and the PI was already set to static ip and not dhcp reservation. However, I made 2 changes and have been ok for 3 days now.
I still have the debug running and gonna let this run for quite some time just to make sure im feeling it's ok.
compiled with new (very noisy) options lol
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
No idea what that means, but it seems if i am seeing that, it's working lol.
@mfalkvidd compiling now. side question, can the ip address be put in the config later? i hate that i have to hard code it in at compile time.
@mfalkvidd do i need to modify the pi code and add that in and recompile? or can i add those in to the config file in /etc/mysensors.conf?
So I have a new development. I noticed something strange. The mysgw stopped again today. I went digging through the syslog around the same time. Didn't see anything just before it went offline, but i did notice that shortly after it went offline it said that the carrier dropped for the nic.
Apr 2 15:50:55 raspberrypi mysgw: TSF:MSG:READ,200-200-0,s=2,c=2,t=25,pt=0,l=0,sg=0:
Apr 2 15:50:55 raspberrypi mysgw: GWT:TPS:TOPIC=mygateway1-out/200/2/2/0/25,MSG SENT
Apr 2 15:51:07 raspberrypi mysgw: TSF:MSG:READ,200-200-0,s=2,c=1,t=23,pt=2,l=2,sg=0:25
Apr 2 15:51:07 raspberrypi mysgw: GWT:TPS:TOPIC=mygateway1-out/200/2/1/0/23,MSG SENT
Apr 2 15:52:27 raspberrypi dhcpcd[377]: eth0: carrier lost
Apr 2 15:52:27 raspberrypi kernel: [ 461.474897] smsc95xx 1-1.1:1.0 eth0: link down
Apr 2 15:52:28 raspberrypi dhcpcd[377]: eth0: deleting address fe80::669:d81d:83fb:3aaa
Apr 2 15:52:28 raspberrypi avahi-daemon[226]: Withdrawing address record for fe80::669:d81d:83fb:3aaa on eth0.
Apr 2 15:52:28 raspberrypi avahi-daemon[226]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::669:d81d:83fb:3aaa.
Apr 2 15:52:28 raspberrypi avahi-daemon[226]: Interface eth0.IPv6 no longer relevant for mDNS.
Apr 2 15:52:28 raspberrypi dhcpcd[377]: eth0: deleting default route via 192.168.2.1
Apr 2 15:52:28 raspberrypi dhcpcd[377]: eth0: deleting route to 192.168.2.0/24
Apr 2 15:52:28 raspberrypi avahi-daemon[226]: Withdrawing address record for 192.168.2.71 on eth0.
Apr 2 15:52:28 raspberrypi avahi-daemon[226]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.2.71.
So i decided to check a few other times in the last 48 hours and sure enough. Same thing. It seems that something is causing the nic to think it lost it's connection to the switch. The mysgw seems to go in to a weird state. Not sure what error checking is in it or what i could do to log more since i am already on debug for the logging of mysgw.
Next step i guess will be instead of dhcp reservation ill static assign it. See if that changes anything, and see swap network cable. Maybe hard set some things like the speed/duplex on the switch.
Just figured i would throw out my latest finding.
I read that the irq thing may not be necessary. I haven't setup the irq on mine. I don't have that much traffic for the irq to be needed yet.
anyone else using the irq on the pi gateway?
dev branch was installed last night. So far so good. Logs are flushing to disk must faster as previously indicated. But i did see this when i went back to the pi gateway code... lol
I wonder if that's what I am up against haha. Ill post an update over the next couple days.
This is running pi gateway with the radio directly to the pi. No pro mini.
Brand new pi 3 power supply. I swapped out my 4.7uf with a 47uf capacitor and thought that fixed it, but the mygw stopped working again today at 3:54pm.
a service restart fixed it. Didn't reboot the pi or do anything other than just issue a restart on the mygw software.
So I have to think maybe it's the software. I may have to go back a version from 2.3.1 to something prior. Or maybe roll forward on the dev branch.
Sorry, I spaced on that. It's not sending messages any more. like the process is hung up.
This is version 2.3.1 mqtt pi gateway.
I have a pi gateway i just built this week.
A strange scenario has presented itself, not sure how to proceed but it's definitely reducing my reliability.
so the status of the mysgw service is running.
But as you can see. The last log message was last night at 11:06PM. But the service is still running. I see the process in ps.
The log output just abruptly stopped a few minutes before that. (i did a cat on the log)
It's in debug right now, so the log is large, but currently only 78megs total.
As of right now the state is exactly like that. I have not killed the process to restart it. I wanted to leave it exactly as is in case anyone has any ideas.
Any sort of watch dog I can do with this maybe?
Thanks!
The space heater was pretty close in proximity and never noticed it cause... well i live in florida, i only use it like 3 times a year lol.
But, i also know this house (built in the 70s), had someone do the electrical that i have to question many a decision. Some outlets not grounded. There is an outlet in my kitchen that only turns on when the switch for the garbage disposal is running.... i haven't found exactly what device would only be needed when the disposal is running... but it's a mission i am on...
So i think throwing some caps on the input side of things is still worth a shot.
So a little new info. Last night i had the lights turn off with the door closed, and no one turned on/off the kitchen/bathroom lights. But what did happen, I turned off a little space heater in my room. When i turned it off, the lights off. Finding this very interesting, i grabbed my phone (in the dark) and check the HA status. The motion detection was triggered... ok... so maybe it's not the PIR/repeater that's the issue...
It's the LIGHT MODULE!! There is a good chance that the power fluctuations aren't messing with the repeater itself, but actually resetting the arduino with my lamp relays. I think this weekend i need to pull that out, check the code to see if i am saving state to eeprom and also throw some capacitors on the incoming power to see if that helps.
@zboblamont good to know! I have 2 florescents in my garage that i swapped for LED. These didn't need to bypass the ballast. Might be worth a test to swap those out for the ones in the bathroom (where i see the most interference)
Guess i know what im going to try when i get home!
@dbemowsk oh yeah, for the radio i have a capacitor. Just not for the main power coming in to the board. I have bags of capacitors so this should be an easy test to see if it helps
@dbemowsk no caps, definitely worth a shot, i figured since i was powering it off a usb port off another device it would already be cleaner power. but have been considering moving location anyway and changing out to some other power. I was looking at this post (https://forum.mysensors.org/topic/9550/build-a-reliable-power-supply-chain/9) and considering maybe trying something like that.
im using wireless, nrf24l01.
Wondering if possibly there is a weird power fluctuation and it's causing the arduino to reset. or if there is something in the light on/off that is messing with the PIR.
an interesting note, and it just occurred to me. Both the bathroom and kitchen lights, the reason they aren't automated is they are both florescent lights... i wonder if that has anything to do with it.
Ah yes. That’s the part that probably makes this strange and I obviously omitted. Both kitchen and bathroom lights are not controlled at all with mysensors or openHAB. Just normal dumb switches. But it happens regularly enough that I don’t think it’s coincidence anymore
I have a small PIR motion sensor setup to detect motion when I walk in to my bedroom. I have not reconfigured my openhab setup to just turn off X amount of time later, so it just turns off when the motion is no longer detected. However, I have noticed a strange behavior. If I walk in to the room, and one of the kids turns off the bathroom light or the kitchen light, my lights in the bedroom turn off. When I check openhab it definitely shows the lights are off, but it also shows that the motionsensor is not triggered. Almost like something happened at that moment causing the the PIR to report no motion, or the whole repeater node to reset. In either case, im surprised motion isn't retriggered. If i leave the room for a bit and walk back in all is normal.
Anyone ever heard of anything like that? Is it something messing with the PIR? maybe weird power fluctuations?
I am considering making this for that exact purpose.
https://www.openhardware.io/view/532/The-Logger-Machine-Short-and-long-term-serial-logging
Otherwise maybe just hook a laptop up with a putty session configured to just output the entire session to text file.
any plans to add an RTC on this and be able to timestamp the log entries? I have some sensors that only wake up and do readings every 90 minutes. But sometimes they just stop doing it. So time stamps on the logs would be good to see if there is anything happening right around the time it stops reporting.
@alexsh1 the reason i am using the 18650's is the fact i have a steady stream of them coming in for my large battery packs. I have a couple hundred that aren't dead but just aren't quite up to to the standard i am putting in my big packs.
@rozpruwacz gonna have to check in to this. i have lots of 3.3 but no 3.0 ldo's
I have a the fantastic newbie pcb board from @sundberg84 and I am making a small pool temp sensor with it.
I am running in to some issues though and wondering if anyone has some ideas. So a fully charged 18650 can get up to 4.2v so I need to regulate it. I was looking to put the battery in through the RAW pin that way the VCC would be 3.3v. However, that is only good until the battery drops below 3.3. The 18650's I am using can go to 3.0 pretty easily, datasheet even says 2.8. 3 is kind of where I would like to limit it though. So I have a little 3.3v boost converter. But when it's over 3.3v not sure if it's going to damage the boost converter (guessing yes).
So i am curious if it's possible to be able to use the newbie board, have the battery voltage monitored. Handle a fully charged 18650 and be able to use the boost converter if the battery drops below 3.3v.
Thanks!
Hey everyone! A buddy of mine is venturing in to a little farming on some unused land at his parents exotic fish farm... yes for real. lol.
He wants to automate a bit of, mainly monitoring the moisture level and open a solenoid valve to water it. The base station will be at the edge of the property. I got some info today from him, said the furthest distance between sensor and base station is going to be maybe 60 yards. Im guessing mesh probably won't be needed in this scenario, so no repeaters.
I think openhab would be WAY overkill for what he is wanting to do here with literally just a couple of actuators and a couple sensors. He does want to be able to see graphs over time of stuff. I like like the idea of using mysensors for this just so we don't have to reinvent the wheel.
The gateway would be on a raspberry pi since that's where his software would most likely run too.
Now that I have provided some info. Anyone have any suggestions on maybe a piece of software for this? any suggestions? clarifications?
Thanks!
Woah. very cool. going to look in to those some more.
I agree, I am wondering if just doing a small pcb, oled screen and some smd parts would be easier.
I don't want to wear extra stuff either. Definitely got me thinking though.
So, I have looked in to this. I even had a fitbit that i was hoping to use to determine if I fell asleep at night and turn off lights in my home automation system.
The down side I ran into is this. I had fitbit setup with ifttt since that was something it could interface with. The sleep detection worked. HOWEVER. It only actually posted info to IFTTT when you woke up, at that point, all sleep related data was submitted. So it didn't track it real time.
I have been looking in to how to integrate sleep in to my HA but also like you mentioned quality of sleep. The fitbit utilizes motion to determine "restless" sleep. Attaching a bunch of sensors to myself doesn't seem like it would yield comfortable natural sleep. So potentially stuff like a mesh of piezo sensors under a mattress topper would work. that would detect when the values change indicating turning, movement.
Temperature should be easy (fitbit probably does it, i had a cheap one so it did not).
If you want to get crazy (which if i had time i would go this route) you can get a fitness watch with a certain chip in it, and reprogram it.
https://www.youtube.com/watch?v=SBHyQ1OSM-4
That's what he did. This could be REALLY REALLY cool. You could code in your own parameters and what not, since it's bluetooth LE you could track it via phone or just remote sensors.
Once you have some basic "restless" night tracking you could do some experimenting (even with the fitbit).
If you make any progress, definitely let me know, i would be interested to see what you come up with!
I would be really interested to see this put in practice. For stuff like those sensors I can't imagine a little extra latency being a terrible thing.
Kind of makes me want to make a bunch of battery/solar nodes and just hide them places and see how far you can get a network to go
Does adding ack to messages help trigger any failures if something can't deliver? ... well that didn't make much sense.
So lets say i have 2 repeaters on my network. i have a sensor that wakes up to report info. it normally goes to repeater1 -> gateway but repeater1 is acting up. Could you tell it to wait for an ack? after X amount of time with no ack would it trigger to find a new parent?
I am about to put some door sensors up around my place. I love this idea of battery powered motion+door sensor. Just wondering if anyone has looked at something like the 18650's? The reason I ask is I have literally HUNDREDS of them from another on going project. Tons that aren't big enough for what I am working on but for uses like this it could work.
Morning all! I have a 2 node lamp relay in one of my rooms and have this really weird issue, thought it was coincidence for a long time but there is no way it can be. The issue is, fairly frequently when either the bathroom light is turned off, or the kitchen light (guessing both are on the same circuit) the lights that are on the relays will get turned off. I know there has to be something as far as noise on the AC line because my tv in the living room will flicker like the hdmi input just got interrupted.
The module is powered from the AC using a small AC-DC 5v converter.
So. I know the obvious answer... replace all your house wiring..... however at the moment this is not really an option. So I was wondering if anyone has any suggestions on maybe a way to filter the noise? or do you think it's just a too cheap module that some like the HLK-PM01 should be used.
Thanks!
mfalkvidd im sure you can confirm if i have my understanding correct here. If you have a repeater and it's gone, the nodes will eventually try to do a find par(ent) again right? at that point they may or may not be able to rejoin the network?
This should be pretty easy. Install your Home Assistant, then follow the pi gateway instructions. Shouldn't have any issues with it conflicting.
not sure about in sleep mode. But here is the sensor i am using.
https://smile.amazon.com/gp/product/B00Q9YBIJI/ref=oh_aui_search_detailpage?ie=UTF8&psc=1
no, i have a couple that i am running at 3.3 off the 18650s. so far it's been pretty good just using the sleep
@david-cabañero Thanks David, i just got a few of the step ups so I will give that a shot. Because of some of my other projects I have TONS of 18650 cells laying around so I figure those are decent batteries for this.
Do we need to upgrade everything? gateway/nodes? or is there some compatibility?
I did an upgrade the other week from 1.8 to 2.2. Then right about the time I had some stuff working 2.3 came out. So I figured since I have to do all the learning curve anyways I might as well stick with 2.3. The variables being presented in mysensors would be HUGE for me. But hopefully it's not too far out.
nice
I ordered a couple of sensors yesterday so as soon as they come in ill start doing some testing with them.
my setup is still just using the direct mqtt subscription so i will hold off.
is there any discovery working (in 2.2 that is) how about once you configure the things. do you get all the properties of that item from when it presents?
I swear I did a search. But apparently I searched on one of my other community forums that had nothing to do with arduino or mysensors 
helps when i search the right forum.
Hey All,
I have done some stuff with normal buttons and interrupts to wake up a node. I am wondering if anyone has done other stuff on the interrupts? Like a moisture/water sensor? im checking the feasibility of doing battery powered leak sensors. Seems like it would work since it's basically doing a button press by conducting through the water.
Now, I know what the first response is.... just try it!! I would, but alas i don't have my water sensors here yet
thanks!
How close is this for 2.3? Worth a try? or should I hold? Thanks for the work so far on it!
@monte i was just wondering if it could use the sparkfun, since you can do an enroll without saving it to the internal and have the template it generates dumped to a var. Then you can do a finger capture without having it try to identify and dump that to a var.
Ill dig in to the adafruit one and see what i can find
do you know if this will work with the sparkfun library?
https://github.com/sparkfun/Fingerprint_Scanner-TTL
I ordered one of those scanners to test with. But aliexpress.... gonna be a bit lol
I guess you could do it with a dummy color item. Not associate it with a specific. Then have a rule that when the dummy item is updated, then loop through the items in the group, or just send it to the X number you have.
Is the fingerprint data stored in the sensor itself? or somewhere else?
Can you not add them all to a group, then send a group command? or does that not work with stuff other than on/off? I have never done that so I am guessing.
Im using an 18650. currently it's sitting around 3.9v.
Do you have a link to the proper "mysensors" way of handling watch dog? Im not opposed to trying it. Especially if it gets hung up trying to do something then maybe the WDT while it's awake may help.
Where do you put your enable/disable watchdog? My node sleeps for 90 minutes at a time. Do you mean like a voltage booster? no, but i am monitoring the battery voltage so i know when it gets close to the 3.3 that the radio needs.
This is a cool idea. Definitely worth throwing some bigger batteries at it for debugging. I am looking for this bridge stuff now
just the sensor. Node is in box outside of the pool.
I have definitely thought of throwing a repeater in the room closest to where it is outside. That could definitely help. Can't move it closer since it's a temp sensor in my pool lol.
Wonder if i made a connector out of rj45 if it would work over that length to something inside
i fully agree. But my sensor bombs out after a week or so of running. It's just a temp sensor used from the examples. Only thing I did was change the sleep timeout. So i am thinking either there is something with the cheap pro mini clones. Or something with the radio not sending. Which could be it, for all I know it's waking up and the arduino is saying everything is good but the radio isn't working. The only thing I know for certain is a reset brings it all back online.
Quite possible the packets are lost in the RF transmission. Just difficult to leave a serial monitor hooked up to it outside for a week till it dies lol.
hmmm possible. power consumption would be a concern. having a second node running granted it wouldn't have a radio. I could potentially do the same thing with an attiny85 as it's smaller and lower power. It gets the cost down a little too... about to the same price as as the TPL5010. lol. in a pinch a pro mini would definitely work. Since I have some attiny85s that may be my option right now since i have them and don't have to buy the TPL5010's.
I think Jon Oxer did something with a hardware external watchdog like that. I am now wondering if i could use the attiny85, have it sleep as well. Wakeup hourly to see if it should reset the sensor. But also wake up on interrupt, where in the sensor if it's running well would pulse to the attiny. The tiny would reset the counter. Then each hour if the tiny wakes up, and the sensor hasn't reported in a couple hours, it would just reset it.
This is an actual possibility. lol