You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to clarify how I see that the 'Add-On' feature of MaxAir is intended to work:
MaxAir has basic functionality + the ability to add extra additional functions via the use of 'Add-On'
MaxAir should be configurable from the user interface (not the command line)
MaxAir 'Add-Ons' should not impact on system resources, if they are not installed, to avoid over burdening a hardware platform with limitted resources (particularly in the case of budget SBCs).
MaxAir 'Add-Ons' should, wherever possible, be self contained, they should not include changes to existing code modules.
MaxAir 'Add-Ons' are installed using the Install Software option in the System Configuration menu
Each 'Add-On' should include an install.sh, which installs any dependencies, installs any services required and installs the 'Add-On' itself
If new services are deployed as part of the installation, they should be included in the services section of ajax.php, in order that they can be managed from the user interface
An example deployment is for the Amazon Echo 'Add-On'
An example of what is not an 'Add-On' would be support for Tasmota devices.
The text was updated successfully, but these errors were encountered:
Hi,
I'd like to clarify how I see that the 'Add-On' feature of MaxAir is intended to work:
An example deployment is for the Amazon Echo 'Add-On'
An example of what is not an 'Add-On' would be support for Tasmota devices.
The text was updated successfully, but these errors were encountered: