-
Notifications
You must be signed in to change notification settings - Fork 2
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
More usage examples or ? #6
Comments
Yep, more examples are needed. This version 2 module is just the code for the Efergy Component, Wifi, MQTT is now not part of this code any more, so user can utilise the library how they need. I have just pushed an example with Wifi and Slack if that helps. you'll need to load the MQTT module and add that back in if you need. Hopefully that gets you underway. Documentation will happen at some point. :) |
Thanks, appreciate the new example. Having a play to see how far into it I can get. I use Telegram for event messaging out of Home Assistant with a ton of entities, not heard of Slack before tonight so will have to see I can adapt. BTW, how did you derive your TX ID initially to enter that into setup ? |
Create a loop of |
I stripped out the Slack code from the example and tried to work this out, but then after three or four JSON beginners tutorials on Youtube and reading stuff the ArduinoJSON website I'm still not able to work out how dump the objects from the efergy library to the arduino terminal. I've not looked at any JSON before this and it shows. |
Take a Look here for the JSON Object Names: And here on how to access the fields That should let you get the data out into a variable of your choice. you can see in the example we are getting the 'id' object out of the son dictionary to use in our transmitter notification routine. |
Thanks for the pointers, I'm trying this loop below currently as a general test if I can get the values, but getting 0's from all variables including the timestamp. (I've not shown the setup block as it's same as your examples minus the Slackpost code lines).
|
I notice you have the mainloop commented out, this will mean packets are not getting received, so it is possible this is just looping through empty data - This would return Null/None/False or 0 depending on the data type. Otherwise looks sensible. |
Modified to use the mainloop (I was not sure if I had to poll this or if it updated in the background).
|
You should be getting something. Can you set this in your Arduino code? This will dump out a heap of information about the Radio RX and decoding being performed for you. This might enlighten if we are beginning to decode anything and if there are errors. #define DEBUG 1 |
Actually if you remove the 'if' around mainloop, as you won't have any Transmitters Identified, it will return a False and not run the code in the loop. |
Thanks. Removed the if around the mainloop and set #define DEBUG from 0 to 1. [00d 00:00.01s] Efergy Monitor has intitialized. loop is now looking like this
|
Yeah, looks like you aren't receiving any data. Double check the inpin is set correctly to D0 and physically connected. I do notice it appears you aren't in debug mode still. When starting you should see a message like below on the console to indicate debugging is on |
OK I'll double check the signal on D0.
|
Also tried reassigning the data input pin to GPIO4 (D2), compiled and switched the cable. Same result as above. |
I tried something more basic today. Created a very small sketch that just reads pin 16 (D0 efergy signal) into a boolean and then right away sets pin 4 (D2) to that boolean in a tight loop. Digital equivalent of an analogue opamp 'follower' I guess... |
I know it's been 2 years now, but did you ever get this working? I'm also stuck on not recieving any data |
Hi @SarahDal It is definately working as it has been running for me for a couple of years. Haven't got back to the doco as I haven't had to touch it for a while to remind me. :) If you haven't had a look at some of the notes in this thread, please do, are you experiencing the exact same thing as mr-sneezy? I'm starting to think maybe there is a different style of receiver. |
Hi Steven, thanks so much for replying! Yes exact same errors, I've gone through this thread . Also, I see that a debug level was added, but I can't seem to set this, any number after #define DEBUG just returns the same level of info as #define DEBUG 1. Is there a different way to get the different debug levels? |
Just Enable debug like shown here in the example scripts:
|
Yes, debug is on, looks like I'm not getting any data. I can measure voltage change on the data wire, so I think there's something being sent? But all I recieve is
|
OK. The first couple of things to confirm.
Home that helps. |
I may have bitten off more than I can chew with my own fragmented coding knowledge (or lack of) with this version.
I've compiled the example ino and loaded to the Wemos D1 Mini, and connected to the Efergy E2.
In a serial terminal at 74880 baud, I see the ESP8266 serial boot message, then some initialization message from the firmware relating to the example settings, but then nothing else after that at all. No esp AP on air to connect too for configuration...
Have I mistakenly thought that there would be an AP on air to do the MQTT configuration etc, similar to what the original code readme describes, or is there a process I've not understood to configure wifi and MQTT settings for my network or get the Efergys TX ID with the library code ?
Sorry for the long winded question.
Serial terminal output.
ets Jan 8 2013,rst cause:2, boot mode:(3,7)
load 0x4010f000, len 3460, room 16
tail 4
chksum 0xcc
load 0x3fff20b8, len 40, room 4
tail 4
chksum 0xc9
csum 0xc9
v00044b70
~ld
[00d 00:00.01s] Efergy Monitor has intitialized.
with 20 events logged, status will change@ 80mA, report@ 60 seconds
The text was updated successfully, but these errors were encountered: