-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Blueline PowerCost Monitor #1248
Comments
FCC : Data obtained by an IR-reader/sensor is transmitted in form of short bursts every 28.5 to 31.5 seconds on 433.92 MHz (single frequency). The carrier is On/Off pulse modulated (logic ‘1’: 0.5ms TX-on followed by 2ms TX-off, logic ‘0’: 0.5ms TX- on followed by 4ms TX-off). |
http://scruss.com/blog/2013/12/03/blueline-black-decker-power-monitor-rf-packets/ So you can just clean up the old code from the above branch. |
I think I have a valid packet captured. The ON period is 2ms, not 0.5ms as described in the FCC filing, but it has matching OFF periods of 2ms or 4ms. Can I ask why these produce the same results? Swapping short and long values in the decoder string?
|
That example might get the wrong results, you do need |
Sorry, I made a copy/paste error. One was |
For PPM short and long will only result in a threshold (6000 here) if no tolerance value is used. |
Blueline PowerCost monitor added by #1580 |
I'm unable to enable this filter for rtl_433:
Then the output interestingly:
Adding a second random protocol with
|
rtl_433 -R 176:auto should give you the key. And then rtl_433 -R 176:"key" should work. |
I've read the PR to try and get a better understanding of what's happening. I've run it with
Unless id is the key? Also, I think the missing "gap" is the packets when I pushed the button (twice). |
Aha, note to future people following the breadcrumps - read the comments in the source file for an exhaustive description of steps to follow and what is going on, as well as how to calculate kWh - https://github.com/merbanan/rtl_433/blob/master/src/devices/blueline.c I'm good to go - wonderful work by everyone involved. Looks like a lot of work was needed to get past the traditional stateless decoding, hopefully paving the way for future peculiar devices :) |
s/power/energy/ |
Has anyone looked at the battery info? Mine is returning a value of 1 with new batteries. I'm trying to determine if this is a flag that returns 1 for "good" and 0 (or some other value) for "bad" or if it returns a remaining percentage. I'm trying to set up a notification and right now all I have to trigger on is when battery_ok doesn't equal 1. |
I never hooked my monitor up to a variable power supply to see how the flags or battery status changed as the voltage decreased. My implementation was purely trusting the prior work. The old implementations only looked at one single bit for the battery, so that's all I did in mine. |
It looks like the code simply outputs "1" in my case. I can review what the previous work found if you have a link. I've looked at lots of code for this device over the last few years but never considered the battery because I never had anything working reliably (until now). |
Some references used include:
|
I am closing this issue now. If some one figures out the battery flag send a PR or reopen this issue. |
Home Assistant now has Energy tracking. Power monitoring devices not yet supported, but posting this here for reference as it may help other if/when power devices become supported.
|
Documentation : https://static.hydroottawa.com/documents/residential/conservation/pdf/peaksaver_user_guides/8-Energy-Display-Installation-Guide-EN.pdf
I'm a bit confused as there is reference to rtl_433 ( https://github.com/CapnBry/Powermon433/blob/master/arduino/Powermon433/Powermon433.ino ) but it's not a supported device. Perhaps the author meant he used rtl_433 to do the decoding.
I'm willing to capture the samples and submit to test repo. Based on the code above, I am using this
-X "name=blueline,modulation=OOK_MC_ZEROBIT,short=500,long=1000,r=58000"
Does that seem accurate?
The text was updated successfully, but these errors were encountered: