Skip to content
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

sysinfo data doesn't get imported into influx for multiple plug units #4

Open
pixscooby opened this issue Jul 13, 2024 · 2 comments
Open
Assignees

Comments

@pixscooby
Copy link

emeter_output.json
sysinfo_output.json
influx
If I enable JSON files (attached), I can see the state of each plug is logged in the sysinfo JSON, however the child devices don't get imported into InfluxDB. I'm assuming this is because the emeter JSON uses plug_alias for the description and sysinfo uses alias under children. My goal is to know when a device has failed and see the state is on while not using any energy, but I'm not sure how to work the data into influx.

@lux4rd0 lux4rd0 self-assigned this Sep 29, 2024
@lux4rd0
Copy link
Owner

lux4rd0 commented Sep 29, 2024

Ohhh, sorry for missing this, @pixscooby. I just did a quick update for a few other issues tonight. I'll take a quick look at these and see how I can help.

@lux4rd0
Copy link
Owner

lux4rd0 commented Sep 29, 2024

I think I can do something here: enrich data from the sysinfo, add it to the emeter data, and connect those tags. I do track the state of plugs if you look at the Device Details dashboard:

screencapture-grafana-tylephony-d-d6ee3bd9-dafe-46cc-9dad-cd1f8e5ea6b1-kasa-collector-device-details-2024-09-28-23_13_22

But they are not connected to the emeter data - since that JSON doesn't contain direct relationship data - only alias information.

Now - I do add all of the JSON details available from Sysinfo into InfluxDB - but again - not tightly coupled to emeter - I only did enough to create an overview visualization.

I'll keep noodling on this and see if I can't get something added! Feel free to comment or add more details as well! I'll see what I can do!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants