search

bilan / connectlife-api-connector

Connectlife API proxy / MQTT Home Assistant integration
67 stars 17 forks source link

Is this supposed to automatically add devices through MQTT? #3

Closed andy2002a closed 7 months ago

andy2002a commented 7 months ago

I have this config:

connectlife_login: <email>
connectlife_password: <pw>
disable_http_api: false
mqtt_host: 192.168.1.10
mqtt_user: <user>
mqtt_password: <pw>
mqtt_port: 1883
mqtt_ssl: false
-----------------------------------------------------------
 Add-on: Connectlife API proxy / MQTT Add-on
 Integrates Connectlife AC devices with Home Assistant via MQTT and provides an HTTP API
-----------------------------------------------------------
 Add-on version: 1.0.11
 You are running the latest version of this add-on.
 System: Home Assistant OS 11.5  (amd64 / qemux86-64)
 Home Assistant Core: 2024.2.1
 Home Assistant Supervisor: 2024.01.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------

But It doesn't seem to do anything.

The MQTT log shows this:

2024-02-10 17:23:06: New connection from 172.30.32.1:55404 on port 1883.
2024-02-10 17:23:06: New client connected from 172.30.32.1:55404 as connectlife-api (p1, c0, k10, u'<user>').

Also seeing this in the add-on logs

2024-02-10 17:22:31,819 INFO supervisord started with pid 198
2024-02-10 17:22:32,821 INFO spawned: 'mqtt' with pid 199
2024-02-10 17:22:32,823 INFO spawned: 'www' with pid 200

   INFO  Server running on [http://0.0.0.0:8000].  

  Press Ctrl+C to stop the server

2024-02-10 17:22:34,442 INFO success: mqtt entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-02-10 17:22:34,442 INFO success: www entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

In PendingRequest.php line 926:

  cURL error 28: Operation timed out after 30002 milliseconds with 0 bytes re  
  ceived (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https:/  
  /api.connectlife.io/api/v1/appliance                                         

In CurlFactory.php line 210:

  cURL error 28: Operation timed out after 30002 milliseconds with 0 bytes re  
  ceived (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https:/  
  /api.connectlife.io/api/v1/appliance                                         

2024-02-10 17:23:05,092 WARN exited: mqtt (exit status 1; not expected)
2024-02-10 17:23:06,095 INFO spawned: 'mqtt' with pid 206
2024-02-10 17:23:07,097 INFO success: mqtt entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Home Assistant discovery created.
Home Assistant subscribes created.
bilan commented 7 months ago

Yes, it will auto add devices to your ha but you have connection problem. There is time out on connection from your network to ConnectLife api:

https://api.connectlife.io/api/v1/appliance

andy2002a commented 7 months ago

Yes, it will auto add devices to your ha but you have connection problem. There is time out on connection from your network to ConnectLife api:

https://api.connectlife.io/api/v1/appliance

it seems to work fine in the console of the server, at least when running the curl command.

image

bilan commented 7 months ago

Maybe 30s timeout is too short for your case?I will need your connectlife credentails to debug it.

andy2002a commented 7 months ago

I waited a few days and I'm no longer getting those errors, but still not seeing any devices on MQTT:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------

 Add-on: Connectlife API proxy / MQTT Add-on
 Integrates Connectlife AC devices with Home Assistant via MQTT and provides an HTTP API
-----------------------------------------------------------
 Add-on version: 1.0.12
 You are running the latest version of this add-on.
 System: Home Assistant OS 11.5  (amd64 / qemux86-64)
 Home Assistant Core: 2024.2.1
 Home Assistant Supervisor: 2024.01.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
Log level is set to INFO
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
Config OK
MQTT creds: 192.168.1.10 / <user> / 1883 / no-ssl
2024-02-12 11:14:31,428 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2024-02-12 11:14:31,431 INFO supervisord started with pid 202
2024-02-12 11:14:32,433 INFO spawned: 'mqtt' with pid 203
2024-02-12 11:14:32,435 INFO spawned: 'www' with pid 204

   INFO  Server running on [http://0.0.0.0:8000].  

  Press Ctrl+C to stop the server

2024-02-12 11:14:34,051 INFO success: mqtt entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-02-12 11:14:34,051 INFO success: www entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Home Assistant discovery created.
Home Assistant subscribes created.
bilan commented 7 months ago

Are your Connectlife devices in Online state? Are your devices Air Conditioner?

andy2002a commented 7 months ago

Yes, and I can manually interact with the API through curl.

image

andy2002a commented 7 months ago

Maybe this needs to be expanded to include "WindowAirConditioner"?

image

image

image

bilan commented 7 months ago

Yes, that's the reason. This is different device with different properties. I will think about it but it will be hard to not make an error without your ConnectLife credentials.

IzzyEvelynFox commented 7 months ago

I seem to have the same problem, my AC device type is "MobileAirConditioner" instead of "AirConditioner".

image

Here's its properties from the API: response_1707775183350.json

I can send you the login / password if you need it for debugging!

seayworld commented 7 months ago

I have the same as well:


[
  {
    "id": "8650051000200030003000000c6e1c5cc1a6-8650051000200030003000000c6e1c5cc1a6",
    "name": "Portable air conditioner",
    "type": "MobileAirConditioner",
    "status": "Online"
  }
]```
andy2002a commented 7 months ago

I seem to have the same problem, my AC device type is "MobileAirConditioner" instead of "AirConditioner". image

Here's its properties from the API: response_1707775183350.json

I can send you the login / password if you need it for debugging!

Response for mine:

[
  {
    "id": "<ID>",
    "supportsSettingPropertiesInSequence": false,
    "propertyMetadata": [
      {
        "key": "CurrentTemperature",
        "description": "Current Temperature",
        "readWriteMode": "Read",
        "type": "Temperature",
        "minValue": "0",
        "maxValue": "99",
        "step": "1",
        "minValueCelsius": "0",
        "maxValueCelsius": "37",
        "minValueFahrenheit": "0",
        "maxValueFahrenheit": "99",
        "unitPropertyKey": "TemperatureUnit"
      },
      {
        "key": "FanSpeed",
        "description": "Fan Speed",
        "readWriteMode": "ReadWrite",
        "type": "Enum",
        "enumValues": {
          "2": {
            "key": "Low",
            "label": "Low"
          },
          "3": {
            "key": "Medium",
            "label": "Medium"
          },
          "4": {
            "key": "High",
            "label": "High"
          }
        }
      },
      {
        "key": "Mode",
        "description": "Mode",
        "readWriteMode": "ReadWrite",
        "type": "Enum",
        "enumValues": {
          "0": {
            "key": "Fan only",
            "label": "Fan only"
          },
          "2": {
            "key": "Heat",
            "label": "Heat"
          },
          "3": {
            "key": "Cool",
            "label": "Cool"
          },
          "5": {
            "key": "Dry",
            "label": "Dry"
          }
        }
      },
      {
        "key": "Power",
        "description": "Power",
        "readWriteMode": "ReadWrite",
        "type": "Boolean"
      },
      {
        "key": "SetTemperature",
        "description": "Set Temperature",
        "readWriteMode": "ReadWrite",
        "type": "Temperature",
        "minValue": "16",
        "maxValue": "90",
        "step": "1",
        "minValueCelsius": "16",
        "maxValueCelsius": "32",
        "minValueFahrenheit": "61",
        "maxValueFahrenheit": "90",
        "unitPropertyKey": "TemperatureUnit"
      },
      {
        "key": "TemperatureUnit",
        "description": "Temperature Unit",
        "readWriteMode": "ReadWrite",
        "type": "Enum",
        "enumValues": {
          "0": {
            "key": "°C",
            "label": "Celsius degree"
          },
          "1": {
            "key": "°F",
            "label": "Fahrenheit degree"
          }
        }
      }
    ]
  }
]
bilan commented 7 months ago

@IzzyEvelynFox @andy2002a , update to v1.1.0, this version should support your ac device.

andy2002a commented 7 months ago

@IzzyEvelynFox @andy2002a , update to v1.1.0, this version should support your ac device.

Thanks! It's showing up correctly now.

It looks loke the API has a bug where the mode numbers do not line up with the actual mode of the AC.

At least for my unit the correct ones are:

self.systemModes = {'Fan only': '0', 'Heat': '1', 'Cool': '2', 'Dry': '3'}

Not sure if other ones have this issue

djm193 commented 7 months ago

My devices will also not show up via autodiscover. when I configure my split aircon in ConnectLife app I have to choose „geteilte Klimaanlage“ or „split airconditioner“. Where can I look up if I have the same problem as the unseres above?

s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service base-addon-banner: starting

Add-on: Connectlife API proxy / MQTT Add-on Integrates Connectlife AC devices with Home Assistant via MQTT and provides an HTTP API

Add-on version: 1.1.0 You are running the latest version of this add-on. System: Home Assistant OS 11.5 (aarch64 / raspberrypi4-64) Home Assistant Core: 2024.2.2 Home Assistant Supervisor: 2024.01.1

Please, share the above information when looking for help or support in, e.g., GitHub, forums or the Discord chat.

s6-rc: info: service base-addon-banner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service base-addon-log-level: starting s6-rc: info: service fix-attrs successfully started Log level is set to DEBUG s6-rc: info: service base-addon-log-level successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started [21:40:46] DEBUG: Requested API resource: http://supervisor/services/mqtt [21:40:46] DEBUG: Request method: GET [21:40:46] DEBUG: Request data: {} [21:40:46] DEBUG: API HTTP Response code: 200 [21:40:46] DEBUG: API Response: {"result":"ok","data":{"host":"core-mosquitto","port":1883,"ssl":false,"protocol":"3.1.1","username":"addons","password":"aei1EGhe3ph","addon":"core_mosquitto"}}

Config OK MQTT creds: core-mosquitto / addons / 1883 / no-ssl HTTP API disabled, running MQTT client only. Home Assistant discovery created. Home Assistant subscribes created.

djm193 commented 7 months ago

Hello everyone, with the new Version 2.1 the Add-On will no find the devices added in the connectlife app with the correct names for exampel "Klimaanlage Schlafzimmer". However I cannot find the entities which should be created through the add-on. at this very moment, alle units are operable within the connectlife app.

When I check my mqqt Logs there is always an error:

024-02-26 12:28:14: Client connectlife-api closed its connection. 2024-02-26 12:28:16: New connection from 172.30.33.4:56410 on port 1883. 2024-02-26 12:28:16: New client connected from 172.30.33.4:56410 as connectlife-api (p1, c0, k10, u'addons'). 2024-02-26 12:28:17: Client connectlife-api closed its connection. 2024-02-26 12:28:19: New connection from 172.30.33.4:56418 on port 1883. 2024-02-26 12:28:19: New client connected from 172.30.33.4:56418 as connectlife-api (p1, c0, k10, u'addons'). 2024-02-26 12:28:20: Client connectlife-api closed its connection. 2024-02-26 12:28:21: New connection from 172.30.33.4:56422 on port 1883. 2024-02-26 12:28:21: New client connected from 172.30.33.4:56422 as connectlife-api (p1, c0, k10, u'addons'). 2024-02-26 12:28:22: Client connectlife-api closed its connection. 2024-02-26 12:28:23: New connection from 172.30.33.4:58904 on port 1883. 2024-02-26 12:28:23: New client connected from 172.30.33.4:58904 as connectlife-api (p1, c0, k10, u'addons'). 2024-02-26 12:29:06: Client connectlife-api closed its connection. 2024-02-26 12:29:17: New connection from 172.30.33.4:47586 on port 1883. 2024-02-26 12:29:17: New client connected from 172.30.33.4:47586 as connectlife-api (p1, c0, k10, u'addons'). 2024-02-26 12:29:48: New connection from 172.30.32.2:59666 on port 1883. 2024-02-26 12:29:48: Client closed its connection. 2024-02-26 12:31:48: New connection from 172.30.32.2:58402 on port 1883. 2024-02-26 12:31:48: Client closed its connection. 2024-02-26 12:33:48: New connection from 172.30.32.2:56996 on port 1883. 2024-02-26 12:33:48: Client closed its connection.

Add-On looks stable like this:

2024-02-26 12:35:23,186 DEBG 'mqtt' stdout output: [2024-02-26 11:35:23] production.INFO: Updating HA device state ["pu000098650051000200030003000000887dd8cf79d"]

2024-02-26 12:35:23,188 DEBG 'mqtt' stdout output: [2024-02-26 11:35:23] production.INFO: Updating HA device state ["pu000098650051000200030003000000d26a6f07d2b"]

2024-02-26 12:35:23,191 DEBG 'mqtt' stdout output: [2024-02-26 11:35:23] production.INFO: Updating HA device state ["pu000098650051000200030003000000d26a6f07d98"]

2024-02-26 12:36:23,712 DEBG 'mqtt' stdout output: [2024-02-26 11:36:23] production.INFO: Response ["[{\"wifiId\":\"8650051000200030003000000887dd8cf79d\",\"deviceId\":\"8650051000200030003000000887dd8cf79d\",\"puid\":\"pu000098650051000200030003000000887dd8cf79d\",\"deviceNickName\":\"Klimaanlage Wohnzimmer\",\"deviceFeatureCode\":\"104\",\"deviceFeatureName\":\"104\u51b7\u6696\u8282\u80fd\u65e0\u529f\u7387\",\"deviceTypeCode\":\"009\",\"deviceTypeName\":\"\",\"bindTime\":1708286816345,\"role\":1,\"roomId\":870122,\"roomName\":\"Wohnzimmer \",\"statusList\":{\"t_sleep\":\"0\",\"t_power\":\"0\",\"t_work_mode\":\"0\",\"t_fan_speed\":\"0\",\"t_fan_speed_s\":\"0\",\"t_fan_mute\":\"0\",\"t_super\":\"0\",\"t_eco\":\"0\",\"t_temp\":\"0\",\"t_temp_type\":\"0\",\"t_up_down\":\"0\",\"t_swing_follow\":\"2\",\"t_swing_direction\":\"4\",\"t_swing_angle\":\"0\",\"t_fanspeedcv\":\"0\",\"t_tms\":\"0\",\"t_temp_compensate\":\"5\",\"f_humidity\":\"128\",\"f_temp_in\":\"21\",\"f_electricity\":\"0\",\"f_votage\":\"0\",\"f_e_intemp\":\"0\",\"f_e_incoiltemp\":\"0\",\"f_e_inhumidity\":\"0\",\"f_e_infanmotor\":\"0\",\"f_e_arkgrille\":\"0\",\"f_e_invzero\":\"0\",\"f_e_incom\":\"0\",\"f_e_indisplay\":\"0\",\"f_e_inkeys\":\"0\",\"f_e_inwifi\":\"0\",\"f_e_inele\":\"0\",\"f_e_ineeprom\":\"0\",\"f_e_outeeprom\":\"0\",\"f_e_outcoiltemp\":\"0\",\"f_e_outgastemp\":\"0\",\"f_e_outtemp\":\"0\",\"f_e_waterfull\":\"0\",\"f_e_upmachine\":\"0\",\"f_e_dwmachine\":\"0\",\"f_e_over_cold\":\"0\",\"f_e_over_hot\":\"0\",\"f_e_push\":\"0\",\"t_demand_response\":\"0\",\"t_dal\":\"0\",\"t_talr\":\"1\",\"f-filter\":\"0\"},\"useTime\":1708286816324,\"offlineState\":1,\"seq\":1,\"createTime\":0},{\"wifiId\":\"8650051000200030003000000d26a6f07d2b\",\"deviceId\":\"8650051000200030003000000d26a6f07d2b\",\"puid\":\"pu000098650051000200030003000000d26a6f07d2b\",\"deviceNickName\":\"Klimaanlage Schlafzimmer\",\"deviceFeatureCode\":\"104\",\"deviceFeatureName\":\"104\u51b7\u6696\u8282\u80fd\u65e0\u529f\u7387\",\"deviceTypeCode\":\"009\",\"deviceTypeName\":\"\",\"bindTime\":1708285893716,\"role\":1,\"roomId\":870120,\"roomName\":\"Schlafzimmer 1\",\"statusList\":{\"t_sleep\":\"0\",\"t_power\":\"0\",\"t_work_mode\":\"0\",\"t_fan_speed\":\"0\",\"t_fan_speed_s\":\"0\",\"t_fan_mute\":\"0\",\"t_super\":\"0\",\"t_eco\":\"0\",\"t_temp\":\"0\",\"t_temp_type\":\"0\",\"t_up_down\":\"0\",\"t_swing_follow\":\"3\",\"t_swing_direction\":\"1\",\"t_swing_angle\":\"0\",\"t_fanspeedcv\":\"0\",\"t_tms\":\"1\",\"t_temp_compensate\":\"0\",\"f_humidity\":\"128\",\"f_temp_in\":\"19\",\"f_electricity\":\"0\",\"f_votage\":\"0\",\"f_e_intemp\":\"0\",\"f_e_incoiltemp\":\"0\",\"f_e_inhumidity\":\"0\",\"f_e_infanmotor\":\"0\",\"f_e_arkgrille\":\"0\",\"f_e_invzero\":\"0\",\"f_e_incom\":\"0\",\"f_e_indisplay\":\"0\",\"f_e_inkeys\":\"0\",\"f_e_inwifi\":\"0\",\"f_e_inele\":\"0\",\"f_e_ineeprom\":\"0\",\"f_e_outeeprom\":\"0\",\"f_e_outcoiltemp\":\"0\",\"f_e_outgastemp\":\"0\",\"f_e_outtemp\":\"0\",\"f_e_waterfull\":\"0\",\"f_e_upmachine\":\"0\",\"f_e_dwmachine\":\"0\",\"f_e_over_cold\":\"0\",\"f_e_over_hot\":\"0\",\"f_e_push\":\"0\",\"t_demand_response\":\"0\",\"t_dal\":\"1\",\"t_talr\":\"0\",\"f-filter\":\"0\"},\"useTime\":1708285893695,\"offlineState\":1,\"seq\":0,\"createTime\":0},{\"wifiId\":\"8650051000200030003000000d26a6f07d98\",\"deviceId\":\"8650051000200030003000000d26a6f07d98\",\"puid\":\"pu000098650051000200030003000000d26a6f07d98\",\"deviceNickName\":\"Klimaanlage Kind 1\",\"deviceFeatureCode\":\"104\",\"deviceFeatureName\":\"104\u51b7\u6696\u8282\u80fd\u65e0\u529f\u7387\",\"deviceTypeCode\":\"009\",\"deviceTypeName\":\"\",\"bindTime\":1664043766820,\"role\":1,\"roomId\":870198,\"roomName\":\"Kind 1\",\"statusList\":{\"t_sleep\":\"0\",\"t_power\":\"0\",\"t_work_mode\":\"0\",\"t_fan_speed\":\"0\",\"t_fan_speed_s\":\"0\",\"t_fan_mute\":\"0\",\"t_super\":\"0\",\"t_eco\":\"0\",\"t_temp\":\"0\",\"t_temp_type\":\"0\",\"t_up_down\":\"0\",\"t_swing_follow\":\"1\",\"t_swing_direction\":\"0\",\"t_swing_angle\":\"0\",\"t_fanspeedcv\":\"0\",\"t_tms\":\"0\",\"t_temp_compensate\":\"0\",\"f_humidity\":\"128\",\"f_temp_in\":\"19\",\"f_electricity\":\"0\",\"f_votage\":\"0\",\"f_e_intemp\":\"0\",\"f_e_incoiltemp\":\"0\",\"f_e_inhumidity\":\"0\",\"f_e_infanmotor\":\"0\",\"f_e_arkgrille\":\"0\",\"f_e_invzero\":\"0\",\"f_e_incom\":\"0\",\"f_e_indisplay\":\"0\",\"f_e_inkeys\":\"0\",\"f_e_inwifi\":\"0\",\"f_e_inele\":\"0\",\"f_e_ineeprom\":\"0\",\"f_e_outeeprom\":\"0\",\"f_e_outcoiltemp\":\"0\",\"f_e_outgastemp\":\"0\",\"f_e_outtemp\":\"0\",\"f_e_waterfull\":\"0\",\"f_e_upmachine\":\"0\",\"f_e_dwmachine\":\"0\",\"f_e_over_cold\":\"0\",\"f_e_over_hot\":\"0\",\"f_e_push\":\"0\",\"t_demand_response\":\"0\",\"t_dal\":\"0\",\"t_talr\":\"0\",\"f-filter\":\"0\"},\"useTime\":1694353036524,\"offlineState\":1,\"seq\":0,\"createTime\":0}]"]

2024-02-26 12:36:23,715 DEBG 'mqtt' stdout output: [2024-02-26 11:36:23] production.INFO: Updating HA device state ["pu000098650051000200030003000000887dd8cf79d"]

2024-02-26 12:36:23,716 DEBG 'mqtt' stdout output: [2024-02-26 11:36:23] production.INFO: Updating HA device state ["pu000098650051000200030003000000d26a6f07d2b"]

2024-02-26 12:36:23,718 DEBG 'mqtt' stdout output: [2024-02-26 11:36:23] production.INFO: Updating HA device state ["pu000098650051000200030003000000d26a6f07d98"]

**As this is the only Appliance in my whole house which is yet not operable with Home Assistant I would be really thankful for some help. What am I missing here?

Best djm193**

bilan commented 7 months ago

Add-on will create the device (not only entity) which can by found by typing "connectlife" in search field:

image

@djm193 do you have something in that place?

djm193 commented 7 months ago

Thank you for your answer. Unfortunately I cannot see anything like this either in devices nor in entities. the only thing I can find ist as follows: grafik

bilan commented 7 months ago

Do you have MQTT Integration?

image

https://www.home-assistant.io/integrations/mqtt

djm193 commented 7 months ago

Oh wait, now it is getting embarrasing. I do only have the mosquitto broker add-on. Ok I have just set it up. It works!

Thank you very much! I was so confused with "mqtt add-on" in the name of your connectlife add-on that I did not try to install the integration.

saragrigolin commented 7 months ago

Do you have MQTT Integration? image https://www.home-assistant.io/integrations/mqtt

Hello I have the same problem but I have the MQTT integration. The add-on seems to work correctly, since I have new logs every minute with correct deviceId, deviceNickName and so on, but I cannot find the device in the MQTT integration. I tried to reload everything, but I have no clue why it's not appearing as device. Is there something that I'm doing wrong?

Thanks

image
bilan commented 7 months ago

Do you have MQTT Integration? image https://www.home-assistant.io/integrations/mqtt

Hello I have the same problem but I have the MQTT integration. The add-on seems to work correctly, since I have new logs every minute with correct deviceId, deviceNickName and so on, but I cannot find the device in the MQTT integration. I tried to reload everything, but I have no clue why it's not appearing as device.

Is there something that I'm doing wrong?

Thanks

image

What ha version do you have? You can always add the device by hand in configuration.yaml

RaulFury commented 7 months ago

Thank you for this integration! Unfortunately I am also having the same issue: image Your addon seems to be working correctly and I am receiving the A/C information. However, the MQTT integration is not discovering any devices.

saragrigolin commented 7 months ago

Do you have MQTT Integration? image https://www.home-assistant.io/integrations/mqtt

Hello I have the same problem but I have the MQTT integration. The add-on seems to work correctly, since I have new logs every minute with correct deviceId, deviceNickName and so on, but I cannot find the device in the MQTT integration. I tried to reload everything, but I have no clue why it's not appearing as device.

Is there something that I'm doing wrong?

Thanks

image

What ha version do you have? You can always add the device by hand in configuration.yaml

I solved updating the HA version to the latest one (I had the one before). Thank you!