Fix connection type on BS444

A number of BS444 users report having problems connecting to the scale using random BLE adressing. This version uses public adressing when the BS444 is selected in the BS440.ini file.

Catch up with latest features

Realized that potential users download the lastest Release which is currently over 3 years old...
Since then these addidions were made (among many others!)

• fix exception error on disconnect
• BS410, 430, 444 support
• Node-red flow to graph CSV data
• MQTT support
• InfluxDB support

BS440 with plugin support

It worried me that each time a new kind of data processing was added by a pull request by one of the much appreciated contributers the base BS440.py program would be changed. Also the .ini file would contain empty sections to enable/disable processing options and imports would depend on the data processors used.
That's all history now.

From this version on it is possible to leave the BS440.py and its .ini untouched. Data processors reside in a subfolder called "plugins". All files named "BS440pluginname.py" will be called with the scale data as parameters.
Also each plugin uses its private BS440pluginname.ini to configure its task.

When communication to the scale works, most of the testing left will be testing the plugin. That's why i wrote BS440test.py which produces data exactly like a real scale en also searches for plugins the way BS440.py does. Values created by BS440test.py can be modified by changing BS440test.ini

A good starting point for your plugin is _BS440plugintemplate.py. It contains the "must haves" to be able to run as plugin. When done, rename it to BS440yourplugin.py to have it recognized and run by BS440.py
One note: In version 1.0 additional Data processors were merely imported. In 2.0 plugins come as Classes and the processing is done in its methods.

In this repo all plugins will be published Inactive i.e. preceded with the underscore. To activate the plugin rename the file on the target machine.

First release

First stable release