-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider rebranding/readme from RPI specific to any Linux system? #70
Comments
Now that I'm looking at it, It's really just the title. Could be worth adding a mention in the readme still. |
Yeah the project evolved from RPI specific to something more general. Cleaning of the readme is always welcome! |
Nice project! And I also really like to use this on non-rpi hosts (macmini running ubuntu in my case). I think a little more work is involved. The mqtt config topics for home assistants autodiscovery still add 'RPI' as manufacturer and 'RPI {deviceName}' as model for all the devices created. And personally I have at least one error running this on something non-rpi, the underVoltage stuff doesn't work. Is there a dependency missing in requirements.txt or should this maybe become disableable as well?
|
Undervoltage wouldn't work because this is RPI specific. You can disable it in the settings. |
@Sennevds Thank you for this project, loving it. I've modified it a bit to suite my needs. You can find my changes here (diff).
In the future i want to extend it, make it more modular so different type of services can be monitored |
May I ask how you have it on other platforms? Edit: I've just started it manually rather than via the service and get the below:
Edit Again: I manually removed the temperature and power sensors from the code, all is working well now for a VM. |
Can you share your version? |
Please see attached, I've also renamed all the references from RPi to VM. |
Works on my vm perfectly well. Thank you <3 |
Hello! thanks for this! works perfectly on ubuntu! only one thing, I am not getting available updates :-( what am I missing? |
Since there's been a bit of change to the code base and it now running nicely on any Linux system (personally have it running on aarch64, armv61 and x86 64/32 bit platforms), perhaps this tool should be rebranded and readme updated to reflect its potential.
I'm happy to dig through the readme if you're keen.
The text was updated successfully, but these errors were encountered: