My Project

@Artmai said in Looking for bluetooth proximity tracking (+/- 10cm precision) hardware.: hardware solution would you recommend me to build a small device sending Bluetooth signals that an iPh any other techno you would recommend to track this though?

@Yveaux Thanks for your reply. I've done a lot of debugging today. And I guess I found the issue. It's definitely related to the radio power consumption as you suggested. I'm currently using the new RFM69 driver, with ATC enabled by default. As long as the power level stays below -4 dB, everything works fine. If the gateway is powered off, the radio power level automatically increases to 100% and the PIR behaves weird. It's always HIGH. By rebooting the gateway, the node relink itself and gradually lowers its power. As before, when it goes below -4dB the PIR starts to work again. Since it's a battery powered device I decided to set #define MY_RFM69_MAX_POWER_LEVEL_DBM (-4) at the beginning of the sketch file. Even if the gateway fails (shutdown) the PIR does not get HIGH anymore. All the measurements work fine now by limiting the max power to the radio. By doing so all the sleeps of 1000ms after each send are not needed anymore.

@brendanl Sounds like you're speaking from experience... I've never worked with a Daikin system, but I have had my share of similar problems in my years of working on electronics..

@jeremushka I haven't done it on the smart outlet but I did do it on my "Whole House Fan" project. You can check out the code from that if you're interested. Here is a link to the video if you wanted to check that out: https://youtu.be/KVsUe7sOCPo Also, just make sure you check out the specs on the acs712 and don't pass through more current than is safe. I don't remember the specs off the top of my head but I knew my whole house fan was safe because of what it would be drawing

@Nca78 said in First go at a smallish TH sensor that can be deployed anywhere.: At what voltage are you running your sensebender micro ? Using 2x AA batteries (3V) Current multimeter reading is 2.75V, reading on Vera is 57%. Looks like reading on Vera is out. I've stuck on a sticker with today's date to see how long sensebender will go on, probably a few years.

by looking at the picture the voltage is measured near the battery, so I'd say it is the battery voltage

@raulandresmoch The 3D design is for the Easy Newbie PCB designed by @sundberg84. The board carries an arduino pro mini and the nRF24L01+ radio.

@mfalkvidd YES!!!! That was the problem!!!! Thank you so much!!!!

@Newzwaver I think that makes sense. D3 on Wemos D1 Minis is GPIO0. I usually use the Dn notation, because I find it easier to understand.

@ben999 just for the record... =! is wrong. Should have been != Makes quite a difference :(

Re: LCD Clock and Text sensor node with new V_TEXT Hello , I have done the same exercise also with the LCD 4*20 and use the same program. It is great. It works but only I have the first line with the date. The lines 2,3,4 are empty. In Domoticz my V_TEXT are created and filled in. It seems that I can not read correctly the information LCD_line2, LCD_line3,LCD_line4 [image: 1510218377649-screen-shot-2017-11-09-at-9.56.27-am-resized.png] [image: 1510218402874-screen-shot-2017-11-09-at-9.55.50-am-resized.png] we can see that on the line READ , the text is V_TEXT but nothing is received. Why ? [image: 1510218423240-screen-shot-2017-11-09-at-9.50.27-am-resized.png] Thanks

@gohan alkaline batteries in general have been tested quite extensively and don't deviate much from the S-curve characteristics.

The low power node is now working as intended, the addition of an extra 47uf for the nrf power pin (there are two there now so a total of near 100uf) and an aditional .1uf on the LE33 power pin has made the node stable. It shows just how fussy the nrf can be about its power requirements. I have made the changes to the wiring diagram in the previous post to reflect these additions. Have also now had a chance to compare the graphs of the two nodes in Domoticz and the low powered node with voltage averaging seems to give a much better result. In the following pictures you can see the steady drop of voltage over time for the low power node and a more zigzag line for the original node. Will not know for sure until I add averaging to the first node, maybe the extra power draw is also affecting the reading. The original node [image: 1509918567429-graph2-resized.jpeg] The low powered node. These are both connected to the same vehicle at the moment. [image: 1509918629434-graph1-resized.jpeg]

@Yveaux Thanks, i will have a look at it

Go with the Z19. Here's some ready made code: https://forum.mysensors.org/topic/6528/mh-z19-co2-sensor/5