Add plugin for mupihat

[stopfkuchen]

This pull request introduces the initial plugin for the MuPiHAT.

It has been tested in hardware by different test users. The Plugin is for the RaspberryPI HAT see mupihat.de

It includes setup for the MuPiHAT Volumio plugin, providing battery monitoring and management capabilities for the MuPiHAT Raspberry Pi HAT. The changes include configuration files, UI definitions, localization, installation scripts, and package management files to enable full integration with Volumio. The most important changes are grouped below:

Plugin Configuration and UI:

• Added UIConfig.json to define the plugin's configuration interface, allowing users to select battery types, set custom voltage thresholds, and view MuPiHAT status from the Volumio web UI.
• Added English localization strings in strings_en.json for all UI elements and documentation tooltips.

Plugin Settings and Defaults:

• Introduced config.json to store default plugin settings, including battery type, current limit, and custom voltage thresholds for battery management.

Installation and System Integration:

• Added an installation script install.sh that sets up system and Python dependencies, copies necessary files, configures boot scripts, and installs/enables a systemd service for the MuPiHAT battery management daemon.
• Included a systemd service file mupi_hat.service for managing the MuPiHAT background service, ensuring it starts with the system and integrates with Volumio.

Package Management:

• Added package.json and package-lock.json to define Node.js dependencies, plugin metadata, and compatibility requirements for Volumio and Node.js versions. [1] [2]

[balbuze]

hello!
Thank you for the plugin!
Just some points:
In package.json remove amd64
In install.sh
why do you install the venv in /data/INTERNAL? This rather for user settings like filters for DSP or skins for peppymeter. Install it in the plugin folder directly.
Each change, update version number in package.json
And when ok, submit with
volumio plugin submit
TY

[foonerd]

@stopfkuchen - Are there user configurable artifacts which will augment functionality? From the code itself the target category is audio_interface whereas controls are relaying on UI management only.

The /data/INTERNAL/... is used when there are user controlled parts interacting with plugins daemon. To prevent functional consistency keep the plugin in the default plugin opath.