lux4rd0 / kasa-collector Goto Github PK

I always get this message. By visiting the code, I cannot find this file at all.

kasa-collector    | kasa-init: Starting Health Check
kasa-collector    | /kasa-collector/kasa-collector-init.sh: line 98: ./start-health-check.sh: No such file or directory

this is my compose

services:
  kasa-collector:
    container_name: kasa-collector
    environment:
      TZ: America/Chicago
      KASA_COLLECTOR_COLLECT_INTERVAL: 5
      KASA_COLLECTOR_DEVICE_HOST: 192.168.178.49
      KASA_COLLECTOR_HOST_HOSTNAME: localhost
      KASA_COLLECTOR_INFLUXDB_PASSWORD: none
      KASA_COLLECTOR_INFLUXDB_URL: http://influxdb:8086/write?db=kasa
      KASA_COLLECTOR_INFLUXDB_USERNAME: none
    image: lux4rd0/kasa-collector:latest
    restart: always
    depends_on:
      - influxdb

  influxdb:
    image: influxdb:1.8
    container_name: influxdb
    restart: always
    ports:
      - "8086:8086"


version: '3.3'

My unraid server is on a different VLAN than my the kasa devices. I would think this would be pretty much standard. Is there a way to specify the VLAN for the Kasa devices with respect to discovery or should it be able to find them anyway?

I am trying to just add the vlan to the network on unraid and see how that goes...

Welp, no luck. Could be user error, but I definitely won't be moving IoT devices out of an IoT network to see just to see something on grafana. This new version seems to be missing the ability to manually add devices? Is the only way to get devices added via discovery? I hope I am wrong about this and there is a way to manually add by assigning an IP address like before.

Thanks for any help

Now that I've collected 24h of data I'm not sure I understand what I am looking at here:

The power bar is reporting 68w but if you add up all 6 devices below you get 235.26w

This would lead me to believe the top 4 graphs are also incorrect if they are based on the power bar number.

It is also possible I simply do not understand what I am looking at :)

emeter_output.json
sysinfo_output.json

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.