Here's the single PCB version of the LoRa motion detector:
It works as expected. The entire board is roughly the size footprint as the 3x AA batteries that are a part of it. Thanks to @NCA78, it's using an XC6206 LDO.
I just received a 3D printer kit today. I suppose the next step will be to print a 3D case for it. Ideally I'd like to make it waterproof/moistureproof so that it can also work outdoors.
0.45mm pitch, it will be a pain to hand solder and the big ground pad at the bottom is out of reach, get a stencil.
soldering paste and soldering dryer
It's very simple
No stencil?
@toyman Looks like a DIY watch, using one of the very small nRF52 modules and a small OLED screen (or maybe ePaper?) would be fairly easy to design and put together.
https://www.aliexpress.com/item/Free-shipping-Latest-Big-time-wearable-devices-DIY-electronic-watch-programmable-watch-FOR-ARDUINO/32309696848.html?spm=2114.search0104.3.43.6855283fBpRmHN&ws_ab_test=searchweb0_0,searchweb201602_5_10152_10065_10151_5711320_10344_10068_10130_10324_10342_10547_10325_10343_10546_10340_10341_10548_10698_10545_10697_10696_10084_5722520_10083_10618_10307_5711220_10059_5722620_5722920_308_5722720_5722820_100031_10103_441_10624_10623_10622_10621_10620-10152,searchweb201603_25,ppcSwitch_5&algo_expid=e4147df1-7362-4700-8575-4d5fa986cd9a-6&algo_pvid=e4147df1-7362-4700-8575-4d5fa986cd9a&transAbTest=ae803_1&priceBeautifyAB=0
Making it aesthetically pleasing is probably much harder! Still, maybe a DIY bridge would tide you over until a more proper watch is available for conversion. Interestingly, it looks like they made their case from stacked pieces of laser cut acrylic.
Unfortunately, theirs is impractically large:
@alowhum Doesn't answer your question, but I use just regular FTDI to listen to the serial output from the nRF5. So, there's always that for you to fall back on.
@berkseo Thanks! I just ordered it to test how easy/hard it is to solder. If I can manage that, then I may switch over to it.
@alowhum I'm not sure the function call that reveals that amount of free memory available, but I'm sure there must be one. Logging that as a diagnostic would reveal whether you have a memory leak in your code.
It's a good question, and it deserves a good answer. Since a gateway will probably be mains powered, rather than battery powered, I'm guessing that an LDO with less ripple and/or more noise rejection might improve the range/coverage of the gateway. i.e. just slapping in the cheapest, most common chips might be self defeating. That's too vague an answer though, and I'm sorry I can't do better. Has anyone looked into that angle?
I tried running the MySensors LoRa motion sensor code to connect with the MySensors LoRa serial gateway code:
MyS Duino
/**
* 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-2015 Sensnology AB
* Full contributor list: https://github.com/mysensors/Arduino/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
* Motion Sensor example using HC-SR501
* http://www.mysensors.org/build/motion
*
*/
// Enable debug prints
// #define MY_DEBUG
// Enable and select radio type attached
//#define MY_RADIO_NRF24
//#define MY_RADIO_NRF5_ESB
//#define MY_RADIO_RFM69
#define MY_RADIO_RFM95
#include <MySensors.h>
uint32_t SLEEP_TIME = 120000; // Sleep time between reports (in milliseconds)
#define DIGITAL_INPUT_SENSOR 3 // The digital input you attached your motion sensor. (Only 2 and 3 generates interrupt!)
#define CHILD_ID 1 // Id of the sensor child
// Initialize motion message
MyMessage msg(CHILD_ID, V_TRIPPED);
void setup()
{
pinMode(DIGITAL_INPUT_SENSOR, INPUT); // sets the motion sensor digital pin as input
Serial.println("Starting....");
}
void presentation()
{
// Send the sketch version information to the gateway and Controller
sendSketchInfo("Motion Sensor", "1.0");
// Register all sensors to gw (they will be created as child devices)
present(CHILD_ID, S_MOTION);
}
void loop()
{
// Read digital motion value
bool tripped = digitalRead(DIGITAL_INPUT_SENSOR) == HIGH;
Serial.println(tripped);
send(msg.set(tripped?"1":"0")); // Send tripped value to gw
// Sleep until interrupt comes in on motion sensor. Send update every two minute.
sleep(digitalPinToInterrupt(DIGITAL_INPUT_SENSOR), CHANGE, SLEEP_TIME);
}
but it just seems to hang. It never even gets to the setup loop, where I had enterd a println to say, "Starting..."
On the node, the serial output is:
dd⸮d⸮⸮⸮⸮ccÄ⸮f⸮d⸮cÄc⸮⸮c⸮___ ___ _ __ ___
| |\/| | | | \___ \ /⸮
__ __ ____
| \/ |_ _/ ___| ___ _ __ ___ ___ _ __ ___
| |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __|
| | | | |_| |___| | __/ | | \__ \ _ | | \__ \
|_| |_|\__, |____/ \___|_| |_|___/\___/|_| |___/
|___/ 2.3.0-alpha
and on the gateway, the serial output is:
Console
0;255;3;0;9;0 MCO:BGN:INIT GW,CP=RLNGA---,VER=2.2.0-rc.2
0;255;3;0;9;14 TSM:INIT
0;255;3;0;9;20 TSF:WUR:MS=0
0;255;3;0;9;38 TSM:INIT:TSP OK
0;255;3;0;9;47 TSM:INIT:GW MODE
0;255;3;0;9;55 TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;67 MCO:REG:NOT NEEDED
0;255;3;0;14;Gateway startup complete.
0;255;0;0;18;2.2.0-rc.2
0;255;3;0;9;79 MCO:BGN:STP
0;255;3;0;9;100 MCO:BGN:INIT OK,TSP=1
On the same hardware, RadioHead works fine.
The gateway I've used has been:
https://www.openhardware.io/view/491/PA-LNA-nRF52832-ESP-LINK-Shield-for-Wemos-D1-Mini-ESP8266
I haven't noticed any problems.
@toyman Would this work? Buy two. Sacrifice the first so that you can image the firmware on the chip and extract the password. Use that password to unlock the OTA firmware update for the second one.
Or, maybe it's the universal bluetooth password: 1234. Maybe try that first. 