@John Thanks for the reply, work got in the way this past week… My core drill lost a battle with a concrete wall…
In response:
Yes, 0/1 vs ON/OFF is independant of transmission mode - I didn’t feel the need to make it any more complicated. I could include setup.h in converter.h to bring BOOLNUM from there possibly.
I didn’t really understand the purpose of mqttSerial, so in https.h I just used the regular Serial print. Is this an issue do you think?
3.agreed, yes.
On the list for EmonCMS requirements (without MQTT), I agree with your observation of what needs to be defined. The ONEVAL_ONETOPIC is a good catch. If that is defined then the ‘#else’ after it isn’t caught (main.cpp line 78) so the jsonbuff/jsonbuffhttps are not populated.
I have added a section in my readme to make the EmonCMS definition requirements all clear
An EMONCMS define could deal with defining BOOLNUM, HTTPS, not-MQTT in one go, but I’d struggle with ONEVAL_ONETOPIC as that my need to be controlled independantly if someone else wanted to use that (i.e. in the case that EMONCMS was not defined, and they wanted to define ONEVAL_ONETOPIC).
I’ve had this compiled and it runs (on my desk, not in a heat pump) whenever my computer is on and it seems to be giving me the wifi strength, battery and memory reliably.
This looks like exactly what I’m after! If this can just get me “flow rate” directly into emonCMS I’ll have what I need for my heat pump monitoring.
I’ve tried HA and not really got on with it so far, whereas emonCMS just works for me.
Thanks Phil. I’m green on these coding aspects (but have managed to get an M5stickplus2 sending values to HA).
Please could you be a bit more explicit on what I need to change in these files:
in converters.h, BOOLNUM needs to be defined - this means that rather than ON or OFF being sent, the data is 0 or 1 which is what EMONCMS is expecting
in setup.h, HTTPS needs to be defined, as well as MQTT not being defined
also in setup.h, ONETOPIC_ONEVAL should not be defined.
APIKEY and NODE also need to be defined with your own values
Hi @scanfer
If you’ve managed to make the HA bit work then you’ve presumably got as far as being in plaformio and compiling the cose to the M5 device, well done so far.
You’ll need to go to my pull request in github and download that, rather than the main program from Raomin.
As regards the steps needed for making it go direct to emoncms then what you’ve posted back is the summary. To be more explicit:
in converters.h, BOOLNUM needs to be defined - this means that rather than ON or OFF being sent, the data is 0 or 1 which is what EMONCMS is expecting
Only issue seems to be the 3 port flag, I’m not seeing this getting picked up to identify the water heating.
Any ideas?
Pleased to get this working prior to some plumbing improvements to help flow and maybe cop. Cold week coming up to get some good baseline data too!
@scanfer presumably you have asked for that in the list of data to send. I don’t see it in the screenshot above.
Do you have any of the 0/1 data that would have been ON/OFF in the normal HA/MQTT version?
@Phil_E I’m using “3way valveOn”, firstly I should check that it’s the correct one to use to detect DHW?
It’s showing as zero in emonCMS Data Viewer since logging started on saturday.
Hi all, i am going to give this a go this afternoon, as above i have the data in home assistant , i have my emoncms account setup, im expecting to run in to some issues as my coding skills are still in there youth , before i get started is there a step by step guide anywhere ? and my last question will any of the changes effect my HA integration ?
is there a instruction about how to do @Phil_E download and what to do with it
Just a quick thanks to you and others on this thread. By following these steps I have got the data from my Daikin direct into Open Energy Monitor. It is much a much simpler setup overall than using Home Assistant for the reasons you have set out. So do hope your request gets accepted.
The only problems I hit were:
As Simon Scanfer found, the 3-way valve signal is coming through but is zero all the time. This means that I do’t get separate data for hot water and heating. I have uncommented the line below
{0x60,12,306,1,-1,“3way valve(On:DHW_Off:Space)”},
and also uncommented #define BOOLNUM in converters.h
I could not find the definition file ALTHERMA(TOP-GRADE) which others have mentioned is the correct one for my heat pump (Altherma 3H HT split). Just wondering if therefore I’m using the wrong code for the 3-way valve.
Thanks again for all the work. Any advice welcome.
Thanks all for the posts of late, I’m in the middle of silly season in the Alps pre Christmas getting all my installation work done, so I’ve not had time to look at this for a bit - and I’m likely going to switch to mainly Vaillant heat pumps - training course is in a couple of weeks… (sorry!)
Well done to those who’ve commented, implemented and used the non-HA version I worked on, I’m really pleased it’s been helpful, if anyone can figure out the DHW / 3-way valve flag issue that @martinc and @scanfer had then that would be great.
@Chris_Hill I’ve not got time to look deeply at what you just said right now, but is this yaml (I’d have to google what that means!) something that you do in emoncms rather than in the code from my pull request - so that for the ESP code you leave BOOLNUM not defined on the ESP board (so it sends on/off) and then the data is formatted to 0/1’s on arrival to emoncms?
Would that help @scanfer and @martinc ? If so can you put a couple of screenshots of how to do this so they can benefit?