From 73fc274bc206ea2d6ca4f5e79cb192583f44715a Mon Sep 17 00:00:00 2001 From: PLTorrent <33349763+PLTorrent@users.noreply.github.com> Date: Fri, 10 Jul 2020 15:44:01 +0200 Subject: [PATCH] Update README.md (#72) I think users are confused and try to extract the encryption key from their mobile devices even if they currently don't have to I think the readme file is misleading. Please find the proposed changes to the file in order to avoid customer confusion. This would also solve #64 #69 #71 . Best Regards ;] --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 0fbcbb4..f4ff60b 100644 --- a/README.md +++ b/README.md @@ -40,7 +40,7 @@ This component is added to HACS default repository list. port: 7000 mac: '' target_temp_step: 1 - encryption_key: + encryption_key: uid: temp_sensor: lights: @@ -74,7 +74,7 @@ This component is added to HACS default repository list. custom_components.gree.climate: debug ``` -5. OPTIONAL: Provide encryption key if HVAC's wifi is already configured. +5. OPTIONAL: Provide encryption key if you have it or feel like extracting it. One way is to pull the sqlite db from android device like described here: @@ -86,7 +86,7 @@ This component is added to HACS default repository list. sqlite3 data.ab 'select privateKey from db_device_20170503;' # but table name can differ a little bit. ``` - Write it down in climate.yaml `encryption_key: `. This solves Issue#1. + Write it down in climate.yaml `encryption_key: `. 6. OPTIONAL: Provide the `uid` parameter (can be sniffed) NOTE: This is not needed for all devices