albertomontesg / hass-setup Goto Github PK

Currently some secrets are still hardcoded in the configs. Better if they are shared objects between deployments and configs.

Solution: Put them as secrets and then pass them as environmental variables.

The container image use does not have either rsync or scp commands which are needed to safely copy over SSH the configuration.

This looks to be the best data logger for the information about our Tesla car. This will require:

• A new DB to store the data,
• Reuse the MQTT we already have to export metrics and signals to Home Assistant (maybe we can disable the integration and rely completely in MQTT sensors),
• Reuse the Grafana dashboard we already have for the c6 cluster and add there all the dashboards and the connection to the TeslaMate DB. No need for an additional grafana instance (with project separation inside Grafana is enough).

Reference: https://docs.teslamate.org/

Documentation: https://www.home-assistant.io/integrations/prometheus/

Also add the energy consumption to a Grafana Dashboard.

Reference: https://github.com/CircuitSetup/Expandable-6-Channel-ESP32-Energy-Meter

This seems to be a better coordinator than the current CC2531 we have.

Reference: https://www.zigbee2mqtt.io/information/supported_adapters.html#slaeshs-cc2652rb-stick

Migrate all the devices to the new WiFi and IoT Subnetwork to provide more isolation.

This will require to update the network parameters for the ESPHome configurations. Also document the network setup.

The ideal scenario would be to trigger an action that pauses Netflix in one chromecast, and sends it to another chromecast. Investigate if is possible to do it with the pychromecast package.