Hello simple man! :)

I like your repo, thanks for sharing! Personally I felt the flashing approach was simpler, and went that way. However with little success, the Shelly would not expose a /metrics endpoint even after I flashed a custom Tasmota binary (I started a discussion here).

What if I'd like to monitor multiple Shellys with your PHP docker? I find it a bit heavy to deploy a full PHP container for every Shelly I want to monitor... We're talking 5+.

I think a cool approach would be to identify them by routes rather than ports. Eg:

---
version: "3"

services:
  shelly-plug:
    container_name: shelly-plug
    image: php:8-apache
    ports:
      - "9924:80"
    environment:
      SHELLY_1_HOSTNAME='my-shelly-plug1-host-or-ip'
      SHELLY_1_IDENTIFIER='shelly-kitchen'
      SHELLY_1_HTTP_USERNAME='username'
      SHELLY_1_HTTP_PASSWORD='password'
      SHELLY_2_HOSTNAME='my-shelly-plug2-host-or-ip'
      SHELLY_2_IDENTIFIER='shelly-living-room'
      SHELLY_2_HTTP_USERNAME='username'
      SHELLY_2_HTTP_PASSWORD='password'
      SHELLY_3_HOSTNAME='my-shelly-plug3-host-or-ip'
      SHELLY_3_IDENTIFIER='shelly-dining-room'
      SHELLY_3_HTTP_USERNAME='username'
      SHELLY_3_HTTP_PASSWORD='password'
    volumes:
      - './:/var/www/html'
    restart: unless-stopped

Your code would then check for the defined env variables to know how many there are and expose them via the identifier variable: so to get metrics for the kitchen shelly, you'd go to: http://<dockerhost>:9924/shelly-kitchen/metrics and for the living room metrics: http://<dockerhost>:9924/shelly-living-room/metrics

What do you think?

Hello,

The version of metrics php file I'm using.

I get the temperature and customise the plug name.

metrics.txt

And the grafana dashboard

grafana_dashboard.txt

Hello,

On docker-compose.yml file this line : environment: SHELLY_HOSTNAME='my-shelly-plug-host-or-ip' SHELLY_HTTP_USERNAME='username' SHELLY_HTTP_PASSWORD='password'

Should be like that : environment: - SHELLY_HOSTNAME=my-shelly-plug-host-or-ip - SHELLY_HTTP_USERNAME=username - SHELLY_HTTP_PASSWORD=password

Removing ' and adding -

I followed the instruction and I get the data shown when I run the curl command. Also, I was able to add the data source to Grafana but when I try to look up the data I get no metrics found and the query returns no data. Any further instructions on how the data can be used in a Grafana dashboard?

Since the API for the plus devices is different, I've split up the functionality so that the functionality for polling the first generation is in one file, and the second gen in another.

The structure of these files is largely the same, and you still access both of them via the "metrics" entry point.

Key differences:

• The new generation uses digest authentication rather than basic, and has a hardcoded username
• The URL has changed, they now use an RPC style API
• The format of the json you get back is also different (but standardised across all the new generation

I've also added support for relays with multiple switches (i.e. PM2). I'm not able to test it extensively (yet), as all the relays I have are only of the single variety, but I'm fairly confident it should work, as it was only a minor tweak to the script

Also of note: The new shellys are also able to report temperature and voltage (and current in amps): https://shelly-api-docs.shelly.cloud/gen2/Components/FunctionalComponents/Switch#status - it might be cool to add them to the graphana/prometheus internet-pi monitoring suite (though I'm not familiar at all with either of them and I'm not sure how the output of this script makes its way into graphana (yet!)