Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue when I configure custom integration #21

Open
krelltunez opened this issue Sep 18, 2022 · 0 comments
Open

Issue when I configure custom integration #21

krelltunez opened this issue Sep 18, 2022 · 0 comments

Comments

@krelltunez
Copy link

krelltunez commented Sep 18, 2022

Hi! I'm a long-time user and a coffee contributor to the efforts for the local add-on. I figured I'd try it out today with one of my garage door opener. I have the local add-on configured according to your guide, and I have successfully paired the door opener (it shows as ONLINE in the custom pairer app and in the "paired devices" section of the add-on). The device also has an IP address in my router admin, so it appears to be fully connected.

The issue appears to occur when I setup the component integration. I select "Connect to LAN-only broker" and see "The discovery was unable to automatically find MQTT/API addresses. Default values have been selected." I leave the default values and fill in the same username and password that I used when I set up the add-on (I'm assuming that's what I'm supposed to do). I then get the success message that says "Created configuration for http://homeassistant.local:2003." However, in the integration page it says "Retrying setup: None."

The HA log says:

This error originated from a custom integration.

Logger: custom_components.meross_cloud
Source: custom_components/meross_cloud/__init__.py:196
Integration: Meross Cloud IoT
First occurred: 10:17:19 AM (46 occurrences)
Last logged: 11:19:47 AM

Error occurred. ------------------------------------- Component version: 0.4.5.0 Device info: <Unavailable> Error Message: "An exception occurred while setting up the meross manager. Setup will be retried..."
Traceback (most recent call last):
  File "/config/custom_components/meross_cloud/__init__.py", line 451, in async_setup_entry
    await meross_coordinator.initial_setup()
  File "/config/custom_components/meross_cloud/__init__.py", line 196, in initial_setup
    await self._manager.async_device_discovery()
  File "/usr/local/lib/python3.10/site-packages/meross_iot/manager.py", line 363, in async_device_discovery
    dev = await self._async_enroll_new_http_dev(d)
  File "/usr/local/lib/python3.10/site-packages/meross_iot/manager.py", line 446, in _async_enroll_new_http_dev
    mqtt_hostname=extract_domain(device_info.domain),
  File "/usr/local/lib/python3.10/site-packages/meross_iot/utilities/network.py", line 8, in extract_domain
    tokens = address.split(":")
AttributeError: 'NoneType' object has no attribute 'split'


And the MQTT Service log says:

2022-09-18 16:22:01.759397008 time="2022-09-18T11:22:01-05:00" level=warning msg="wrong password for user _agent"
2022-09-18 16:22:00.398775777 time="2022-09-18T11:22:00-05:00" level=info msg="error code: 401"
2022-09-18 16:20:00.336504901 time="2022-09-18T11:20:00-05:00" level=warning msg="wrong password for user _agent"
2022-09-18 16:19:58.927098082 New client connectedtime="2022-09-18T11:19:58-05:00" level=info msg="error code: 401"
2022-09-18 16:19:52.259497043 New connection from 192.168.2.25:64530 on port 2001.
2022-09-18 16:19:52.259487099 Client fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU disconnected.
2022-09-18 16:19:52.259476784 fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU 1 /appliance/2009106082461136100548e1e931f72a/subscribe
2022-09-18 16:19:52.259466062 New client connected from 192.168.2.25:64529 as fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU (p1, c1, k120, u'48:e1:e9:31:f7:2a').
2022-09-18 16:19:52.259454840 New connection from 192.168.2.25:64529 on port 2001.
2022-09-18 16:19:52.259444748 Client fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU disconnected.
2022-09-18 16:19:52.259434378 fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU 1 /appliance/2009106082461136100548e1e931f72a/subscribe
2022-09-18 16:19:52.259423711 New client connected from 192.168.2.25:64528 as fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU (p1, c1, k120, u'48:e1:e9:31:f7:2a').
2022-09-18 16:19:52.259412415 New connection from 192.168.2.25:64528 on port 2001.
2022-09-18 16:19:52.259402637 Client fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU disconnected.
2022-09-18 16:19:52.259392008 fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU 1 /appliance/2009106082461136100548e1e931f72a/subscribe
2022-09-18 16:19:52.259381156 New client connected from 192.168.2.25:64527 as fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU (p1, c1, k120, u'48:e1:e9:31:f7:2a').
2022-09-18 16:19:52.259369805 New connection from 192.168.2.25:64527 on port 2001.
2022-09-18 16:19:52.259359731 Client fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU disconnected.
2022-09-18 16:19:52.259349305 fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU 1 /appliance/2009106082461136100548e1e931f72a/subscribe
2022-09-18 16:19:52.259338601 New client connected from 192.168.2.25:64526 as fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU (p1, c1, k120, u'48:e1:e9:31:f7:2a').
2022-09-18 16:19:52.259327194 New connection from 192.168.2.25:64526 on port 2001.
2022-09-18 16:19:52.259317287 Client fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU disconnected.
2022-09-18 16:19:52.259306824 fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU 1 /appliance/2009106082461136100548e1e931f72a/subscribe
2022-09-18 16:19:52.259296046 New client connected from 192.168.2.25:64525 as fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU (p1, c1, k120, u'48:e1:e9:31:f7:2a').
2022-09-18 16:19:52.259284584 New connection from 192.168.2.25:64525 on port 2001.
2022-09-18 16:19:52.259274732 Client <unknown> disconnected, not authorised.
2022-09-18 16:19:52.259264639 New connection from 127.0.0.1:39879 on port 2001.
2022-09-18 16:19:52.259254806 Client fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU disconnected.
2022-09-18 16:19:52.259244288 fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU 1 /appliance/2009106082461136100548e1e931f72a/subscribe
2022-09-18 16:19:52.259233140 New client connected from 192.168.2.25:64524 as fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU (p1, c1, k120, u'48:e1:e9:31:f7:2a').
2022-09-18 16:19:52.259221473 New connection from 192.168.2.25:64524 on port 2001.
2022-09-18 16:19:52.259211325 Client fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU disconnected.
2022-09-18 16:19:52.259200455 fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU 1 /appliance/2009106082461136100548e1e931f72a/subscribe
2022-09-18 16:19:52.259189270 New client connected from 192.168.2.25:64523 as fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU (p1, c1, k120, u'48:e1:e9:31:f7:2a').
2022-09-18 16:19:52.259177622 New connection from 192.168.2.25:64523 on port 2001.
2022-09-18 16:19:52.259167326 Client fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU disconnected.
2022-09-18 16:19:52.259156789 fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU 1 /appliance/2009106082461136100548e1e931f72a/subscribe
2022-09-18 16:19:52.259145808 New client connected from 192.168.2.25:64522 as fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU (p1, c1, k120, u'48:e1:e9:31:f7:2a').
2022-09-18 16:19:52.259134641 New connection from 192.168.2.25:64522 on port 2001.
2022-09-18 16:19:52.259124530 Client fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU disconnected.
2022-09-18 16:19:52.259113642 fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU 1 /appliance/2009106082461136100548e1e931f72a/subscribe
2022-09-18 16:19:52.259102364 New client connected from 192.168.2.25:64521 as fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU (p1, c1, k120, u'48:e1:e9:31:f7:2a').
2022-09-18 16:19:52.259090753 New connection from 192.168.2.25:64521 on port 2001.
2022-09-18 16:19:52.259080272 Client fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU disconnected.
2022-09-18 16:19:52.259069309 fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU 1 /appliance/2009106082461136100548e1e931f72a/subscribe
2022-09-18 16:19:52.259057531 New client connected from 192.168.2.25:64520 as fmware:2009106082461136100548e1e931f72a_TKlAxDiPg8f12cbU (p1, c1, k120, u'48:e1:e9:31:f7:2a').
2022-09-18 16:19:52.259044161 New connection from 192.168.2.25:64520 on port 2001.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant