@gry2000 & @amansingh - This project was never intended to be a “turnkey” replacement solution for watchpower but rather an integration to HA for those who have a Smart Home setup (So I’m expecting that you will have experience on how to setup and configure Home Assistant before using this solution).
It’s clearly obvious that there’s a few of you out there that just want the interface that’s in the screenshot’s in Github without having to worry about the whole Home Assistant setup - Perhaps you (or someone else who fits this use-case and is competent with Linux) should look at making some sort of simple Raspberry Pi “Image” for these users with plain Grafana, InfluxDB, and the voltronic-mqtt once you’ve mastered how to set it up) - At this stage, I’m not prepared (or interested) in maintaining such an image as I have no use for it myself - and frankly, if anything in my HA architecture is not running within Docker, I won’t use it as it’s to hard to backup and restore in the event of hardware failures (with exception of course to my esp8266’s / other IoT Hardware).
Reading through your initial comments I see you’ve not read/followed/understood the Prerequisites & Configuration & Standing Up section of the readme which states that you need to set your “MQTT server’s IP/Host Name, Port, Credentials, HA topic, and name of the Inverter that you want displayed in Home Assistant” - So for anyone else with issues, please carefully read the readme before posting questions on the forum/github issues that are already covered in the readme.
Best of luck with your setup, at this stage I’d suggest you look at your logs in your failed container in Portainer and go from there, chances are you’ll need to double check your configuration and also that the image you’re pulling supports the architecture if your device (There’s multiple architectures that have been built on docker hub).
Lastly, if you’re using Portainer you won’t need watchtower since Portainer has the ability to ‘auto update’ containers when new releases are pushed to docker-hub… The docker-compose file that’s included on github is “lightweight & simple” so it can be easily deployed onto “lightweight” SBC devices in the field … I’d advise any users running this solution on “slow/low-end” devices to do without a container orchestration tool (Such as Swarm, Portainer, Kubernetes etc) since you’re probably only going to be a handful of containers on the device, and all these extra ‘tools’ will just slow down the SBC.
Note that if you’re plugging a regular computer into the inverter then you’ll probably be fine running everything with some sort of container orchestration tool - but this goes beyond the context of the setup guidelines outlined on the project’s github page.
Best of luck