- Change the device to use auto discovery
- Don't probe /dev/ttyAMA0 that upsets Raspberry PIs
After the changes in this PR I could see on my setup:
```
[...]
Running wmbusmeters ...
No wmbus device detected, waiting for a device to be plugged in.
No meters configured. Printing id:s of all telegrams heard!
```
Then I plugged in my dongle and...
```
Started auto rtlwmbus[00000001] listening on t1
Received telegram from: [ommissis]
manufacturer: (KAM) Kamstrup Energi (0x2c2d)
type: Cold water meter (0x16) encrypted
```
From README.md
```
It is recommended that you use auto to find your dongle, then, when you know the exact device path, you write for example: device=/dev/ttyUSB0:im871a:c1,t1 in the configuration file or on the command line. This will skip the slow probing for all possible dongles when wmbusmeters starts up.
If you have to scan serial devices, then remember that some Raspberry PIs are upset when random data is sent to /dev/ttyAMA0 when it is configured in bluetooth mode. To solve this, add donotprobe=/dev/ttyAMA0
```
* Move ha-addon files to repository
* Add repository json file
* Map raw usb access and uart devices
* Fix meter configuration naming
* Allow to use custom configuration for MQTT
* Fix syntax related to mqtt config
* Fix shothand if syntax
* Another try on syntax fix
* Fix mosquitto_pub.sh
* Fix mosquitto_pub.sh
* Refactor mqtt publisher script
* Clean config use
* Use explicit if
* Add docs for mqtt option
Jan Nielsen