POWR2 (PSC-B67-GL) Not realtime data, Homebridge logs data is wrong
<!-- PLEASE READ BEFORE POSTING A NEW ISSUE
   → Please use this template as well as you can.
   → Things that may seem unimportant are often helpful in finding the cause of the issue.
-->

### What issue do you have? Please be as thorough and explicit as possible.

POWR2 (PSC-B67-GL)
-I use such a tool to measure current energy consumption. I see that the current data is only displayed in homebridge when the ewelink app is also open on my phone. If I close the app, the data will not be updated.


-In the homebridge logs section, the data is displayed incorrectly.
[2021. 01. 25. 21:14:03] [eWeLink] [Melegház Watt mérő] current power [2009.81W] voltage [2009.81V] current [2009.81A].
[2021. 01. 25. 21:14:21] [eWeLink] [Melegház Watt mérő] current power [2004.39W] voltage [2004.39V] current [2004.39A].
[2021. 01. 25. 21:14:21] [eWeLink] [Melegház Watt mérő] current power [2004.48W] voltage [2004.48V] current [2004.48A].

Power and current are used instead of voltage and current.
It would look right like that:
[2021. 01. 25. 21:14:21] [eWeLink] [Melegház Watt mérő] current power [2004.48W] voltage [228.93V] current [8.98A].
### Details of your setup.
* Do you use (1) Homebridge (+ config-ui), (2) Homebridge (CLI) or (3) HOOBS? 



* Which version of Homebridge/HOOBS do you have?

homebridge-config-ui-x v4.36.0

* Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.

Raspberry 

* Which version of this plugin (homebridge-ewelink) do you have? Has the issue started since upgrading from a previous version?

homebridge-ewelink v4.4.6-0

* Which eWeLink devices do you have that are causing issues? Please include product models if applicable.

POWR2 (PSC-B67-GL)

### Please paste any relevant logs below.
<!-- ABOUT LOGS
   → More logging can enabled with 'Debug Logging' in the plugin settings.
   → If you are posting an error then it is helpful for me to also see
     the previous few lines as this can show the cause of the error.
   → Please enter the logs between the two ``` lines below so that the
     logs are formatted in a way which is easier to read.
-->

```

```
