Added some instructions for downgrading the apk to retrieve the token. The current root method does not work with the latest version of the app. I have not tested iOS but I assume the same would be true for all platforms/methods. I suggested apkmirror because they do signed builds and we want to avoid newbies grabbing malware.
Maria DB 10 have changed port from 3306 that Maria DB are using and is standard in this component. Maria DB is using port 3307 instead and that need to be added in the configuration to work. I have added a note in the description to add the port to the server_ip.
* Added instructions for magisk based root
AFAIK Magisk does not integrate with Android to provide an option for shell over adb. However it does allow you to escalate privileges once in a shell.
* Minor changes
The docker compose examples have you create a service called 'web', which will create web_1 docker container. Other references within the documents say to run `docker restart home-assistant`, yet this docker container does not exist when using the docker compose examples. Updated compose so they will have a standard name for the container that is created.
* adding a method to Recovery the token
The access token also can be found with the Command Line tool from miio. I tested this and works.
* Update format
# add paragraph to explain how to update docker-compose.yml example for macOS
# The TZ issue wasn't specific to `boot2docker`
# Add details link for net:host vs port: conflict
# Add details link for TZ issue
Since the website saves numbers with , the sensor ends up with "," when trying to use it in automations float does not work.
So i thought i added this if somone ells uses the example
We should recommend users to setup this optional configuration key, as some were unaware that this is a required step when they add devices in the future so we should inform them of this. Some users are not aware that they can also issue a voice command to sync the home assistant device list.
The basic venv install guide mentions this step so we should make sure the advanced guide has the same step in the same location.
The note about the advanced guide is there to reassure the user they are on the correct page even though the raspberry pi is heavily mentioned here.
