One more issue that needs further digging, AC partner has Gateway function. Actually L

Seems Aqara's dev docs has been updating. At <a href="http://docs.opencloud.aqara.cn/d

<a class="user-mention notranslate" data-hovercard-type="user" data-hover

Still here's the screenshot: <a target="_blank" rel="noopener noreferrer nofollow"

Gateway function support,about syssi/xiaomi_airconditioningcompanion

Comments (45)

cxlwill commented on August 14, 2024 2

According to the latest Aqara Dev Docs, this device does support Lan communication: AC Partner Part

from xiaomi_airconditioningcompanion.

cxlwill commented on August 14, 2024 1

My ac partner v3 arrived today and I try to link it with HA directly. Here's the log:

2018-03-25 16:44:10 ERROR (Thread-13) [xiaomi_gateway] No data in response from hub {'sid': '7811dcb2a7d9', 'model': 'acpartner.v3', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat', 'token': 'aQXnsaock3BXBZUT'}
2018-03-25 16:44:20 ERROR (Thread-21) [xiaomi_gateway] No data in response from hub {'sid': '7811dcb2a7d9', 'model': 'acpartner.v3', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat', 'token': '2bp3EaxRgvXneZ69'}
2018-03-25 16:44:30 ERROR (Thread-14) [xiaomi_gateway] No data in response from hub {'sid': '7811dcb2a7d9', 'model': 'acpartner.v3', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat', 'token': 'dXioOwGOf4l5LByJ'}
2018-03-25 16:44:40 ERROR (Thread-3) [xiaomi_gateway] No data in response from hub {'sid': '7811dcb2a7d9', 'model': 'acpartner.v3', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat', 'token': 'LRTldgDLAnAudQH4'}
2018-03-25 16:44:50 ERROR (Thread-5) [xiaomi_gateway] No data in response from hub {'sid': '7811dcb2a7d9', 'model': 'acpartner.v3', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat', 'token': 'S2ZvU2tjPfMBHWua'}
2018-03-25 16:45:00 ERROR (Thread-13) [xiaomi_gateway] No data in response from hub {'sid': '7811dcb2a7d9', 'model': 'acpartner.v3', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat', 'token': 'U94zL1M9PkIT5ghm'}

Error it was, but unlike partner v2, partner v3 did response for search call. BTW, this production's fireware is 1.4.1_147.

And both nmap and nc work:

pi@raspberrypi:~ $ sudo nmap -sU -p 9898 192.168.50.99

Starting Nmap 7.40 ( https://nmap.org ) at 2018-03-25 16:53 CST
Nmap scan report for lumi-acpartner-v3_miio78478387 (192.168.50.99)
Host is up (0.020s latency).
PORT     STATE SERVICE
9898/udp open  monkeycom
MAC Address: 78:11:DC:B2:A7:D9 (Unknown)

Nmap done: 1 IP address (1 host up) scanned in 1.21 seconds

nc -v -uz 192.168.50.99 9898
found 0 associations
found 1 connections:
     1:	flags=82<CONNECTED,PREFERRED>
	outif (null)
	src 192.168.50.143 port 57240
	dst 192.168.50.99 port 9898
	rank info not available

Connection to 192.168.50.99 port 9898 [udp/monkeycom] succeeded!

from xiaomi_airconditioningcompanion.

cxlwill commented on August 14, 2024 1

Seems Aqara's dev docs has been updating. At Gateway Chapter (Eng) I notice that they add Only Air Conditioning Controller(advanced) supports LAN communication. So only mine model is supported now.
I use UDP/TCP tool and get positive feedback with

{
   "cmd":"discovery"
}

JSON UDP broadcast.
I'm modifying model in Pyxiaomigateway to see the result.

from xiaomi_airconditioningcompanion.

cxlwill commented on August 14, 2024 1

Yes.

from xiaomi_airconditioningcompanion.

Dem0n3D commented on August 14, 2024 1

@gsotiriou Bad news. There is no firmware update and it will be easier to buy another hardware revision.

Still no luck? Just faced this issue :(
Is this model supported?

from xiaomi_airconditioningcompanion.

cxlwill commented on August 14, 2024

Still here's the screenshot:

from xiaomi_airconditioningcompanion.

cxlwill commented on August 14, 2024

Some info update. With the latest firmware and MiHome app. I think finally AC partner's LAN port is open. I test it by nc -uz ac_partner_ip 9898 and receive positive respond Connection to ac_partner_ip port 9898 [udp/monkeycom] succeeded!, which means that UDP port is there. Further test will come since it use the same UDP port with Gateway I will try Gateway's method and HA's component.

from xiaomi_airconditioningcompanion.

syssi commented on August 14, 2024

Cool! Does the MiHome app provide a key now?

from xiaomi_airconditioningcompanion.

cxlwill commented on August 14, 2024

Yeah, actually MiHome app started to provide key since last year but failed to truly open Port 9898, which makes the key useless. I dig into it a bit further, it seems use v2.0 Aqara protocol and original method didn't work. Still the ports are the same.

dev branch of repository use v2.0 protocol and maybe we can find more information.

from xiaomi_airconditioningcompanion.

syssi commented on August 14, 2024

My AC Companion arrived today. I tried to enable the local network protocol but port 9898 doesn't open:

$ nmap -sU -p 9898 192.168.130.83

Starting Nmap 7.40 ( https://nmap.org ) at 2018-03-17 09:54 CET
Nmap scan report for lumi-acpartner-v1-miio54979480.fritz.box (192.168.130.83)
Host is up (0.077s latency).
PORT     STATE  SERVICE
9898/udp closed monkeycom
MAC Address: 28:6C:07:F0:EC:29 (Xiaomi Electronics,co.)

Nmap done: 1 IP address (1 host up) scanned in 0.61 seconds

If I capture the network traffic no UDP traffic shows up. Could you try the nmap call, too? Are you sure port 9898 is open? (Firmware version 1.41_145)

from xiaomi_airconditioningcompanion.

cxlwill commented on August 14, 2024

I tested it with nmap the result is the same as you. But why did nc work? I'm confused now.

from xiaomi_airconditioningcompanion.

syssi commented on August 14, 2024

Try your "nc" call again and add the parameter "-v". Did you see a "connection refused" this time?

from xiaomi_airconditioningcompanion.

cxlwill commented on August 14, 2024

nc -v -uz 192.168.50.236 9898
found 0 associations
found 1 connections:
     1:	flags=82<CONNECTED,PREFERRED>
	outif (null)
	src 192.168.50.143 port 59004
	dst 192.168.50.236 port 9898
	rank info not available

Connection to 192.168.50.236 port 9898 [udp/monkeycom] succeeded!

from xiaomi_airconditioningcompanion.

syssi commented on August 14, 2024

You are right. I cannot explain the behavior of netcat:

$ nc -h
[v1.10-41+b1]
connect to somewhere:   nc [-options] hostname port[s] [ports] ... 
listen for inbound:     nc -l -p port [-options] [hostname] [port]
options:
        -c shell commands       as `-e'; use /bin/sh to exec [dangerous!!]
        -e filename             program to exec after connect [dangerous!!]
        -b                      allow broadcasts
        -g gateway              source-routing hop point[s], up to 8
        -G num                  source-routing pointer: 4, 8, 12, ...
        -h                      this cruft
        -i secs                 delay interval for lines sent, ports scanned
        -k                      set keepalive option on socket
        -l                      listen mode, for inbound connects
        -n                      numeric-only IP addresses, no DNS
        -o file                 hex dump of traffic
        -p port                 local port number
        -r                      randomize local and remote ports
        -q secs                 quit after EOF on stdin and delay of secs
        -s addr                 local source address
        -T tos                  set Type Of Service
        -t                      answer TELNET negotiation
        -u                      UDP mode
        -v                      verbose [use twice to be more verbose]
        -w secs                 timeout for connects and final net reads
        -C                      Send CRLF as line-ending
        -z                      zero-I/O mode [used for scanning]
port numbers can be individual or ranges: lo-hi [inclusive];
hyphens in port names must be backslash escaped (e.g. 'ftp\-data').

$ nc -v -u 192.168.130.83 9898
lumi-acpartner-v1-miio54979480.fritz.box [192.168.130.83] 9898 (?) open
^C
$ nc -v -uz 192.168.130.83 9898
lumi-acpartner-v1-miio54979480.fritz.box [192.168.130.83] 9898 (?) : Connection refused

from xiaomi_airconditioningcompanion.

cxlwill commented on August 14, 2024

Here's another feedback. Couple of people accessed Gateway function through HA's xiaomi_aqara component successfully with both square(Aqara) and round(Mihome) version with fresh installment of HA. Meanwhile others failed to find a gateway through the same process. Majority of them already pair one gateway in pre-build HA.

I try to debug this problem. Is it generated by pyxiaomigateway's multi-gateway function? Besides the auto-discovery of xiaomi_aqara seems out of discovery: setup's scope? I turn off discovery, and indicate specific IP of AC Companion at xiaomi_aqara part. But HA failed to find it.

BTW, 3rd generation of Aqara AC Companion is out today in mainland of China: https://youpin.mi.com/detail?gid=101229. It comes with relay. I ordered one, so let's hope it can pass the test.

from xiaomi_airconditioningcompanion.

syssi commented on August 14, 2024

Interesting. I will try to reset the device again and sniff the complete network traffic. At the moment the device just don't respond to important requests (whois).

from xiaomi_airconditioningcompanion.

syssi commented on August 14, 2024

Awesome! Could you enable the debug log and provide the output of HA statup:

# configuration.yaml

logger:
  default: warn
  logs:
    xiaomi_gateway: debug
    homeassistant.components.xiaomi_aqara: debug

from xiaomi_airconditioningcompanion.

cxlwill commented on August 14, 2024

2018-03-25 18:40:51 INFO (Thread-9) [xiaomi_gateway] Xiaomi Gateway 7811dcb2a7d9 configured at IP 192.168.50.99:9898
2018-03-25 18:40:51 INFO (Thread-9) [xiaomi_gateway] Discovering Xiaomi Devices
2018-03-25 18:40:51 DEBUG (Thread-9) [xiaomi_gateway] _send_cmd >> b'{"cmd" : "get_id_list"}'
2018-03-25 18:40:51 DEBUG (Thread-9) [xiaomi_gateway] _send_cmd resp << {'params': [{'error': 'No sid'}], 'cmd': 'get_id_list_rsp'}
2018-03-25 18:40:51 ERROR (Thread-9) [xiaomi_gateway] Non matching response. Expecting get_id_list_ack, but got get_id_list_rsp
2018-03-25 18:40:51 INFO (Thread-9) [xiaomi_gateway] Discovering Xiaomi Devices
2018-03-25 18:40:51 DEBUG (Thread-9) [xiaomi_gateway] _send_cmd >> b'{"cmd" : "get_id_list"}'
2018-03-25 18:40:51 DEBUG (Thread-9) [xiaomi_gateway] _send_cmd resp << {'params': [{'error': 'No sid'}], 'cmd': 'get_id_list_rsp'}
2018-03-25 18:40:51 ERROR (Thread-9) [xiaomi_gateway] Non matching response. Expecting get_id_list_ack, but got get_id_list_rsp
2018-03-25 18:40:51 INFO (Thread-9) [xiaomi_gateway] Discovering Xiaomi Devices
2018-03-25 18:40:51 DEBUG (Thread-9) [xiaomi_gateway] _send_cmd >> b'{"cmd" : "get_id_list"}'
2018-03-25 18:40:51 DEBUG (Thread-9) [xiaomi_gateway] _send_cmd resp << {'params': [{'error': 'No sid'}], 'cmd': 'get_id_list_rsp'}
2018-03-25 18:40:51 ERROR (Thread-9) [xiaomi_gateway] Non matching response. Expecting get_id_list_ack, but got get_id_list_rsp
2018-03-25 18:40:51 INFO (Thread-9) [xiaomi_gateway] Discovering Xiaomi Devices
2018-03-25 18:40:51 DEBUG (Thread-9) [xiaomi_gateway] _send_cmd >> b'{"cmd" : "get_id_list"}'
2018-03-25 18:40:51 DEBUG (Thread-9) [xiaomi_gateway] _send_cmd resp << {'params': [{'error': 'No sid'}], 'cmd': 'get_id_list_rsp'}
2018-03-25 18:40:51 ERROR (Thread-9) [xiaomi_gateway] Non matching response. Expecting get_id_list_ack, but got get_id_list_rsp
2018-03-25 18:40:51 INFO (Thread-9) [xiaomi_gateway] Discovering Xiaomi Devices
2018-03-25 18:40:51 DEBUG (Thread-9) [xiaomi_gateway] _send_cmd >> b'{"cmd" : "get_id_list"}'
2018-03-25 18:40:51 DEBUG (Thread-9) [xiaomi_gateway] _send_cmd resp << {'params': [{'error': 'No sid'}], 'cmd': 'get_id_list_rsp'}
2018-03-25 18:40:51 ERROR (Thread-9) [xiaomi_gateway] Non matching response. Expecting get_id_list_ack, but got get_id_list_rsp
2018-03-25 18:40:51 INFO (Thread-9) [xiaomi_gateway] Xiaomi Gateway 34ce00965bf1 configured at IP 192.168.50.236:9898
2018-03-25 18:40:51 INFO (Thread-9) [xiaomi_gateway] Discovering Xiaomi Devices
2018-03-25 18:40:51 DEBUG (Thread-9) [xiaomi_gateway] _send_cmd >> b'{"cmd" : "get_id_list"}'
2018-03-25 18:41:56 DEBUG (Thread-23) [xiaomi_gateway] MCAST (heartbeat) << {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': 'qCuzXTywrLzqaU82', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:41:56 ERROR (Thread-22) [xiaomi_gateway] No data in response from hub {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': 'qCuzXTywrLzqaU82', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:42:06 DEBUG (Thread-23) [xiaomi_gateway] MCAST (heartbeat) << {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': 'PPtndJjZLCwR8rz3', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:42:06 ERROR (Thread-16) [xiaomi_gateway] No data in response from hub {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': 'PPtndJjZLCwR8rz3', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:42:16 DEBUG (Thread-23) [xiaomi_gateway] MCAST (heartbeat) << {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': 'jtx3QXScdNZBcTB3', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:42:16 ERROR (Thread-3) [xiaomi_gateway] No data in response from hub {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': 'jtx3QXScdNZBcTB3', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:42:17 DEBUG (Thread-4) [xiaomi_gateway] _send_cmd >> b'{ "cmd":"read","sid":"158d00019e0f1d"}'
2018-03-25 18:42:26 DEBUG (Thread-23) [xiaomi_gateway] MCAST (heartbeat) << {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': 'upAPAwJX2bF9tATU', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:42:26 ERROR (Thread-20) [xiaomi_gateway] No data in response from hub {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': 'upAPAwJX2bF9tATU', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:42:36 DEBUG (Thread-23) [xiaomi_gateway] MCAST (heartbeat) << {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': 'DUnno5Q6Ch00uVK0', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:42:36 ERROR (Thread-6) [xiaomi_gateway] No data in response from hub {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': 'DUnno5Q6Ch00uVK0', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:42:46 DEBUG (Thread-23) [xiaomi_gateway] MCAST (heartbeat) << {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': 'It3nucmL1dwFzb16', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:42:46 ERROR (Thread-15) [xiaomi_gateway] No data in response from hub {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': 'It3nucmL1dwFzb16', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:42:56 DEBUG (Thread-23) [xiaomi_gateway] MCAST (heartbeat) << {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': 'OBg0pVY0zmh7mU9n', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:42:56 ERROR (Thread-15) [xiaomi_gateway] No data in response from hub {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': 'OBg0pVY0zmh7mU9n', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:43:06 DEBUG (Thread-23) [xiaomi_gateway] MCAST (heartbeat) << {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': '8vEsbbNTCvpjnswl', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:43:06 ERROR (Thread-11) [xiaomi_gateway] No data in response from hub {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': '8vEsbbNTCvpjnswl', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:43:16 DEBUG (Thread-23) [xiaomi_gateway] MCAST (heartbeat) << {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': 'KQ3WHCXPb7giFEar', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:43:16 ERROR (Thread-9) [xiaomi_gateway] No data in response from hub {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': 'KQ3WHCXPb7giFEar', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:43:26 DEBUG (Thread-23) [xiaomi_gateway] MCAST (heartbeat) << {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': 'bcvLEWCFkm7zBMzi', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:43:26 ERROR (Thread-9) [xiaomi_gateway] No data in response from hub {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': 'bcvLEWCFkm7zBMzi', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:43:36 DEBUG (Thread-23) [xiaomi_gateway] MCAST (heartbeat) << {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': '4LSIVwwl9lFeC4Y5', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:43:36 ERROR (Thread-10) [xiaomi_gateway] No data in response from hub {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': '4LSIVwwl9lFeC4Y5', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}
2018-03-25 18:43:46 DEBUG (Thread-23) [xiaomi_gateway] MCAST (heartbeat) << {'model': 'acpartner.v3', 'sid': '7811dcb2a7d9', 'token': 'VC57VJfhMHyzX9oX', 'params': [{'ip': '192.168.50.99'}], 'cmd': 'heartbeat'}

from xiaomi_airconditioningcompanion.

syssi commented on August 14, 2024

Just for completeness:

This is the hardware version of my device (v1):

 'cfg_time': 0,
 'fw_ver': '1.4.1_145',
 'hw_ver': 'MW300',
 'life': 645,
 'mac': '28:6C:07:F0:EC:29',
 'mcu_fw_ver': '0143',
 'mmfree': 172616,
 'model': 'lumi.acpartner.v1',
 'ot': 'otu',
 'ott_stat': [0, 0, 0, 0],
 'otu_stat': [359, 589, 31, 13, 16, 1524],
 'token': 'xxx',
 'wifi_fw_ver': 'SD878x-14.76.36.p84-702.1.0-WM'}

You (@cxlwill) own the lumi.acpartner.v2. Many thanks to @ileler for the support of the v3 at Danielhiversen/PyXiaomiGateway#66.

from xiaomi_airconditioningcompanion.

syssi commented on August 14, 2024

@cxlwill Could you help to identify the device version?

This is my device (v1): https://www.gearbest.com/living-appliances/pp_416094.html
Is this one the v2 version? https://www.gearbest.com/power-strips/pp_640724.html

from xiaomi_airconditioningcompanion.

gsotiriou commented on August 14, 2024

Hello, I too seem to have an old model of acpartner, according to the message above (and since I get no support for it in HA although it's configured) it must be the v2 version. Is there any update on IF and HOW will this be possible to be used as gateway reporting zigbee devices? It's very important for me to be able to use it as gateway since my house is big and has lot's of turns and corners and the other gateway (the lumi one) is not enough on its own. Is there anything I can do or provide or test to help move forward? Thanks!

from xiaomi_airconditioningcompanion.

syssi commented on August 14, 2024

@gsotiriou Bad news. There is no firmware update and it will be easier to buy another hardware revision.

from xiaomi_airconditioningcompanion.

carlyang1986 commented on August 14, 2024

syssi, thank you for your xiaomi_airconditioning plug-in let me access my acpartner.v3 square into HA platform. Further I tried to access its gateway to HA but failed. The xiaomi_aqara told me init error seems HA can't find the gateway although I had write the mac: and key:
As I am only a begginer in HA system. But if your need test the plug or test the function. Please tell me.

from xiaomi_airconditioningcompanion.

carlyang1986 commented on August 14, 2024

Here is the log of HA. I hope it may help you.
2018-11-18 18:51:11 ERROR (MainThread) [homeassistant.setup] Error during setup of component xiaomi_aqara
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/homeassistant/setup.py", line 148, in _async_setup_component
component.setup, hass, processed_config) # type: ignore
AttributeError: module 'custom_components.xiaomi_aqara' has no attribute 'setup'

from xiaomi_airconditioningcompanion.

syssi commented on August 14, 2024

@carlyang1986 Please post your configuration. Why is xiaomi_aqara a custom component in your setup?

from xiaomi_airconditioningcompanion.

carlyang1986 commented on August 14, 2024

@carlyang1986 Please post your configuration. Why is xiaomi_aqara a custom component in your setup?

@syssi

# aqara gateway
xiaomi_aqara:
  discovery_retry: 5
  interface: '192.168.2.124'
  gateways:
    - mac: 7C49EB7FD832  
      key: 8ks9nc3xencmcxdu
      host: 192.168.2.64

# climate
climate:
  - platform: xiaomi_miio
    name: Aqara Air Conditioning Companion
    host: 192.168.2.64
    token: 1f00022473b1ec8f7cd8426c5580e334
    target_sensor: sensor.temperature_158d0001f53706
#    target_sensor: lumi.sensor_ht.v1
    scan_interval: 60

from xiaomi_airconditioningcompanion.

syssi commented on August 14, 2024

What's the content of your custom_components folder?

from xiaomi_airconditioningcompanion.

carlyang1986 commented on August 14, 2024

@syssi
configuration.yaml.txt

from xiaomi_airconditioningcompanion.

carlyang1986 commented on August 14, 2024

@syssi

from xiaomi_airconditioningcompanion.

carlyang1986 commented on August 14, 2024

@syssi
This is my web shot. The acpartner is accessed but gateway is not installed successful.

from xiaomi_airconditioningcompanion.

syssi commented on August 14, 2024

Please clean up your custom_component folder. xiaomi_aqara is an official component of Home Assistant. Remove all xiaomi_aqara.py files.

from xiaomi_airconditioningcompanion.

carlyang1986 commented on August 14, 2024

@syssi
I had deleted the acapartner from my mihome app. I'll try to remove all the files in custom_component folder and retry on weekend.

from xiaomi_airconditioningcompanion.

syssi commented on August 14, 2024

Don't remove all files. This custom component is still needed. The xiaomi_aqara must be removed!

from xiaomi_airconditioningcompanion.

carlyang1986 commented on August 14, 2024

Don't remove all files. This custom component is still needed. The xiaomi_aqara must be removed!

I see, I remember this file xiaomi_aqara is downloaded from github, but i foget where the page is. I will try to remove it first and to find the result in the log file.

from xiaomi_airconditioningcompanion.

carlyang1986 commented on August 14, 2024

Don't remove all files. This custom component is still needed. The xiaomi_aqara must be removed!

I see, I remember this file xiaomi_aqara is downloaded from github, but i foget where the page is. I will try to remove it first and to find the result in the log file.

I'm sorry late to try the fuction. I get new discription in the log file after removing xiaomi_aqara.py from custom component.

2018-11-18 18:51:11 WARNING (MainThread) [homeassistant.loader] You are using a custom component for xiaomi_aqara which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2018-11-18 18:51:11 ERROR (MainThread) [homeassistant.setup] Error during setup of component xiaomi_aqara
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/homeassistant/setup.py", line 148, in _async_setup_component
component.setup, hass, processed_config) # type: ignore
AttributeError: module 'custom_components.xiaomi_aqara' has no attribute 'setup'
2018-11-18 18:51:11 WARNING (MainThread) [homeassistant.loader] You are using a custom component for climate.xiaomi_miio which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2018-11-18 18:51:11 WARNING (MainThread) [homeassistant.loader] You are using a custom component for molohub which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.

from xiaomi_airconditioningcompanion.

carlyang1986 commented on August 14, 2024

I reinstall the homeassistant to make sure its pure in the custom_component without xiaomi_aquara.py or xiaomi.py. I found the following discription during in the hass starting up. It May useful for you.
Discovering Xiaomi Gateways (Try 1) 2018-12-16 07:45:21 INFO (SyncWorker_6) [xiaomi_gateway] Xiaomi Gateway 7c49eb7f d832 configured at IP 192.168.2.64:9898 2018-12-16 07:45:21 INFO (SyncWorker_6) [xiaomi_gateway] Discovering Xiaomi Devi ces 2018-12-16 07:45:21 INFO (SyncWorker_6) [xiaomi_gateway] Found 2 devices

In hass it shows to found 2 devices, but I can't find any devices in my webpage acturally I did access a named xiaomi tempreture and humidity sensor (lumi.sensor_ht.1).

from xiaomi_airconditioningcompanion.

carlyang1986 commented on August 14, 2024

Yes.

hello，I want to know if you had access the Gateway function of lumi.acpartner.v3 into homeassistant. I had configured yaml file. The gateway seems be found in HA, but the zigbee device is not show in the web page. The device is lumi.sensor.ht.v1.

你好墨澜大神，我冒昧的问您一下这个绿米空调伴侣的升级版的网关功能您是否也正常的接入到HA了。我根据官网上的方法写好了yaml的配置文件，通过启动hass的代码发现HA通过9898端口找到了网关和下面的2台设备，其中一台是我的小米温湿度探测器，但是在网页上确没有任何的提示或者显示。我现在运行的设备是chroot环境基于armhf平台的ubuntu 18.04，HA平台是0.84.2最新版。

from xiaomi_airconditioningcompanion.

syssi commented on August 14, 2024

Do you see the devices at the dev-state page?

from xiaomi_airconditioningcompanion.

carlyang1986 commented on August 14, 2024

Do you see the devices at the dev-state page?

No，I don't see anything even the some errors in the log file. In order to confirm if the gateway is found by HA. I run hass manually. I saw the it was detect by HA and 2 devices found. But the sensor.ht.v1(weather and humidity sensor under gateway) is not appear.

from xiaomi_airconditioningcompanion.

carlyang1986 commented on August 14, 2024

Do you see the devices at the dev-state page?

(homeassistant) homeassistant@localhost:/home/abc$ hass
Config directory: /home/homeassistant/.homeassistant
2018-12-17 16:20:43 INFO (MainThread) [homeassistant.loader] Loaded websocket_api from homeassistant.components.websocket_api
2018-12-17 16:20:43 INFO (MainThread) [homeassistant.bootstrap] Home Assistant core initialized
2018-12-17 16:20:44 INFO (MainThread) [homeassistant.loader] Loaded history from custom_components.history
2018-12-17 16:20:44 WARNING (MainThread) [homeassistant.loader] You are using a custom component for history which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2018-12-17 16:20:44 INFO (MainThread) [homeassistant.loader] Loaded recorder from homeassistant.components.recorder
2018-12-17 16:20:44 INFO (MainThread) [homeassistant.loader] Loaded http from homeassistant.components.http
2018-12-17 16:20:44 INFO (MainThread) [homeassistant.loader] Loaded introduction from homeassistant.components.introduction
2018-12-17 16:20:44 INFO (MainThread) [homeassistant.setup] Setting up introduction
2018-12-17 16:20:44 INFO (MainThread) [homeassistant.components.introduction]

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    Hello, and welcome to Home Assistant!

    We'll hope that we can make all your dreams come true.

    Here are some resources to get started:

     - Configuring Home Assistant:
       https://home-assistant.io/getting-started/configuration/

     - Available components:
       https://home-assistant.io/components/

     - Troubleshooting your configuration:
       https://home-assistant.io/getting-started/troubleshooting-configuration/

     - Getting help:
       https://home-assistant.io/help/

    This message is generated by the introduction component. You can
    disable it in configuration.yaml.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2018-12-17 16:20:44 INFO (MainThread) [homeassistant.loader] Loaded persistent_notification from homeassistant.components.persistent_notification
2018-12-17 16:20:44 INFO (MainThread) [homeassistant.setup] Setup of domain introduction took 0.0 seconds.
2018-12-17 16:20:44 INFO (MainThread) [homeassistant.loader] Loaded frontend from homeassistant.components.frontend
2018-12-17 16:20:44 INFO (MainThread) [homeassistant.loader] Loaded api from homeassistant.components.api
2018-12-17 16:20:44 INFO (MainThread) [homeassistant.loader] Loaded system_log from homeassistant.components.system_log
2018-12-17 16:20:45 INFO (MainThread) [homeassistant.loader] Loaded auth from homeassistant.components.auth
2018-12-17 16:20:45 INFO (MainThread) [homeassistant.loader] Loaded onboarding from homeassistant.components.onboarding
2018-12-17 16:20:45 INFO (MainThread) [homeassistant.loader] Loaded lovelace from homeassistant.components.lovelace
2018-12-17 16:20:45 INFO (MainThread) [homeassistant.setup] Setting up http
2018-12-17 16:20:45 INFO (MainThread) [homeassistant.setup] Setup of domain http took 0.1 seconds.
2018-12-17 16:20:45 INFO (MainThread) [homeassistant.setup] Setting up recorder
2018-12-17 16:20:45 INFO (MainThread) [homeassistant.setup] Setting up lovelace
2018-12-17 16:20:45 INFO (MainThread) [homeassistant.setup] Setup of domain lovelace took 0.0 seconds.
2018-12-17 16:20:45 INFO (MainThread) [homeassistant.setup] Setting up api
2018-12-17 16:20:45 INFO (MainThread) [homeassistant.setup] Setting up websocket_api
2018-12-17 16:20:45 INFO (MainThread) [homeassistant.setup] Setup of domain websocket_api took 0.0 seconds.
2018-12-17 16:20:45 INFO (MainThread) [homeassistant.setup] Setting up system_log
2018-12-17 16:20:45 INFO (MainThread) [homeassistant.setup] Setup of domain system_log took 0.0 seconds.
2018-12-17 16:20:45 INFO (MainThread) [homeassistant.setup] Setting up auth
2018-12-17 16:20:45 INFO (MainThread) [homeassistant.setup] Setup of domain auth took 0.0 seconds.
2018-12-17 16:20:45 INFO (MainThread) [homeassistant.setup] Setting up onboarding
2018-12-17 16:20:45 INFO (MainThread) [homeassistant.setup] Setup of domain api took 0.1 seconds.
2018-12-17 16:20:45 INFO (MainThread) [homeassistant.setup] Setup of domain onboarding took 0.0 seconds.
2018-12-17 16:20:45 INFO (MainThread) [homeassistant.setup] Setting up frontend
2018-12-17 16:20:50 WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=43 from 2018-12-17 05:19:41.987693)
2018-12-17 16:20:52 INFO (MainThread) [homeassistant.setup] Setup of domain frontend took 6.7 seconds.
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.setup] Setup of domain recorder took 7.8 seconds.
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.setup] Setting up history
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.setup] Setup of domain history took 0.0 seconds.
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.loader] Loaded discovery from homeassistant.components.discovery
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.setup] Setting up discovery
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.setup] Setup of domain discovery took 0.3 seconds.
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.loader] Loaded conversation from homeassistant.components.conversation
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.loader] Loaded automation from homeassistant.components.automation
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.loader] Loaded group from homeassistant.components.group
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.loader] Loaded map from homeassistant.components.map
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.setup] Setting up map
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.setup] Setup of domain map took 0.0 seconds.
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.loader] Loaded tts from homeassistant.components.tts
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.loader] Loaded tts.google from homeassistant.components.tts.google
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.loader] Loaded updater from homeassistant.components.updater
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.setup] Setting up updater
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.loader] Loaded xiaomi_aqara from homeassistant.components.xiaomi_aqara
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.setup] Setting up xiaomi_aqara
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.loader] Loaded switch from homeassistant.components.switch
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.loader] Loaded switch.xiaomi_miio from homeassistant.components.switch.xiaomi_miio
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.setup] Setting up group
2018-12-17 16:20:53 INFO (MainThread) [homeassistant.setup] Setup of domain group took 0.0 seconds.
2018-12-17 16:20:54 INFO (MainThread) [homeassistant.loader] Loaded logbook from homeassistant.components.logbook
2018-12-17 16:20:54 INFO (MainThread) [homeassistant.loader] Loaded climate from homeassistant.components.climate
2018-12-17 16:20:54 INFO (MainThread) [homeassistant.loader] Loaded climate.xiaomi_miio from custom_components.climate.xiaomi_miio
2018-12-17 16:20:54 WARNING (MainThread) [homeassistant.loader] You are using a custom component for climate.xiaomi_miio which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2018-12-17 16:20:54 INFO (MainThread) [homeassistant.setup] Setting up climate
2018-12-17 16:20:54 INFO (MainThread) [homeassistant.loader] Loaded sun from homeassistant.components.sun
2018-12-17 16:20:54 INFO (MainThread) [homeassistant.setup] Setting up sun
2018-12-17 16:20:54 INFO (MainThread) [homeassistant.setup] Setup of domain sun took 0.1 seconds.
2018-12-17 16:20:54 INFO (MainThread) [homeassistant.loader] Loaded cloud from homeassistant.components.cloud
2018-12-17 16:20:54 INFO (MainThread) [homeassistant.loader] Loaded config from homeassistant.components.config
2018-12-17 16:20:54 INFO (MainThread) [homeassistant.loader] Loaded fan from homeassistant.components.fan
2018-12-17 16:20:54 INFO (MainThread) [homeassistant.loader] Loaded fan.xiaomi_miio from homeassistant.components.fan.xiaomi_miio
2018-12-17 16:20:54 INFO (MainThread) [homeassistant.loader] Loaded camera from homeassistant.components.camera
2018-12-17 16:20:54 INFO (MainThread) [homeassistant.loader] Loaded camera.ffmpeg from homeassistant.components.camera.ffmpeg
2018-12-17 16:20:54 INFO (MainThread) [homeassistant.loader] Loaded script from homeassistant.components.script
2018-12-17 16:20:54 INFO (MainThread) [homeassistant.loader] Loaded molohub from custom_components.molohub
2018-12-17 16:20:54 WARNING (MainThread) [homeassistant.loader] You are using a custom component for molohub which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2018-12-17 16:20:54 INFO (MainThread) [homeassistant.setup] Setting up molohub
2018-12-17 16:20:54 INFO (SyncWorker_7) [custom_components.molohub] Begin setup molohub!
2018-12-17 16:20:54 INFO (MainThread) [homeassistant.loader] Loaded sensor from homeassistant.components.sensor
2018-12-17 16:20:54 INFO (MainThread) [homeassistant.loader] Loaded sensor.yr from homeassistant.components.sensor.yr
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.setup] Setting up sensor
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.loader] Loaded ffmpeg from homeassistant.components.ffmpeg
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.setup] Setting up ffmpeg
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.setup] Setup of domain ffmpeg took 0.0 seconds.
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.yr
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.setup] Setup of domain updater took 1.4 seconds.
### 2018-12-17 16:20:55 INFO (SyncWorker_3) [homeassistant.components.xiaomi_aqara] Discovering Xiaomi Gateways (Try 1)
2018-12-17 16:20:55 INFO (SyncWorker_3) [xiaomi_gateway] Xiaomi Gateway 7c49eb7fd832 found at IP 192.168.2.64
2018-12-17 16:20:55 INFO (SyncWorker_3) [xiaomi_gateway] Discovering Xiaomi Devices
2018-12-17 16:20:55 INFO (SyncWorker_3) [xiaomi_gateway] Found 2 devices
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.setup] Setting up conversation
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.setup] Setup of domain conversation took 0.1 seconds.
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.setup] Setting up automation
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.setup] Setup of domain automation took 0.0 seconds.
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.setup] Setting up tts
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.setup] Setting up switch
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.setup] Setting up logbook
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.setup] Setup of domain logbook took 0.0 seconds.
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.setup] Setting up cloud
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.setup] Setup of domain cloud took 0.0 seconds.
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.setup] Setting up config
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.setup] Setting up fan
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.setup] Setting up camera
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.setup] Setting up script
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.setup] Setup of domain script took 0.0 seconds.
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.components.switch] Setting up switch.xiaomi_miio
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.loader] Loaded config.core from homeassistant.components.config.core
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.loader] Loaded config.script from homeassistant.components.config.script
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.loader] Loaded config.automation from homeassistant.components.config.automation
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.loader] Loaded config.customize from homeassistant.components.config.customize
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.loader] Loaded config.group from homeassistant.components.config.group
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.loader] Loaded config.hassbian from homeassistant.components.config.hassbian
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.loader] Loaded config.config_entries from homeassistant.components.config.config_entries
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.loader] Loaded config.auth from homeassistant.components.config.auth
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.loader] Loaded config.auth_provider_homeassistant from homeassistant.components.config.auth_provider_homeassistant
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.loader] Loaded config.device_registry from homeassistant.components.config.device_registry
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.loader] Loaded config.entity_registry from homeassistant.components.config.entity_registry
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.components.fan] Setting up fan.xiaomi_miio
2018-12-17 16:20:55 INFO (MainThread) [homeassistant.setup] Setup of domain molohub took 1.0 seconds.
2018-12-17 16:20:57 INFO (MainThread) [homeassistant.components.switch.xiaomi_miio] Initializing with host 192.168.2.37 (token a575f...)
2018-12-17 16:20:57 INFO (MainThread) [homeassistant.components.switch.xiaomi_miio] qmi.powerstrip.v1 3.4.2_79 RTL8711AF detected
2018-12-17 16:20:58 INFO (MainThread) [homeassistant.components.fan.xiaomi_miio] Initializing with host 192.168.2.219 (token b3a79...)
2018-12-17 16:20:58 INFO (MainThread) [homeassistant.components.fan.xiaomi_miio] zhimi.airpurifier.v3 1.4.0 MC200 detected
2018-12-17 16:20:58 INFO (MainThread) [homeassistant.components.camera] Setting up camera.ffmpeg
2018-12-17 16:20:58 INFO (MainThread) [homeassistant.setup] Setup of domain config took 2.5 seconds.
2018-12-17 16:20:58 INFO (MainThread) [homeassistant.setup] Setup of domain tts took 2.6 seconds.
2018-12-17 16:20:58 INFO (MainThread) [homeassistant.setup] Setup of domain camera took 2.6 seconds.
2018-12-17 16:21:00 INFO (SyncWorker_3) [xiaomi_gateway] Gateway discovery finished in 5 seconds
2018-12-17 16:21:00 INFO (SyncWorker_3) [xiaomi_gateway] Creating Multicast Socket
2018-12-17 16:21:00 INFO (Thread-3) [custom_components.molohub] moloserver reconnecting...
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.loader] Loaded binary_sensor from homeassistant.components.binary_sensor
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.setup] Setting up binary_sensor
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.setup] Setup of domain binary_sensor took 0.0 seconds.
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.loader] Loaded light from homeassistant.components.light
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.loader] Loaded cover from homeassistant.components.cover
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.loader] Loaded lock from homeassistant.components.lock
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.loader] Loaded binary_sensor.xiaomi_aqara from homeassistant.components.binary_sensor.xiaomi_aqara
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.xiaomi_aqara
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.setup] Setting up light
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.setup] Setting up cover
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.setup] Setup of domain cover took 0.0 seconds.
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.setup] Setting up lock
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.setup] Setup of domain lock took 0.0 seconds.
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.setup] Setup of domain light took 0.1 seconds.
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.setup] Setup of domain sensor took 5.7 seconds.
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.loader] Loaded cover.xiaomi_aqara from homeassistant.components.cover.xiaomi_aqara
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.components.cover] Setting up cover.xiaomi_aqara
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.loader] Loaded lock.xiaomi_aqara from homeassistant.components.lock.xiaomi_aqara
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.components.lock] Setting up lock.xiaomi_aqara
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.loader] Loaded light.xiaomi_aqara from homeassistant.components.light.xiaomi_aqara
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.components.light] Setting up light.xiaomi_aqara
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.components.climate] Setting up climate.xiaomi_miio
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.loader] Loaded sensor.xiaomi_aqara from homeassistant.components.sensor.xiaomi_aqara
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.xiaomi_aqara
2018-12-17 16:21:00 INFO (MainThread) [custom_components.climate.xiaomi_miio] Initializing with host 192.168.2.64 (token 643c6...)
2018-12-17 16:21:00 INFO (MainThread) [custom_components.climate.xiaomi_miio] lumi.acpartner.v3 1.4.1_155 MW300 detected
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.setup] Setup of domain xiaomi_aqara took 7.0 seconds.
2018-12-17 16:21:00 INFO (MainThread) [homeassistant.setup] Setup of domain climate took 6.7 seconds.
2018-12-17 16:21:03 INFO (MainThread) [homeassistant.setup] Setup of domain switch took 8.0 seconds.
2018-12-17 16:21:03 INFO (MainThread) [homeassistant.loader] Loaded switch.xiaomi_aqara from homeassistant.components.switch.xiaomi_aqara
2018-12-17 16:21:03 INFO (MainThread) [homeassistant.components.switch] Setting up switch.xiaomi_aqara
2018-12-17 16:21:04 INFO (MainThread) [homeassistant.setup] Setup of domain fan took 8.7 seconds.
2018-12-17 16:21:04 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 21.52s
2018-12-17 16:21:04 INFO (MainThread) [homeassistant.core] Starting Home Assistant
2018-12-17 16:21:04 INFO (MainThread) [homeassistant.core] Timer:starting
2018-12-17 16:21:04 ERROR (MainThread) [homeassistant.components.http] Failed to create HTTP server at port 8123: [Errno 98] error while attempting to bind on address ('0.0.0.0', 8123): address already in use
2018-12-17 16:21:05 INFO (Thread-3) [custom_components.molohub] moloserver reconnecting...
2018-12-17 16:21:05 INFO (Thread-3) [custom_components.molohub] server online, wait for authorize
2018-12-17 16:21:33 INFO (MainThread) [homeassistant.components.discovery] Unknown service discovered: igd {'host': '192.168.2.1', 'port': 38157, 'ssdp_description': 'http://192.168.2.1:38157/rootDesc.xml', 'name': 'ASUS RT-AC54U Wireless Router', 'model_name': 'Wireless Router', 'model_number': 'RT-AC54U', 'serial': '1.0', 'manufacturer': 'ASUSTek Computer Inc.', 'udn': 'uuid:75802409-bccb-40e7-8e6c-cc81da5e64b9', 'upnp_device_type': 'urn:schemas-upnp-org:device:InternetGatewayDevice:1'}

Here are my whole message during hass start. I made the gateway massage in BIG text. I guess the sensor.ht.v1 and another one (maybe gateway) is not setup correct by HA. I reinstall the system to ubuntu 18.04 and only install climate and molohub packages in custom_components.

In the configuration.yaml I tried this two kinds of words, but get the same result.

from xiaomi_airconditioningcompanion.

syssi commented on August 14, 2024

Please provide a screenshot of the dev-state page!

from xiaomi_airconditioningcompanion.

carlyang1986 commented on August 14, 2024

This is my device state, I don't know wether the screenshot is right. Actrually, I can't find lumi.sensor.ht.v1 and the gateway of acpartner.v3.

from xiaomi_airconditioningcompanion.

syssi commented on August 14, 2024

All entities with 158d000202827c in the entity name belongs to your lumi.sensor.ht.v1.

from xiaomi_airconditioningcompanion.

carlyang1986 commented on August 14, 2024

thank you i found it

from xiaomi_airconditioningcompanion.

syssi commented on August 14, 2024

I close this issue because it's out of scope of this custom component and somehow xiaomi_aqara related.

from xiaomi_airconditioningcompanion.

Gateway function support about xiaomi_airconditioningcompanion HOT 45 CLOSED

Comments (45)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent