broadlink_ac_mqtt
broadlink_ac_mqtt copied to clipboard
Can not connect to device or discover
Hi team, First of all thanks for the great work you did and keep doing!!! I am trying to control my AC (TOP-INV-140 X ׂ(WIFI)), however i am getting following errors
python3 ./monitor.py -d
Starting Monitor...
something went wrong, no devices found
Stopping
Then:
2022-01-04 22:47:47,234,234 DEBUG [monitor.py:284] /home/paveld/projects/broadlink_ac_mqtt/./monitor.py v1.1.0 is starting up
2022-01-04 22:47:47,234,234 DEBUG [monitor.py:286] Loglevel set to DEBUG
2022-01-04 22:47:47,237,237 DEBUG [monitor.py:138] Checking if already running
2022-01-04 22:47:47,237,237 INFO [monitor.py:342] Starting Monitor...
2022-01-04 22:47:47,237,237 DEBUG [monitor.py:344] Starting mainloop, responding on only events
2022-01-04 22:47:47,237,237 DEBUG [AcToMqtt.py:301] Coneccting to MQTT: 192.168.28.254 with client ID = ac_to_mqtt
2022-01-04 22:47:47,239,239 DEBUG [AcToMqtt.py:490] Mqtt connected! client=<paho.mqtt.client.Client object at 0x7f4d971fd4e0>, userdata=None, flags={'session present': 0}, rc=0
2022-01-04 22:47:47,239,239 DEBUG [AcToMqtt.py:495] Listing on /aircon/+/+/set for messages
2022-01-04 22:47:47,239,239 DEBUG [AcToMqtt.py:272] publishing on topic "/aircon/LWT", data "online"
2022-01-04 22:47:49,264,264 DEBUG [AcToMqtt.py:490] Mqtt connected! client=<paho.mqtt.client.Client object at 0x7f4d971fd4e0>, userdata=None, flags={'session present': 0}, rc=0
2022-01-04 22:47:49,265,265 DEBUG [AcToMqtt.py:495] Listing on /aircon/+/+/set for messages
2022-01-04 22:47:49,265,265 DEBUG [AcToMqtt.py:272] publishing on topic "/aircon/LWT", data "online"
2022-01-04 22:47:51,272,272 DEBUG [AcToMqtt.py:490] Mqtt connected! client=<paho.mqtt.client.Client object at 0x7f4d971fd4e0>, userdata=None, flags={'session present': 0}, rc=0
2022-01-04 22:47:51,273,273 DEBUG [AcToMqtt.py:495] Listing on /aircon/+/+/set for messages
2022-01-04 22:47:51,273,273 DEBUG [AcToMqtt.py:272] publishing on topic "/aircon/LWT", data "online"
python3 ./monitor.py -S
No devices found, make sure you are on same network broadcast segment as device/s
cat config.yml
service:
daemon_mode: True
update_interval: 10
self_discovery: True
bind_to_ip: False
mqtt:
host: 192.168.28.254
port: 1883
client_id: ac_to_mqtt
# user: koos
# passwd: koos_se_password
topic_prefix: /aircon
auto_discovery_topic: homeassistant
auto_discovery_topic_retain: False
discovery: False
##Devices
devices:
- ip: 192.168.28.131
mac: 24XXXXXXXXf6
name: mamad
port: 80
What am i missing? The wifi module is wt1hb12
Hi,
If you do auto discover, does it pick up the device? (its one of the command line options to dump the config)
From: Pavel Druyan @.> Sent: Tuesday, 04 January 2022 22:54 To: liaan/broadlink_ac_mqtt @.> Cc: Subscribed @.***> Subject: [liaan/broadlink_ac_mqtt] Can not connect to device or discover (Issue #89)
Hi team, First of all thanks for the great work you did and keep doing!!! I am trying to control my AC (TOP-INV-140 X ׂ(WIFI)), however i am getting following errors
python3 ./monitor.py -d
Starting Monitor...
something went wrong, no devices found
Stopping
Then:
2022-01-04 22:47:47,234,234 DEBUG [monitor.py:284] /home/paveld/projects/broadlink_ac_mqtt/./monitor.py v1.1.0 is starting up
2022-01-04 22:47:47,234,234 DEBUG [monitor.py:286] Loglevel set to DEBUG
2022-01-04 22:47:47,237,237 DEBUG [monitor.py:138] Checking if already running
2022-01-04 22:47:47,237,237 INFO [monitor.py:342] Starting Monitor...
2022-01-04 22:47:47,237,237 DEBUG [monitor.py:344] Starting mainloop, responding on only events
2022-01-04 22:47:47,237,237 DEBUG [AcToMqtt.py:301] Coneccting to MQTT: 192.168.28.254 with client ID = ac_to_mqtt
2022-01-04 22:47:47,239,239 DEBUG [AcToMqtt.py:490] Mqtt connected! client=<paho.mqtt.client.Client object at 0x7f4d971fd4e0>, userdata=None, flags={'session present': 0}, rc=0
2022-01-04 22:47:47,239,239 DEBUG [AcToMqtt.py:495] Listing on /aircon/+/+/set for messages
2022-01-04 22:47:47,239,239 DEBUG [AcToMqtt.py:272] publishing on topic "/aircon/LWT", data "online"
2022-01-04 22:47:49,264,264 DEBUG [AcToMqtt.py:490] Mqtt connected! client=<paho.mqtt.client.Client object at 0x7f4d971fd4e0>, userdata=None, flags={'session present': 0}, rc=0
2022-01-04 22:47:49,265,265 DEBUG [AcToMqtt.py:495] Listing on /aircon/+/+/set for messages
2022-01-04 22:47:49,265,265 DEBUG [AcToMqtt.py:272] publishing on topic "/aircon/LWT", data "online"
2022-01-04 22:47:51,272,272 DEBUG [AcToMqtt.py:490] Mqtt connected! client=<paho.mqtt.client.Client object at 0x7f4d971fd4e0>, userdata=None, flags={'session present': 0}, rc=0
2022-01-04 22:47:51,273,273 DEBUG [AcToMqtt.py:495] Listing on /aircon/+/+/set for messages
2022-01-04 22:47:51,273,273 DEBUG [AcToMqtt.py:272] publishing on topic "/aircon/LWT", data "online"
python3 ./monitor.py -S
No devices found, make sure you are on same network broadcast segment as device/s
service:
daemon_mode: True
update_interval: 10
self_discovery: True
bind_to_ip: False
mqtt:
host: 192.168.28.254
port: 1883
client_id: ac_to_mqtt
# user: koos
# passwd: koos_se_password
topic_prefix: /aircon
auto_discovery_topic: homeassistant
auto_discovery_topic_retain: False
discovery: False
##Devices
devices:
-
ip: 192.168.28.131
mac: 24XXXXXXXXf6
name: mamad
port: 80
What am i missing?
— Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fliaan%2Fbroadlink_ac_mqtt%2Fissues%2F89&data=04%7C01%7C%7C741d0376628b478b0a0c08d9cfc46552%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637769264698435488%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=mpPePv7ZuXWTZn0YUkUiWgXSQANSPPQ92%2FQ584XqwCA%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAGTCXYG5OQP6ICDRAPNM6TUUNNADANCNFSM5LIK4UAQ&data=04%7C01%7C%7C741d0376628b478b0a0c08d9cfc46552%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637769264698435488%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=cs4j7JGvleVSXcPpepfMChqql1LBy562mqBZgV1dHMI%3D&reserved=0. Triage notifications on the go with GitHub Mobile for iOShttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04%7C01%7C%7C741d0376628b478b0a0c08d9cfc46552%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637769264698435488%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=vwI9qsQEdMwN3jXoskPGXBv%2BtO55fu1ZHrBQ%2BGwbyP4%3D&reserved=0 or Androidhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04%7C01%7C%7C741d0376628b478b0a0c08d9cfc46552%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637769264698435488%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=fHzQ7X1mVe%2BjiWpJo%2BamKCREVCSAzloPKlKaSz%2FfLm0%3D&reserved=0. You are receiving this because you are subscribed to this thread.Message ID: @.@.>>
@liaan Thanks for looking into it. Yes tried it as well...
./monitor.py -S
No devices found, make sure you are on same network broadcast segment as device/s
Does ACfreedom pickup the device?
From: Pavel Druyan @.> Sent: Thursday, 06 January 2022 10:32 AM To: liaan/broadlink_ac_mqtt @.> Cc: Karman de Lange @.>; Mention @.> Subject: Re: [liaan/broadlink_ac_mqtt] Can not connect to device or discover (Issue #89)
@liaanhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fliaan&data=04%7C01%7C%7Ce6239fbe67804318b5c108d9d0ef0a8d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637770547364235028%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2BAwe61BAnO4cMqZNU4M%2BFzVb5P2Yx4mponxyonVo6PI%3D&reserved=0 Thanks for looking into it. Yes tried it as well...
./monitor.py -S
No devices found, make sure you are on same network broadcast segment as device/s
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fliaan%2Fbroadlink_ac_mqtt%2Fissues%2F89%23issuecomment-1006374394&data=04%7C01%7C%7Ce6239fbe67804318b5c108d9d0ef0a8d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637770547364235028%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ZjxN8WrGWO65JcvYZ89NN61nUtYYhngquBRRvbG8wXI%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAGTCXY2ALMOKRLRYXBCLNLUUVHQ3ANCNFSM5LIK4UAQ&data=04%7C01%7C%7Ce6239fbe67804318b5c108d9d0ef0a8d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637770547364235028%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=h0SeJzN21A%2FGlXYJKzB7BRM3BdbuenvBCkjQ7ywh0vw%3D&reserved=0. Triage notifications on the go with GitHub Mobile for iOShttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04%7C01%7C%7Ce6239fbe67804318b5c108d9d0ef0a8d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637770547364235028%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=LPcpHS8uZVqtC9dT9W725srvofbKcd4aRjA%2BN1d0Fw8%3D&reserved=0 or Androidhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04%7C01%7C%7Ce6239fbe67804318b5c108d9d0ef0a8d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637770547364235028%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=5zmx7ZkwLz%2FBrg824S%2BPURV8zGy24GWU3OMBh%2BYWCO0%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.@.>>
Yeap
The whole 7 :)