I don't know if any of you guys are still around and using this stuff -
I moved and am reviving a few of these 51/52 boards that I had built. Prior to moving I had decent luck with all these fixes though I don't quite remember where I was with any of this stuff seeing as it was 3 years ago.
I had a few motion sensors and some temp/humd based on these fixes and they were working great, no dips.
Not sure any of you will ever see this but hey it all worked.
@NeverDie said in 
AM612 Passive Infrared Sensor Breakout Board:
@waspie said in
for what its worth IIRC i'm getting at least 6 months on the ol' 612 with a CR2450.
Close to two years on a CR123a. So yeah, if I made more I'd design a new board for the new PIR sensors you're finding out there but the 612 even with its higher dropout voltage seems to work fine with even a moderatly sized battery.Unless the actual current drain is larger than the 14ua I'm assuming, it sounds as though the other drains on your battery are what's dominating. So, if my calculations are right, you likely wouldn't get more than a small percentage more battery life out of using the 3ua sensor instead of the AM612.
I'm using mostly 328p with edbyte radios with a resting current (no PIR) of like lets say 5-7ua? I haven't tested it in forever. with 2 years of battery on a 123 it just didnt seem worth the trouble worrying about any of it. and thanks for your designs that got me off the ground with that stuff btw.
after the fix for the 51822 and 832 i put together a few of those and those are using the cr2450. i think those rest at like 4.5ua (minus the pir of course). 6+ months on a button cell is quite all right with me.
for what its worth IIRC i'm getting at least 6 months on the ol' 612 with a CR2450.
Close to two years on a CR123a. So yeah, if I made more I'd design a new board for the new PIR sensors you're finding out there but the 612 even with its higher dropout voltage seems to work fine with even a moderatly sized battery.
So, like i've mentioned before, my coding is ugly but generally works. So if anyone wants to pretty this up - have at it.
Finally circling back to the nrf5 that I haven't touched in like a year I spent some time trying to get a working sketch. I played with neverdie's LPCOMP one and it kept locking up or something and I tried again with a GPIOTE one and it (besides being too complicated for me in general) was doing something similar. Using the latest alpha branch with the fixes for the nrf5 that were added about a year ago it finally works with just the plain jane interrupt sketch with a small addition to put i2c asleep. Found that tidbit on the nordic forums and sprinkled around elsewhere as well.
Power usage is around 24 microamps. I use it with a CR2450 so I figure probably at least 6 months. I'm using a circular board similar to @NeverDie 's nrf51 board so its a very compact PIR.
As a side note, I tried making the LED blink but it would always lock up after sending a 0 (no pir low). no idea why so I stopped messing with it for now just happy that it's working
Hopefully this is of use to someone:
/*
* This example sketch shows how you can manage the nRF5 pin mapping as part of your code.
* You can use the method for any nRF51822 or nRF52832 board or module.
*
* Most components, like UART, SPI, Wire Bus, of the nRF5 series chips don't
* have a fixed pin mapping. There are some pins with restrictions like analog
* inputs, NFC or pins near the radio module. Please refer the latest
* documentation about pin restrictions at http://infocenter.nordicsemi.com
*
* To use the custom pin mapping you have to do following steps:
*
* 1. Install "arduino-nrf5" like described at
* https://github.com/sandeepmistry/arduino-nRF5/
* 2. Install the "My Sensors nRF5 Boards" with the board manager like
* explained at https://github.com/mysensors/ArduinoBoards
* 3. Copy the files "MyBoardNRF5.cpp" and "MyBoardNRF5.h" from
* "MyBoardNRF5" example into your sketch.
* 4. Modify pin mappings in "MyBoardNRF5.cpp" and "MyBoardNRF5.h" to fit
* your requirements.
* 5. Select "MyBoardNRF5 nrf52832" or "MyBoardNRF5 nrf52822" as your board.
* Choose the correct parameters and programmer in the Tools menu.
*/
// MySensors /////////////////////
#define MY_RADIO_NRF5_ESB
#define MY_NODE_ID 121
//#define MY_NRF5_ESB_MODE (NRF5_1MBPS)
#define MY_NRF5_ESB_MODE (NRF5_250KBPS)
#define MY_PASSIVE_NODE
#include <MySensors.h>
#define SKETCH_NAME "NRF52 Motion 2021"
#define SKETCH_VERSION "v1"
#define CHILD_ID 1
#define CHILD_ID_VOLT 28
float batteryVoltage=0;
uint32_t SLEEP_TIME = 840000; //14 minutes
int batteryReport = 0;
int percent = 0;
MyMessage msg(CHILD_ID, V_TRIPPED); // Motion
MyMessage msgVoltage(CHILD_ID_VOLT,V_VOLTAGE);
#define DIGITAL_INPUT_SENSOR 2
void setup() {
pinMode(DIGITAL_INPUT_SENSOR, INPUT);
pinMode(LED_BUILTIN, OUTPUT);
i2c_off(); // Shut down the i2c
}
void presentation()
{
sendSketchInfo(SKETCH_NAME, SKETCH_VERSION);
present(CHILD_ID, S_MOTION);
present(CHILD_ID_VOLT,S_MULTIMETER);
}
void loop()
{
bool tripped = digitalRead(DIGITAL_INPUT_SENSOR) == HIGH;
send(msg.set(tripped?"1":"0")); // Send motion tripped value to gw
i2c_off();
sleep(digitalPinToInterrupt(DIGITAL_INPUT_SENSOR), CHANGE, SLEEP_TIME);
if ( batteryReport == 0 ) {
batteryVoltage=((float)hwCPUVoltage())/1000.0; //take voltage measurement after transmission to hopefully measure lowest voltage that occurs.
percent = map(batteryVoltage, 2.8, 3.25, 0, 100);
//send(msgVoltage.set(batteryVoltage,3)); //send battery voltage with 3 decimal places
send(msgVoltage.set(percent,2));
}
batteryReport++;
if ( batteryReport > 20 ) {
batteryReport=0;
}
}
void i2c_off() // Shut i2c down, powerconsumption rises up to 450uA instead of 11 ua - https://github.com/sandeepmistry/arduino-nRF5/issues/291#issuecomment-407492282
{
NRF_TWI1->ENABLE=TWI_ENABLE_ENABLE_Disabled << TWI_ENABLE_ENABLE_Pos;
*(volatile uint32_t *)0x40004FFC = 0;
*(volatile uint32_t *)0x40004FFC;
*(volatile uint32_t *)0x40004FFC = 1;
}
Are you currently working with any NRF5x? Do you have a working motion/contact sketch for the NRF52?
@mfalkvidd said in AM612 PIR can:
BL412 (the adafruit link) is rated for 2.7V minimum.
However, the BS412 is rated for 2.0V minimum. Maybe that's a good candidate?
nice find!
and 11ua, a little lower than the 612. Might have to try one of these some day
@chey I really never did much looking around. As I said, it wasn't really much of an issue. The first PIRs I built are having their batteries die just now. I started down this road with the PIRs about 2 years ago - so that's about how long they've been lasting as-is. 
Did anyone ever find a PIR sensor that could handle voltages below 2.8v without going wonky?
I use CR123a batteries with my PIR and I recently had to replace one. It was at the moment I realized I had at least of year of life out of this one and it had only then dropped to 60%.
If there was another sensor readily and cheaply available it could be of some interest although I'm pretty content with a year of life.
i'm still around but most of my stuff is working and has been for a long time so I haven't much need to check in. I wish i could get my nrf51/52 based things to work better but i've kind of given up on those.
@skywatch
hah, tell me about it. it went through battery and all. Still dutifully reporting every 3 minutes.
A temperature sensor in my boys' room went missing this morning when my wife gathered up the bed sheets to launder. I hadn't printed a case for it and mounted it anywhere and had it on the bed out of the way. It should have been hard to get tangled up in the sheets.
I noticed it was missing from its perch and was looking around for it but not too hard as I was working.
And hour or so later I walked passed one of the panels in the house that displays information and noticed the temperature for that room had increased to over 100 Fahrenheit which immediately confirmed my suspicion about where it went.
It went through the wash cycle and on to dry (combination machine) and survived the whole thing 
@haasje30 if it's mqtt both can subscribe at the same time
@haasje30
smartsleep is easy with MQTT
Initially a few years ago i tried the binding and it gave me nothing but trouble.
While it was configured I'd watch MQTT to see what it would do.
2020-12-31 22:58:22 unoout/202/255/3/0/33 180000 (THIS IS THE SLEEP DURATION)
2020-12-31 22:58:22 unoout/202/255/3/0/32 500 (AT THIS MOMENT YOU HAVE 500MS to GET A COMMAND SENT)
So define a thing to the channel ending in 32.
Bind an item to that channel with an expire timer for like 10 seconds state = 0
then for your rule you'd have
rule "whatever"
when
Item whateverSleepItem changed from 0 to 500
then
whateverOtherItemThatIsSendingOutACommand.sendCommand(ON/OFF/WHATEVER)
end
@Didou @evb
I download the dev version AND replaced the two files with the ones from the proposed fix.
I think that's the right path - it seems to be showing positive results.
@ncollins
Seems to be working well on NRF51, not so much on NRF52. I backed off the changes for NRF52 modules and they're working ok with latest alpha. I think I need a better sketch for them...
Anyway, NRF51822 is doing much much better.
@Didou follow the links posted by @ncollins
The first big dip on 11/29 was a deadlock. I tried some change after that that still didn't work and lead to another deadlock on 12/7. Using the fix from github you can see how much more stable battery reporting has been since 12/9 (small spike when it was plugged in for programming) when i flashed it using the fixed code. This one might finally be fixed.
@Omemanti
If you're experiencing this issue I'd certainly try 1. I don't know that I'd got hog wild just yet unless they're easy to get to and easy to hook up.
@ncollins
yep!
while its only a few days I'm not seeing those dips that you can notice prior to the big drop. might be nothing, might be something. who know!
I also had a lot of problems before finally switching to (cd)ebyte modules. After moving to ebyte modules for the gateway and nodes my problems have all but vanished. good luck.
@ncollins 1455 is the latest and greatest
https://github.com/mysensors/MySensors/pull/1455
d00616 replied to use it.
6 days on no dip (yet)
edit i guess its 3 days since the spike (plugged in) was on 12/10
that's the reversion isn't it? so wouldn't that be the same as no changes at all? or is this supposed to be the pre-reversion test fix? i think i'll try that code in 1455. nothing to lose but another cr2032 heh
good idea on asking, will do
I think that's an accurate description. Range won't be a factor this time in particular as its probably 10 feet (3 meters) away from the parent. I'll grab it and reflash it in a few days with the updated code.
I see our graphs show identical behavior, interesting.
edit
If I want to try out the new code is this the one i'm after:
https://github.com/mysensors/MySensors/pull/1455
? Its a little unclear to me
it happened...i'm losing it already.
@ncollins thanks bud!
with the htu21 the sleeping consumption is sub 5ua. its been 4 days and hovering around 3 volts. i'm keeping my fingers crossed. Would love to reliably use these. Since I had so much trouble with them I designed and put into use atmega328p boards quite a while ago now so I'm happy with those but I still had a crap ton of these nrf51 and nrf52 boards made thinking i would get a lot of use out of them.
Things are improving. With some of the more recent developments and the reboot strategy I at least have reliable motion sensors working now. They've been up for about 2 months now, huge improvement!
@ncollins sure:
be aware, i'm not a coder. i just hack crap together to the point that it works then move on.
// SUMMARY: This demo sketch runs on MultiSensor Version 7 board with an I2C Si7021 module to transmit temperature, humidity, and battery voltage to a MySensors gateway using MySensors protocols.
// Note: because this is a passive node, node ID must be set manually to a unique sensor node ID:
#define MY_NODE_ID 150 // Passive mode requires static node ID
/**
* 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-2017 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 - tekka
*
* DESCRIPTION
* Passive node example: This is a passive & independent reporting node
*
*/
// This demo sketch uses the LowPowerLab SI7021 library and also some of its sample code: https://github.com/LowPowerLab/SI7021
// This demo sketch also draws from the MySensor's example MockMySensors sketch.
// This demo sketch also draws from some of the code posted by smilvert here: https://forum.mysensors.org/topic/7961/why-do-passive-nodes-need-to-set-their-node-id-manually/14
#define SHORT_WAIT 50
#include <Wire.h>
#include <SparkFunHTU21D.h>
HTU21D myHumidity;
// Enable debug prints
//#define MY_DEBUG
// Enable passive mode
#define MY_PASSIVE_NODE
#define MY_PARENT_NODE_IS_STATIC
#define MY_PARENT_NODE_ID 0
#define MY_TRANSPORT_MAX_TSM_FAILURES 2
#define MY_SLEEP_TRANSPORT_RECONNECT_TIMEOUT_MS 3000
#define MY_TRANSPORT_WAIT_READY_MS 10000
#define MY_SLEEP_TRANSPORT_RECONNECT_TIMEOUT_MS 5000
// 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>
#define CHILD_ID_TEMP 0 //definitions contributed by smilvert (see above credit)
#define CHILD_ID_HUM 1
// Initialize general message
MyMessage msgTemp(CHILD_ID_TEMP, V_TEMP);
MyMessage msgHum(CHILD_ID_HUM, V_HUM);
#define ID_S_MULTIMETER 28
MyMessage msg_S_MULTIMETER_V_VOLTAGE(ID_S_MULTIMETER,V_VOLTAGE);
//float lastTemperature=0;
float lastSentTemp=0;
int lastSentHumd=0;
//float lastHumidity=0;
float lastVoltage=0;
float batteryVoltage=0;
float temperature=0;
int humidity=0;
unsigned long time;
void setup()
{
myHumidity.begin();
NRF_CLOCK->INTENSET=B11; //enable interrupts for EVENTS_HFCLKSTARTED and EVENTS_LFCLKSTARTED
NRF_CLOCK->TASKS_HFCLKSTART=1; //start the high frequency crystal oscillator clock
while (!(NRF_CLOCK->EVENTS_HFCLKSTARTED)) {} //wait until high frequency crystal oscillator clock is up to speed and working
wait(SHORT_WAIT);
}
void presentation()
{
// Send the sketch version information to the gateway and controller
sendSketchInfo("NRF51822 Temp & Humidity", "1.0");
// Register all sensors to gw (they will be created as child devices)
present(CHILD_ID_TEMP, S_TEMP);
wait(SHORT_WAIT);
present(CHILD_ID_HUM, S_HUM);
wait(SHORT_WAIT);
present(ID_S_MULTIMETER,S_MULTIMETER,"Electric Station");
wait(SHORT_WAIT);
}
void loop() {
myHumidity.begin(); //power consumption add
// get humidity and temperature in one shot, saves power because sensor takes temperature when doing humidity anyway
float temperature = myHumidity.readTemperature();
temperature = (temperature*1.8)+32;
wait(SHORT_WAIT);
float humidity = myHumidity.readHumidity();
//temperature = float(temperature*1.8)+32;
batteryVoltage=((float)hwCPUVoltage())/1000.0; //take voltage measurement after transmission to hopefully measure lowest voltage that occurs.
if ( (temperature > lastSentTemp + .1) || (temperature < lastSentTemp - .1) ) {
send(msgTemp.set(temperature,2));
lastSentTemp = temperature;
}
if ( (humidity > lastSentHumd + 1) || (humidity < lastSentHumd - 1) ){
send(msgHum.set(humidity,0));
lastSentHumd = humidity;
}
//if ( batteryVoltage > (lastVoltage+.1) || batteryVoltage < (lastVoltage-.1) ) {
send(msg_S_MULTIMETER_V_VOLTAGE.set(batteryVoltage,2)); //send battery voltage with 2 decimal places
//lastVoltage = batteryVoltage;
//}
time = millis();
if (time > 64800000 ) {
reboot();
}
NRF_TWI0->ENABLE = 0; //possible power consumption adds
NRF_TWI1->ENABLE = 0;
sleep(180000); //sleep for three minutes
}
void reboot() {
wdt_disable();
wdt_enable(WDTO_15MS);
while (1) {}
}
@ncollins
Thanks, I backed off the changed when I read the one pull that got reversed. Hadn't seen there was an update.
Im not using any interrupts on my NRF51 modules - only si7021/htu21s
thanks for the update on the PRs. I'll give that a go after I see how long the battery lasts this go 'round.
So far holding steady at 3+ volts with 3 minute read times but again, it does go for a while before randomly killing itself.
@ncollins said in High power consumption NRF52832 & SI7021:
NRF_TWI0->ENABLE = 0;
NRF_TWI1->ENABLE = 0;
thanks, added those lines after reading and an appropriate .begin prior and it compiled and sent and works so far.
Won't know about consumption for a while - it doesn't act up while I'm watching it... it seems to get stuck at some point (1 week? 2 weeks? 10 days?) and then dies. And yes, it is set to reboot every 24 hours
So it's something else you or I have not pinpointed yet.
thanks, i've been fighting with this (i think) in a 51822. I was reviving getting these working and i keep chewing through batteries.
@Puneit-Thukral
Could you post your full working sketch please?
I'm revisiting some of my 51822 nodes that have sat collecting dust for a long time and thought i might try to get them working again.
i tried to get the binding working as i wanted to maybe 2 years ago and after a bunch of issues i moved it all to MQTT instead. You obviously lose auto adding of new nodes but thats about it. MQTT just works better, i wouldn't call it a work around.
I had initial problems with the 2.4 binding and went MQTT only.
I can't help you at the moment with your problem but if it were me, I'd make it work with MQTT only rather than introduce another binding unless there was no other way. I think I do a couple things with null values and it works fine but I haven't touched it in months (since it just works) so i'm of no actual help right now 
@olka
Can't say I remember what I did anymore. Probably suppressed sending in the case of 85 degrees.
@NeverDie
where did you find them for $1.08??
I didn't tune speed at all so they should be running at 2mbps and I've had no issue.
This one in particular for my SMD needs
http://www.ebyte.com/en/product-view-news.aspx?id=111
I haven't used any of the larger, non-SMD versions but i would expect to have similar success.
I had 2 or 3 different SMD versions from no-name vendors (not blobs, at least) that had various issues communicating. These issues included not communicating at all to garbled characters and loads of NACKS.
The pinout is slightly different so I had to make a small change to my board design but other than that everything else was the same. The ebyte modules have (for me) worked first time, every time.
I had seemingly unending problems getting sensors to be reliable and about gave up until i switched to ebyte modules.
Since redesigning boards to use their slightly different pinout and moving to their modules I haven't had any issues. A complete turnaround from what i was experiencing before - highly recommended.
try another radio? My gateway is a Pi Zero W and works fine so there's no reason it shouldn't work for you.
@ncollins good news
I wonder if this has anything to do with it?
https://forum.mysensors.org/topic/10705/nrf52-watchdog-problem-myboardnrf5
@neverdie thanks, i'll look into it and keep my eye on it.
I've been sticking with atmega328p as I've tried nrf51 and 52 but i'm just not smart enough code-wise to get them to work reliably enough. the atmega on the other hand is very reliable and gives me almost no trouble.
i've had many PCBs done by JLPCB and they've all been top notch as far as I can tell.
I'm getting ready to make an integrated nrf24/atmega328 qfn board with them putting the components down soon so I can't answer how the part placement is but if it's like their PCBs it should be good.
throw this somewhere in your code:
void reboot() {
wdt_disable();
wdt_enable(WDTO_15MS);
while (1) {}
}
and then calling the reboot (in the entire loop):
void loop() {
if (motion_change) {
motionDetected=!motionDetected;
if (motionDetected) {
send(msg.set("1")); // motion detected
}
else {
digitalWrite(LED_BUILTIN,LOW); //turn-off LED to signify motion no longer detected
send(msg.set("0")); // send all-clear to prepare for future detections
}
NRF_LPCOMP->EVENTS_CROSS=0;
motion_change=false;
}
else { //must be a scheduled wake-up. Time to report voltage as a heartbeat.
batteryVoltage=((float)hwCPUVoltage())/1000.0; //take voltage measurement after transmission to hopefully measure lowest voltage that occurs.
send(msg_S_MULTIMETER_V_VOLTAGE.set(batteryVoltage,3)); //send battery voltage with 3 decimal places
time = millis();
if (time > 14400000 ) {
reboot();
}
}
mySleep(1200000); //sleep for 20 minutes
}```@ncollins I had the same problem and sort of "solved" it by having it reboot every 3 hours (or maybe it was 6).
I don't know how to use the nrf5x stuff anywhere near well enough to actually fix it but it seems to work.
@scalz
Thanks for the link to the 3.3v USBASP mod!
i have been pulling my hair out trying to get bare 328p chips programmed using a generic ASP
thank you!!!
5 months and voltage still holding decently high
/77/28/1/0/38 2.964
@nca78 If you're talking about the basic motion sketch - I've tried it and it doesn't work
The node checks in when initially powered but i can't seem to trigger it...
It's post 1515 in nrf action
https://forum.mysensors.org/topic/6961/nrf5-action/1515
In particular I download the zip file from post 1543
https://forum.mysensors.org/topic/6961/nrf5-action/1543#
Re: nRF5 action!
I'm trying to modify @Nca78 GPIOTE example for the NRF51 for use on the nrf52 motion sensor I made with an optional reed/switch input for monitoring the door and motion in a bedroom.
I've gotten it to work on the NRF52 well enough and I can get an update when I close or open the reed OR motion sensor but I don't know how to separate them so I know WHICH one of the two triggered. I've tried for the past week but the nrf functions inside of arduino confuse me and I can't say i understand the NRF stuff all that well anyway.
@Nca78 could you please help? Based on the script you've already written I'm guessing it would take very little modification but I don't know what I'm doing ![😕](https://forum.mysensors.org/plugins/nodebb-plugin-emoji/emoji/apple/1f615.png?v=qn99trbepkk ":\")
@berkseo said in nrf52832 PIR:
I would like to find an available pir sensor powered by 1.8 V
yeah, that'd be nice
thanks guys, i just ordered a few
@berkseo i was searching for buck/boost converters and found TPS61098 which when i searched for turned up on one of you designs
what i can't figure out just yet is how to wire it up for our application. can you shed any light on that, please?
well, i think i may have sorted it.... GND and MODE to ground. VSUB is 3.3 (or 3v if i do the 61098) out (not being used in this application?).
SW inductor, vin of course, and vmain is the output for the mcu i think
Yeah, it's an AM612. I think when I originally put this together I didn't realize the low cutoff voltage 
We'll see how long it lasts...
I guess options then are to add a buck converter or strap AAAs on the back instead
Black fresnel lens? what?? I might have to find some of those
Some pictures of an assembled unit with 3d printed case
I'll be updating this with pictures of actual boards soon, including my PIR "hat"
I've been running several of them for about two months now on a single CR2450 (~620mah) and they're still showing just slightly over 3 volts. These are detecting motion many times per hour during the day.
this is great info, this could potentially help a lot of people on this forum
I have quite an annoying problem keeping me from successfully deploying a bunch of NRF52 PIRs.
For a little while it works and then the messages stop. I have serial logs from the NRF52 seemingly sending the messages but nothing on the gateway side. The two devices are about 6 feet apart. I've tried it at home with a completely different pi and a completely different radio (pa and non-pa version) and the results are the same. On my desk at work its a regular pi b with a non-pa radio. Again, six feet apart. I've tried the default channel. I've tried channel 10 and 125 as well. I've tried max power and low power. I send the message twice thinking maybe one gets lost and the second makes it through.
Here's the sketch:
// SUMMARY: This demo sketch runs on the AM612 PIR v607 PCBto transmit battery voltage (heartbeat) and motion detections to a MySensors gateway using MySensors protocols.
// Note: because this is a passive node, node ID must be set manually to a unique sensor node ID:
#define MY_NODE_ID 70 // Passive mode requires static node ID
//#define MY_CORE_ONLY
//#define MY_PASSIVE_NODE
#define MY_RADIO_NRF5_ESB
/**
* 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-2017 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 - tekka
*
* DESCRIPTION
* Passive node example: This is a passive & independent reporting node
*
*/
// This demo sketch also draws from the MySensor's example MotionSensor sketch.
//#define IS_NRF51 //true iff the target is an nRF51. If an nRF52, then comment this line out!
#define PIR_DETECTION_PIN 2
#define SHORT_WAIT 100
//#define MY_RF24_CHANNEL 125
#define MY_NRF5_ESB_CHANNEL 125
//#define MY_NRF5_ESB_PA_LEVEL NRF5_PA_MAX
//#define MY_TRANSPORT_WAIT_READY_MS 3000
//#define MY_TRANSPORT_MAX_TSM_FAILURES 2
//#define MY_SLEEP_TRANSPORT_RECONNECT_TIMEOUT_MS 3000
//#define MY_TRANSPORT_UPLINK_CHECK_DISABLED
//#define MY_PARENT_NODE_IS_STATIC
//#define MY_PARENT_NODE_ID 0
#define MY_DEBUG_VERBOSE_NRF5_ESB
//#define MY_NRF5_ESB_REVERSE_ACK_RX
//#define MY_NRF5_ESB_REVERSE_ACK_TX
#define MY_DEBUG
#define MY_DEBUG_VERBOSE_TRANSPORT
#include <MySensors.h>
// Enable debug prints
volatile bool motion_change=false;
void blinkityBlink(uint8_t pulses, uint8_t repetitions) {
for (int x=0;x<repetitions;x++) {
for (int i=0;i<pulses;i++) {
digitalWrite(LED_BUILTIN,HIGH);
wait(20);
digitalWrite(LED_BUILTIN,LOW);
wait(100);
}
wait(500);
}
}
void disableNfc() { //only applied to nRF52
#ifndef IS_NRF51
//Make pins 9 and 10 usable as GPIO pins.
NRF_NFCT->TASKS_DISABLE=1; //disable NFC
NRF_NVMC->CONFIG=1; // Write enable the UICR
NRF_UICR->NFCPINS=0; //Make pins 9 and 10 usable as GPIO pins.
NRF_NVMC->CONFIG=0; // Put the UICR back into read-only mode.
#endif
}
void turnOffRadio() {
NRF_RADIO->TASKS_DISABLE=1;
while (!(NRF_RADIO->EVENTS_DISABLED)) {} //until radio is confirmed disabled
}
void turnOffUarte0() {
#ifndef IS_NRF51
NRF_UARTE0->TASKS_STOPRX = 1;
NRF_UARTE0->TASKS_STOPTX = 1;
// NRF_UARTE0->TASKS_SUSPEND = 1;
NRF_UARTE0->ENABLE=0; //disable UART0
while (NRF_UARTE0->ENABLE!=0) {}; //wait until UART0 is confirmed disabled.
#endif
#ifdef IS_NRF51
NRF_UART0->TASKS_STOPRX = 1;
NRF_UART0->TASKS_STOPTX = 1;
NRF_UART0->TASKS_SUSPEND = 1;
NRF_UART0->ENABLE=0; //disable UART0
while (NRF_UART0->ENABLE!=0) {}; //wait until UART0 is confirmed disabled.
#endif
}
void turnOffAdc() {
#ifndef IS_NRF51
if (NRF_SAADC->ENABLE) { //if enabled, then disable the SAADC
NRF_SAADC->TASKS_STOP=1;
while (NRF_SAADC->EVENTS_STOPPED) {} //wait until stopping of SAADC is confirmed
NRF_SAADC->ENABLE=0; //disable the SAADC
while (NRF_SAADC->ENABLE) {} //wait until the disable is confirmed
}
#endif
}
void turnOffHighFrequencyClock() {
NRF_CLOCK->TASKS_HFCLKSTOP = 1;
while ((NRF_CLOCK->HFCLKSTAT) & 0x0100) {} //wait as long as HF clock is still running.
}
void mySleepPrepare() { //turn-off energy drains prior to sleep
turnOffHighFrequencyClock();
turnOffRadio();
//turnOffUarte0();
}
void activateLpComp() {
NRF_LPCOMP->PSEL=0; // monitor AIN0 (i.e. pin P0.02 on nRF52832 PIR Motion Sensor v607).
while (!(NRF_LPCOMP->PSEL==0)) {} //wait until confirmed
NRF_LPCOMP->REFSEL=3; // choose 1/2 VDD as the reference voltage
while (!(NRF_LPCOMP->REFSEL==3)) {} //wait until confirmed
NRF_LPCOMP->ANADETECT=0; //detect CROSS events on PIR detection pin
while (NRF_LPCOMP->ANADETECT!=0) {} //wait until confirmed
NRF_LPCOMP->INTENSET=B1000; //Enable interrupt for CROSS event
while (!(((NRF_LPCOMP->INTENSET)&B1000)==B1000)) {} //wait until confirmed
NRF_LPCOMP->ENABLE=1; //Enable LPCOMP
while (!(NRF_LPCOMP->ENABLE==1)) {} //wait until confirmed
NRF_LPCOMP->TASKS_START=1; //start the LPCOMP
while (!(NRF_LPCOMP->EVENTS_READY)) {} //wait until ready
NVIC_SetPriority(LPCOMP_IRQn, 15);
NVIC_ClearPendingIRQ(LPCOMP_IRQn);
NVIC_EnableIRQ(LPCOMP_IRQn);
}
void suspendLpComp() { //suspend getting more interrupts from LPCOMP before the first interrupt can be handled
if ((NRF_LPCOMP->ENABLE) && (NRF_LPCOMP->EVENTS_READY)) { //if LPCOMP is enabled
NRF_LPCOMP->INTENCLR=B0100; //disable interrupt from LPCOMP
while (((NRF_LPCOMP->INTENCLR)&B0100)==B0100) {} //wait until confirmed
}
}
void resumeLpComp() { //suspend getting interrupts from LPCOMP
NRF_LPCOMP->INTENSET=B0100; //Enable interrupt for UP event
while (((NRF_LPCOMP->INTENSET)&B1000)!=B0100) {} //wait until confirmed
}
#define CHILD_ID 1 // Id of the motion sensor child
#define ID_S_MULTIMETER 28
// Initialize motion message
MyMessage msg(CHILD_ID, V_TRIPPED);
MyMessage msg_S_MULTIMETER_V_VOLTAGE(ID_S_MULTIMETER,V_VOLTAGE);
float batteryVoltage=0;
void blinkityBlink(uint8_t repetitions) {
for (int x=0;x<repetitions;x++) {
digitalWrite(LED_BUILTIN,HIGH);
wait(20);
digitalWrite(LED_BUILTIN,LOW);
wait(100);
digitalWrite(LED_BUILTIN,HIGH);
wait(20);
digitalWrite(LED_BUILTIN,LOW);
if (x<(repetitions-1)) { //skip waiting at the end of the final repetition
wait(500);
}
}
}
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);
wait(SHORT_WAIT);
present(ID_S_MULTIMETER,S_MULTIMETER,"Electric Station");
wait(SHORT_WAIT);
}
void setup()
{
hwInit();
hwPinMode(LED_BUILTIN,OUTPUT_D0H1);
hwPinMode(PIR_DETECTION_PIN,INPUT);
blinkityBlink(2,1); //Signify end of setup with two quick pulses.
disableNfc(); //remove unnecessary energy drains
turnOffAdc(); //remove unnecessary energy drains
activateLpComp();
motion_change=false;
}
void mySleep(uint32_t ms) {
mySleepPrepare(); //Take steps to reduce drains on battery current prior to sleeping
sleep(ms);
}
bool motionDetected=false;
void loop() {
mySleep(300000); //sleep for 5 minutes
if (motion_change) {
motionDetected=!motionDetected;
if (motionDetected) {
digitalWrite(LED_BUILTIN,HIGH); //turn-on LED to signify motion detected
send(msg.set("1")); // motion detected
wait(SHORT_WAIT);
send(msg.set("1"));
delay(500);
digitalWrite(LED_BUILTIN,LOW);
}
else {
digitalWrite(LED_BUILTIN,LOW); //turn-off LED to signify motion no longer detected
send(msg.set("0")); // send all-clear to prepare for future detections
wait(SHORT_WAIT);
send(msg.set("0"));
}
NRF_LPCOMP->EVENTS_CROSS=0;
motion_change=false;
}
else { //must be a scheduled wake-up. Time to report voltage as a heartbeat.
batteryVoltage=((float)hwCPUVoltage())/1000.0; //take voltage measurement after transmission to hopefully measure lowest voltage that occurs.
send(msg_S_MULTIMETER_V_VOLTAGE.set(batteryVoltage,3)); //send battery voltage with 3 decimal places
}
}
// * Reset events and read back on nRF52
//* http://infocenter.nordicsemi.com/pdf/nRF52_Series_Migration_v1.0.pdf
#if __CORTEX_M == 0x04
#define NRF5_RESET_EVENT(event) \
event = 0; \
(void)event
#else
#define NRF5_RESET_EVENT(event) event = 0
#endif
// This must be in one line
extern "C" { void LPCOMP_IRQHandler(void) {motion_change=true; NRF5_RESET_EVENT(NRF_LPCOMP->EVENTS_CROSS); NRF_LPCOMP->EVENTS_CROSS=0; MY_HW_RTC->CC[0]=(MY_HW_RTC->COUNTER+2);}}
The serial log from a wake up event:
849294 MCO:SLP:WUP=-1
849296 TSF:TRI:TPU
849298 NRF5:INIT:ESB
849300 NRF5:STL
849301 NRF5:SND:TO=255,LEN=8,PID=1,NOACK=1
849311 NRF5:SND:END=1,ACK=0,RTRY=4,RSSI=-61,WAKE=10
849316 ?TSF:MSG:SEND,70-70-255-0,s=1,c=1,t=16,pt=0,l=1,sg=0,ft=0,st=OK:0
849373 NRF5:SND:TO=255,LEN=8,PID=2,NOACK=1
849383 NRF5:SND:END=1,ACK=0,RTRY=4,RSSI=-61,WAKE=9
849388 ?TSF:MSG:SEND,70-70-255-0,s=1,c=1,t=16,pt=0,l=1,sg=0,ft=0,st=OK:0
849394 NRF5:RX:LEN=8,NOACK=0,PID=1,RSSI=-63,RX=0
849399 TSF:MSG:READ,0-0-70,s=1,c=1,t=16,pt=0,l=1,sg=0:0
849404 TSF:MSG:ACK
849406 MCO:SLP:MS=300000,SMS=0,I1=255,M1=255,I2=255,M2=255
849411 TSF:TDI:TPD
849413 NRF5:PD
From the gateway at NRF5 power-on:
May 07 14:07:49 DEBUG TSF:MSG:READ,70-70-0,s=255,c=3,t=6,pt=1,l=1,sg=0:255
May 07 14:07:49 DEBUG GWT:TPS:TOPIC=mysensors-out/70/255/3/0/6,MSG SENT
Sometimes it all makes it through, not this time.
Here's the startup log from the NRF5 at the same time:
__ __ ____
| \/ |_ _/ ___| ___ _ __ ___ ___ _ __ ___
| |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __|
| | | | |_| |___| | __/ | | \__ \ _ | | \__ \
|_| |_|\__, |____/ \___|_| |_|___/\___/|_| |___/
|___/ 2.3.1
23 MCO:BGN:INIT NODE,CP=RNNPN---,REL=255,VER=2.3.1
28 TSM:INIT
29 TSF:WUR:MS=0
30 NRF5:INIT:ESB
32 TSM:INIT:TSP OK
34 TSM:INIT:TSP PSM
35 TSM:INIT:STATID=70
37 NRF5:STL
39 TSF:SID:OK,ID=70
40 TSM:FPAR
41 TSM:FPAR:STATP=255
43 TSM:ID
44 TSM:ID:OK
46 TSM:UPL:DISABLED
47 TSM:READY:ID=70,PAR=255,DIS=1
50 NRF5:SND:TO=255,LEN=9,PID=0,NOACK=0
60 NRF5:SND:END=1,ACK=0,RTRY=4,RSSI=-61,WAKE=11
65 ?TSF:MSG:SEND,70-70-255-0,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
72 NRF5:RX:LEN=9,NOACK=0,PID=1,RSSI=-71,RX=0
76 TSF:MSG:READ,0-0-70,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
81 NRF5:SND:TO=255,LEN=12,PID=1,NOACK=1
92 NRF5:SND:END=1,ACK=0,RTRY=4,RSSI=-61,WAKE=10
96 ?TSF:MSG:SEND,70-70-255-0,s=255,c=0,t=17,pt=0,l=5,sg=0,ft=0,st=OK:2.3.1
103 NRF5:SND:TO=255,LEN=8,PID=2,NOACK=1
113 NRF5:SND:END=1,ACK=0,RTRY=4,RSSI=-61,WAKE=9
118 ?TSF:MSG:SEND,70-70-255-0,s=255,c=3,t=6,pt=1,l=1,sg=0,ft=0,st=OK:255
2124 NRF5:SND:TO=255,LEN=20,PID=3,NOACK=1
2135 NRF5:SND:END=1,ACK=0,RTRY=4,RSSI=-61,WAKE=9
2139 ?TSF:MSG:SEND,70-70-255-0,s=255,c=3,t=11,pt=0,l=13,sg=0,ft=0,st=OK:Motion Sensor
2147 NRF5:SND:TO=255,LEN=10,PID=0,NOACK=1
2158 NRF5:SND:END=1,ACK=0,RTRY=4,RSSI=-61,WAKE=9
2162 ?TSF:MSG:SEND,70-70-255-0,s=255,c=3,t=12,pt=0,l=3,sg=0,ft=0,st=OK:1.0
2169 NRF5:SND:TO=255,LEN=7,PID=1,NOACK=1
2179 NRF5:SND:END=1,ACK=0,RTRY=4,RSSI=-61,WAKE=9
2184 ?TSF:MSG:SEND,70-70-255-0,s=1,c=0,t=1,pt=0,l=0,sg=0,ft=0,st=OK:
2240 NRF5:SND:TO=255,LEN=23,PID=2,NOACK=1
2251 NRF5:SND:END=1,ACK=0,RTRY=4,RSSI=-61,WAKE=9
2256 ?TSF:MSG:SEND,70-70-255-0,s=28,c=0,t=30,pt=0,l=16,sg=0,ft=0,st=OK:Electric Station
2314 MCO:REG:NOT NEEDED
2316 MCO:BGN:STP
3057 MCO:BGN:INIT OK,TSP=1
3059 MCO:SLP:MS=300000,SMS=0,I1=255,M1=255,I2=255,M2=255
3064 TSF:TDI:TPD
3066 NRF5:PD
PORT CLOSED
any hints would be more than welcome, please
is there an option to run a pi as a repeater? I didn't see anything in configure help
its the start of a nrf52832-based motion sensor similar to neverdie's Multi-Sensor: Temp/Humidity/PIR/ Leak/Magnet/Light/Accel seen here:
https://www.openhardware.io/view/510/Multi-Sensor-TempHumidityPIR-LeakMagnetLightAccel
The nrf51822 is a bit finicky. I made it slightly bigger to accommodate a cr2450 and use a nrf52832 which is allegedly more reliable for low power sensors. I have a PIR hat, too, that i need to upload. I made my version adjustable. Neverdie's version works, but, the pir triggers quite a lot at the minimum reset time which means its triggering often in a busy room which uses a lot more battery.
my pi3b does this as well. it's far and few in between. I even made a watchdog in openhab to "ping" the msgw (requesting an ack) and mysgw responds but it doesn't send out new sensor readings. i thought about expanding the watchdog to watch for all sensor readings and throw up a restart to the gw if it receives no readings in a 10 minute period but mine doesn't fail nearly as consistently as yours so I haven't worried about it too much...
would still like to see a resolution to this as I've moved most of my PIRs and temp sensors to mysgw so when it goes down it can be a bit of a problem.
oh yeah, forgot to mention unplugging it after programming. that has bit me in the butt at least 20 times. finally i remember to unplug it now /facepalm.
i've only played with the nrf51 but i know well enough getting either of these to fully sleep can be a bit of a process software-wise. i doubt you need any hardware, it's going to be software related
For anyone looking to use @NeverDie 's nrf51 circular board (v9) with this breakout - I'm using the sketch as linked from @Nca78 in this post: https://forum.mysensors.org/topic/6961/nrf5-action/1542
in conjunction with the edit to the file as described in this post:
https://forum.mysensors.org/topic/6961/nrf5-action/1514 (the edit to WInterrupt.c and I'm using version 0.6.0 from sandeep)
with just a few minor edits to the sketch from Nca (setting the pin to 10 (sda marked on the circular board).
14ua idle current btw, working like a charm. so far i'm just using a 2032. Trying to figure out a way to strap a cr2450 or 2477 on the back
get rid of all your apostrophes. Those words are pluralized, not possessive (as long as you're trying to clean it up and make it look nice you might as well fix the punctuation).
@magpern
sorry, without direct access to tinker with it I can't say where it is stuck. At this moment I've dumped the binding altogether and just do everything via MQTT. I have a good feeling the binding was somehow crashing the mqtt broker which is why I stopped using the binding.
yeah, mysensors in 2.4+ is very touchy.
Have you restarted the openhab service lately?
Try deleting your mysensors gateway then restart openhab and re-add the mysensors mqtt gateway. Just for grins...
i dont know what folder path your stuff would be in exactly but can you list openhab???/userdata/config/org/openhab/
ex:
/volume1/public/openHAB/userdata/config/org/openhab$ ls -la
total 852
drwxrwxrwx+ 1 openhab users 504 Feb 13 13:55 .
drwxrwxrwx+ 1 openhab users 74 Feb 13 12:39 ..
-rwxrwxrwx+ 1 openhab users 402 Feb 13 13:55 addons.config
-rwxrwxrwx+ 1 openhab users 118 Feb 13 12:39 basicui.config
-rwxrwxrwx+ 1 openhab users 120 Feb 13 12:39 dashboard.config
-rwxrwxrwx+ 1 openhab users 796758 Feb 13 08:28 habpanel.config
-rwxrwxrwx+ 1 openhab users 230 Feb 13 12:39 http.config
-rwxrwxrwx+ 1 openhab users 184 Feb 13 12:39 influxdb.config
-rwxrwxrwx+ 1 openhab users 162 Feb 13 12:39 jdbc.config
-rwxrwxrwx+ 1 openhab users 131 Feb 13 12:39 logging.config
-rwxrwxrwx+ 1 openhab users 115 Feb 13 12:39 mail.config
-rwxrwxrwx+ 1 openhab users 116 Feb 13 12:39 mapdb.config
-rwxrwxrwx+ 1 openhab users 118 Feb 13 12:39 network.config
-rwxrwxrwx+ 1 openhab users 114 Feb 13 12:39 nma.config
-rwxrwxrwx+ 1 openhab users 158 Feb 13 12:39 plex.config
-rwxrwxrwx+ 1 openhab users 200 Feb 13 12:39 pushover.config
-rwxrwxrwx+ 1 openhab users 116 Feb 13 12:39 rrd4j.config
-rwxrwxrwx+ 1 openhab users 118 Feb 13 12:39 runtime.config
-rwxrwxrwx+ 1 openhab users 119 Feb 13 12:39 services.config
-rwxrwxrwx+ 1 openhab users 119 Feb 13 12:39 voicerss.config
-rwxrwxrwx+ 1 openhab users 308 Feb 13 12:39 weather.config
in your mysensors gateway config the name of the broker is fd3193ea
I dont see a broker in your things view. Please re-snip and post
not only that, zigbee has different standards/profiles and not all controllers support all devices.
zwave is interoperable with ALL zwave devices of ALL versions. IMO, zwave is a better way to go.
don't install that.
just configure a regular broker in a .thing file
or add it via paperui
inbox-> + sign -> mqtt thing - > add manually - > mqtt broker -> give it the IP and hit the check.
then you'll have a broker to attack mysensors to
try giving it a different node id
It's looking more and more like the code is fine and its the sensors i'm using that are the problem.
I got some BM612 (cheaper) from ali supposedly the same as am612 but they don't seem to work right. It's like they trigger once and then never again. Can't find a data sheet for them...
I hooked up a 312 just for kicks and it seems to be working. I doubt I'll deploy any 312s due to what seems to be a VERY narrow range and plus it doesn't match the profile of the round board etc...
Anyway, wanted to say that i think this is all working as its supposed to I just got a bad batch of sensors or they're slightly different in some way
They don't seem to play well and seems like most or any of you guys messing with NRF5x are preferring nrf52.
I have however figured out one problem. Whenever my nrf51 was sleeping i was seeing 1ma current which is a deal killer. I accidentally discovered that disconnecting the st link and replugging it got sleep current to ~5ua. Something about uploading the program puts it in some state whereby it won't sleep properly.
So, I can get it to sleep all the way down now and I'm starting to understand the psel refsel stuff. And, I can make it trigger on p0.03 (an4 or 5, whatever) but its not particularly reliable. I need to get this section right:
void activateLpComp() {
NRF_LPCOMP->PSEL=4; // monitor AIN0 (i.e. pin P0.02 on nRF52832 PIR Motion Sensor v607).
while (!(NRF_LPCOMP->PSEL==4)) {} //wait until confirmed
NRF_LPCOMP->REFSEL=2; // choose 1/2 VDD as the reference voltage
while (!(NRF_LPCOMP->REFSEL==2)) {} //wait until confirmed
NRF_LPCOMP->ANADETECT=0; //detect CROSS events on PIR detection pin
while (NRF_LPCOMP->ANADETECT!=0) {} //wait until confirmed
NRF_LPCOMP->INTENSET=B1000; //Enable interrupt for CROSS event
while (!(((NRF_LPCOMP->INTENSET)&B1000)==B1000)) {} //wait until confirmed
NRF_LPCOMP->ENABLE=1; //Enable LPCOMP
while (!(NRF_LPCOMP->ENABLE==1)) {} //wait until confirmed
NRF_LPCOMP->TASKS_START=1; //start the LPCOMP
while (!(NRF_LPCOMP->EVENTS_READY)) {} //wait until ready
NVIC_SetPriority(LPCOMP_IRQn, 15);
NVIC_ClearPendingIRQ(LPCOMP_IRQn);
NVIC_EnableIRQ(LPCOMP_IRQn);
}```broker name is "embedded-mqtt-broker"
yeah well i got a few nrf51822 which was evidently a big mistake
No Ethernet, just mqtt
Thanks.
I'm really not too good at writing arduino code but I did come across this library:
https://github.com/mristau/Arduino_nRF5x_lowPower
Is this something that could be incorporated into the sketch and then use "normal" interrupts?
@nizoo91 right, well then there's no need to be setting IPs and such in the arduino...
@mfalkvidd
yeah, I don't think that's working. I think I may understand better why not, so correct me if I'm wrong.
The low power comparator only works on analog inputs and in the nrf51 board by @NeverDie the SCL marked pin on the board is tied to P0.10 which has no analog input on it.
So, what I think I need to do is cut the trace and re-route it to the INT marked on the board which is tied to P0.03 which is analog 1 (AIN1). At that point then I think I only need to change the line in the sketch to use pin 3 instead of 2.
I think all the MQTT/OH stuff looks right but I'm not sure what's going on with the arduino part.
You're using an UNO with an ethernet shield?
It works for you with an external broker?
2.4 works well enough. there were some big bugs squished with 2.5m1 hot on 2.4's heels.
If you're planning to use this more and more (and you likely will once you start to see what you can do) stick with the 2.x implementation of MQTT. I don't know how openhabian handles things. If you can, disable whatever bundled MQTT broker openhabian has and use the built in broker (for the sake of simplicity).
Enable/install the embedded (built in) broker by using PaperUI. Go to Add-ons->Misc and install the Embedded MQTT Broker.
Once installed, you'll have a new item in the PaperUI Inbox. That item will be the broker - add it. If you don't get it in your inbox you may still have an external broker running which will keep the embedded one from starting (two processes are trying to use a single port).
@Yveaux this has resolved it, thank you
does anyone have a sample sketch for this. i don't understand the whole pin assignment thing well enough to know what the heck i'm doing.
I grabbed the sketch from the 10 year pir but this seems much more geared to the nrf52
i may tinker with things some more in the next day or two to see if i can get MYS to connect to an external broker. i'm assuming @TimO knows best and if he can't get it to work i probably can't either but i'm not in love with how the embedded broker works (plus all the extra garbage it puts in the logs).
@yveaux
thank you, this sounds very promising! I will try it this evening
@jimmy-loyens
1 broker per port otherwise one won't start. Sounds like mys is connecting to 1883 and not 1884
@boozz
That isn't 100% the exact code. I convert the celcius manually so that temp graphed is farhenheit.
The first 2-3 nodes i put together I didn't know about the ismetric thing going on and I didn't want to go back and reflash those modules so I just make sure to calculate before sending to the GW. Definitely not a heater issue.
I've got two nodes sitting right next to each other taking measurements every 3-4 minutes and I'm finding the si7021 doesn't present a very fine-grained measurement like the dallas:
The green line is the dallas sensor and the red line is the si7021. How do I get the si7021 to behave more like the dallas?
as you can see I'm getting temperatures in steps greater than .5 degrees fahrenheit.
The si7021 is using @NeverDie round board with this code:
// SUMMARY: This demo sketch runs on MultiSensor Version 7 board with an I2C Si7021 module to transmit temperature, humidity, and battery voltage to a MySensors gateway using MySensors protocols.
// Note: because this is a passive node, node ID must be set manually to a unique sensor node ID:
#define MY_NODE_ID 128 // Passive mode requires static node ID
/**
* 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-2017 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 - tekka
*
* DESCRIPTION
* Passive node example: This is a passive & independent reporting node
*
*/
// This demo sketch uses the LowPowerLab SI7021 library and also some of its sample code: https://github.com/LowPowerLab/SI7021
// This demo sketch also draws from the MySensor's example MockMySensors sketch.
// This demo sketch also draws from some of the code posted by smilvert here: https://forum.mysensors.org/topic/7961/why-do-passive-nodes-need-to-set-their-node-id-manually/14
#define SHORT_WAIT 50
#include <Wire.h>
#include <SI7021.h> //from LowPowerLab: https://github.com/LowPowerLab/SI7021
SI7021 sensor;
// Enable debug prints
#define MY_DEBUG
// Enable passive mode
#define MY_PASSIVE_NODE
// 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>
#define CHILD_ID_TEMP 0 //definitions contributed by smilvert (see above credit)
#define CHILD_ID_HUM 1
// Initialize general message
MyMessage msgTemp(CHILD_ID_TEMP, V_TEMP);
MyMessage msgHum(CHILD_ID_HUM, V_HUM);
#define ID_S_MULTIMETER 28
MyMessage msg_S_MULTIMETER_V_VOLTAGE(ID_S_MULTIMETER,V_VOLTAGE);
float batteryVoltage=0;
float temperature=0;
int humidity=0;
void blinkityBlink(uint8_t repetitions) {
for (int x=0;x<repetitions;x++) {
digitalWrite(LED_BUILTIN,HIGH);
wait(20);
digitalWrite(LED_BUILTIN,LOW);
wait(100);
digitalWrite(LED_BUILTIN,HIGH);
wait(20);
digitalWrite(LED_BUILTIN,LOW);
if (x<(repetitions-1)) { //skip waiting at the end of the final repetition
wait(500);
}
}
}
void setup()
{
hwPinMode(LED_BUILTIN,OUTPUT_D0H1);
blinkityBlink(5); //signify power-up and start of operations
sensor.begin();
NRF_CLOCK->INTENSET=B11; //enable interrupts for EVENTS_HFCLKSTARTED and EVENTS_LFCLKSTARTED
NRF_CLOCK->TASKS_HFCLKSTART=1; //start the high frequency crystal oscillator clock
while (!(NRF_CLOCK->EVENTS_HFCLKSTARTED)) {} //wait until high frequency crystal oscillator clock is up to speed and working
}
void presentation()
{
// Send the sketch version information to the gateway and controller
sendSketchInfo("Passive node", "1.0");
// Register all sensors to gw (they will be created as child devices)
present(CHILD_ID_TEMP, S_TEMP);
wait(SHORT_WAIT);
present(CHILD_ID_HUM, S_HUM);
wait(SHORT_WAIT);
present(ID_S_MULTIMETER,S_MULTIMETER,"Electric Station");
wait(SHORT_WAIT);
}
void loop() {
// get humidity and temperature in one shot, saves power because sensor takes temperature when doing humidity anyway
si7021_env data = sensor.getHumidityAndTemperature();
temperature = data.celsiusHundredths/100;
// humidity is an integer representing percent
humidity = data.humidityBasisPoints/100;
sleep(60000); //sleep for one minute to recover voltage after temperature and humidity measurements.
send(msgTemp.set(temperature,2));
sleep(60000); //sleep for 60 seconds
send(msgHum.set(humidity,0));
batteryVoltage=((float)hwCPUVoltage())/1000.0; //take voltage measurement after transmission to hopefully measure lowest voltage that occurs.
sleep(60000); //sleep for one minute
send(msg_S_MULTIMETER_V_VOLTAGE.set(batteryVoltage,3)); //send battery voltage with 3 decimal places
sleep(60000); //sleep for 60 seconds
}
I'm still planning to use MQTT as I have it tied to about 20 esp8266s around the house so I would never abandon it
One problem I'm having now that I switched over to the embedded broker is the LWT doesn't seem to work right.
I have a module in each car that when it disconnects send a LWT of off so I know to automatically close garage doors. Using the embedded broker has broken this for some reason??? So I start to think why not just use ethernet for mysensors. Fix one problem create 10 more
Sorry to be a pain, but where exactly are things failing right now?
is there any reason to prefer MQTT over Ethernet? If getting MQTT to work is this much of a pain why are we bothering?
Maybe I'm missing something
irq=18 worked for me for anyone who comes along wondering
@nizoo91 said in Temp-Monitoring using OpenHab, MQTT, Pi 3 & Uno:
Can I transmit and receive data using the MySensors libraries without installing MySensors in OpenHab? (because I don't have it, according to the tutorial it wasn't installed)
For the MQTT Broker on PaperUI, I was only able to get it online by using "LocalHost" is that right?
You don't need the mysensors binding if all you're doing is taking in readings. you'd probably be better for it.
localhost/127.0.0.1/the actual ip should all work. if localhost works, just use that. don't make it complicated.
I have two gateways (though i would like to eliminate the second) since i have two PIs running at opposite ends of the house on different floors. They both talk MQTT to openhab. For the couple of nods that can reach both GW at most I see two MQTT messages with the same data. More advanced features I can't comment on. I'm not using the OH binding on any nodes that reach more than 1 GW. Most of my nodes just provide sensor data, so duplicate data doesn't both it.
@timo
works for me, will try it out.
also, i got it working another way. tested it on clean installs of 2.4.0 vs 2.5.0-1512
back to the config file org.eclipse.smarthome.mqttbroker.cfg
not sure why it didn't work in 2.5.0 the first time. i'm starting to think it was leftover in the userdata folder which is why i thought it was no longer necessary in the services directory
but, if i can skip it altogether and user the system broker then i'm just as happy with that. one less thing.
BTW, for anyone who happens along this thread in the future: literally the only two bindings you need to install in 2.4.0-2.5.0 is the serial binding and the mqtt (2.x) binding. then drop the mysensors binding in. that's it. it's so much easier now.
@TimO @davidgraeff
I don't know if this is of any use or not but many hours later in my openhab.log I received this:
2019-01-31 06:05:37.371 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method 'ThingHandler.handleComm$
java.lang.NullPointerException: null
at org.openhab.binding.mysensors.internal.gateway.MySensorsGateway.sendMessage(MySensorsGateway.java:366) ~[?:?]
at org.openhab.binding.mysensors.handler.MySensorsThingHandler.handleCommand(MySensorsThingHandler.java:200) ~[?:?]
at sun.reflect.GeneratedMethodAccessor150.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [102:or$
at org.eclipse.smarthome.core.internal.common.InvocationHandlerSync.invoke(InvocationHandlerSync.java:59) [102:org.eclipse.smart$
at com.sun.proxy.$Proxy202.handleCommand(Unknown Source) [187:org.openhab.binding.mysensors:2.4.0.201812040738]
at org.eclipse.smarthome.core.thing.internal.profiles.ProfileCallbackImpl.handleCommand(ProfileCallbackImpl.java:75) [109:org.ec$
at org.eclipse.smarthome.core.thing.internal.profiles.SystemDefaultProfile.onCommandFromItem(SystemDefaultProfile.java:49) [109:$
at sun.reflect.GeneratedMethodAccessor149.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [102:or$
at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:53) [102:org.eclipse.smarthome.core:0.11.0.2019011$
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
at java.lang.Thread.run(Thread.java:748) [?:?]