| //https://forum.iobroker.net/post/133815 | |
| //VL, outgoing temperature | |
| const idTempVL = 'sonoff.0.HWR.DS18B20-2_Temperature'; | |
| const iddTVL = '0_userdata.0.WWZirkulationspumpe.dTVL'; | |
| const swOn = 0.7; // Grenzwert in K/min | |
| var speedVL | |
| var speedVLold = 0; | |
| //RL, return temperature |
As a general principle, I'm not in favour of override files. I think they muddy the waters. I think you're much better off editing docker-compose.yml directly.
That said…
When you use IOTstack to manage Docker containers, you have access to two override mechanisms:
compose-override.yml file. This mechanism is peculiar to IOTstack and is implemented by the so-called "new" menu on the master branch.docker-compose.override.yml file. This mechanism is part of docker-compose.
This gist answers a Discord question. It explains my approach to collecting CPU temperatures by sending the data as an MQTT payload.
I like to think of this approach as working with the MING (Mosquitto, InfluxDB, Node-RED, Grafana) paradigm rather than fighting against it (eg using approaches like SSH calling out of the Node-RED container).
The approach is not tied to the Raspberry Pi that is running IOTstack. If you have several Raspberry Pis, they can all log their temperatures to the Raspberry Pi running IOTstack using exactly the same mechanism.
| #!/bin/bash | |
| command -v docker >/dev/null 2>&1 || { echo >&2 "I require Docker but it's not installed. Aborting."; exit 1; } | |
| echo "Basic auth for traefik >= v1.7" | |
| read -p "User: " USER | |
| read -p "Password: " PW | |
| # Pull httpd:alpine image (small and includes httpasswd) | |
| docker pull httpd:alpine >/dev/null 2>&1 |