-
Notifications
You must be signed in to change notification settings - Fork 117
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 missing energyMeter data to emoncmss_publish() #580
Conversation
EmonCMS only accepts numeric data and does not necessarily need all the data exposed by event_send. Also as EmonCMS will typically be remote and WS/MQTT local sending less data is best. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the logic to event the data should be removed from the energy_monitor and just add evse.createEnergyMeterJsonDoc
to create_rapi_json
so it is inline with the previous implementation and does not hit the EmonCMS severs more than previously
I'm agree, and not sure :) I've wanted to move it out of this create_rapi_json() because it's not RAPI data. edit: for now I've moved it back to create_rapi_json |
For now it is probably best to make that change, we can rename that function to make it clearer that it is not just RAPI if you want. |
…sing data to emoncms ) move deprecated properties in create_rapi_json ( were missing for emoncms )
rebased and ready |
Apologies, ignore that. I was using the wrong build :-/ It's actually working great 👍 |
forgot this one
Also put the deprecated properties in create_rapi_json as they are missing for emoncms publish
( time to ask emoncms to use the new properties before deprecation )
edit: is there a good reason why data are sent separately to emoncms instead of using event_send like websocket & mqtt?
Also it seems we should send the full /status topic to emoncms instead of create_rapi_json as more data are now coming from ESP32 and not RAPI.