jalle19 / eachwatt Goto Github PK

Currently the only way to visualize groups is by querying the data published to InfluxDB

IotaWatt at least supports this

The logic becomes too complicated then, best to avoid it

Hidden sensors can be used as children for a virtual sensor, but are not published individually to publishers. This can be useful to combine multiple different lighting-related sensors into one or more.

Timeout could be e.g. half of the polling interval

We need a logger per module at least so we know where messages come from. The console publisher can use one as well.

Currently if a sensor glitches and throws an error we end up publishing 0 watts, which is incorrect

Currently it's missing and the web interface may become out of sync

It needs to build the web interface and read the configuration file from a static path that can be mounted by the user, etc.

Copy-paste typo

For real-time monitoring, preferably with WebSockets

The current situation where the WebSocket URL must be specified in the client is unbearable

Perhaps with Home Assistant support for easy integration

Weird things start happening if we fail to resolve any circular references in the configuration

In the future we might be able to click ourselves to a "phase" page that shows everything that's connected to that phase.