This may take minutes upon first boot as the file system is being prepared. Once connected, browse to a random HTTP website and you will be redirected to the configuration page.
To change the configuration the ESP needs to boot without being able to connect to your configured Access Point. This is designed to run on an Adafruit Huzzah or Wemos D1 mini which will fit inside the battery compartment of the Efergy Receiver unit. Skip to content.
I guess it messes with the timing. I realized that debug messages on UART reset the micro. But take into account that now I'm not using any radio module What a coincidence. I returned to this project today also.
I still have to share the SPI bus with the Ethernet module though. I'll let you know how it goes. The ethernet GW approach performs even worse than your original solution. I get one or 2 measurements and then nothing. Still responds to ping but no communication with the controller. I don't know how to debug this since it just stops working. Is there by any chance anything in the code that consumes memory?
I was wondering do you know if we need to have established link between the wireless sensor and the receiver? I only have the wireless sensor so I was wondering if I can use this without the receiver? I could try again now with the new MySensors 2.
I have been trying to receive the efergy signal using RFM69 and so far it's a dead end. I'm unable to receive any data on the RFM69 module. Since you guys talked about RFM69 module here, I thought you might have some insight to share.
I bought the parts back in January and just found it in a drawer this evening. I can't receive any data, and i don't know how to substitute the code block related to RF12 with a correct one for my receiver.
Can someone help me? Thanks in advance, Mauro. I tried for years to received my Chacon Ecowatt a rebranded Efergy 2 classic data. I knew the frequency wasn't I lastly opened transmitter case to find which RF chip was used On last resort, I sought a signal on all " I did find something centered on As for Somfy stuff which uses Didn't happen. Once I found your contribution at the end of the comments on Gough's site I got my hopes up.
After a bit of frequency tuning I finally got a validated preamble but still no successful readings. Just the same sequence of bytes. I assumed that the pulses-to-bits-converion was ok since I got the same sequence over and over again. Added these two things together and came to the conclusion that. Some device identifier? Battery status? I got really excited about this and I basically just wanted to say thanks!
I will add to your code locally. If I get things fully working I could push if you'd like me to,. The text was updated successfully, but these errors were encountered:. Thanks for the comment. I'm glad the code helped at least somewhat. When you get it all the way figured out, be sure to post an update and I'll add a section with defines for the e2 IR power meter.
It'd be great if we could have sets of defines to support each Efergy product, all in one file. I correctly retrieve an 8 byte sequence every 6 seconds, but i cannot decode that. Note: first 4 bytes never change only 64 changes into after link missing the 10 i believe is a multiplier, W it becomes Where you able to verify using the checksum code?
Sorry for my incredible delay Now the arduino code is done now i have to test if it keep working on long time , there is a difference of some watt between lcd and arduino but I believe is a rounding problem between the two electronics Hi all! There is a bug in the code bytes[6] should be treated as signed number.
Thus change the line affected by the computation to You will get that error if the monitor receives a low wattage data where bytes[6] variable should be a negative number :. The issue isn't bytes[6] - char is already signed, so the code additions you gave there do nothing at all.
Compile with clang and you'll find clang's static code analysis even points out that fact. The issue is that bytes[4] and bytes[5] are also signed, when they should be treated as unsigned.
If bytes[4] is over 0x80 it would result in negative numbers, while if bytes[5] is over 0x80 it wouldn't result in a massive difference, but it would be subtly different lower by a few watts for example than what the receiver reads.
The good news is it's easily fixed in one line with a bit of type casting. I can't download the source code. It keeps insisting I install ilivid executable. What's the secret? User Gough Lui has posted a modifed code from his blog site. Maybe if you can try downloading it from his site? Does anyone have the original piece of source code for raspberry pi and efergy e2?
Does anyone know if this code is suppose to work with e2-ir? Tuner error set to 25 ppm. Tuned to Hz. Oversampling input by: 6x. Oversampling output by: 1x. Buffer size: 7. Output at Hz. Sample Values: negative positive Wave Center: this frame 0 last frame Decode from positive pulses: 09 2e 14 40 00 00 00 00 chk: 8b kW: 0. Sample rate set to Bit detection level set to Tuner gain set to Auto.
Reading samples in async mode
0コメント