Cant generate/update the map

Question

Cant generate/update the map

FranciscoTrigo opened this issue 5 years ago · comments

Hello,

I am trying to use this component, but it doesnt work. It doesnt update/generate the map with either the service call or the "Update Now" button.
I do not know where to look for logs for this, there is nothing about it in the hassio logs.

What can i do?
Thanks

rgruebel · Answer 1 · Sun Apr 28 2019 18:36:34 GMT+0800 (China Standard Time)

Can you please try again with the current version? There was a problem with HA 0.92, but now it should work again.

Francisco Trigo · Answer 2 · Mon Apr 29 2019 13:26:59 GMT+0800 (China Standard Time)

Hello
I updated both HA and this component but its not working yet

rgruebel · Answer 3 · Mon Apr 29 2019 13:49:13 GMT+0800 (China Standard Time)

You need to look in the homeassistan log, not the hassio log.

boojew · Answer 4 · Tue Apr 30 2019 11:31:48 GMT+0800 (China Standard Time)

I'm running 0.92.1 and I get

2019-04-29 23:30:15 ERROR (MainThread) [homeassistant.core] Error doing job: SSL handshake failed
Traceback (most recent call last):
  File "uvloop/sslproto.pyx", line 500, in uvloop.loop.SSLProtocol._on_handshake_complete
  File "uvloop/sslproto.pyx", line 484, in uvloop.loop.SSLProtocol._do_handshake
  File "/usr/local/lib/python3.7/ssl.py", line 763, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: SSLV3_ALERT_CERTIFICATE_UNKNOWN] sslv3 alert certificate unknown (_ssl.c:1056)

This was running well on 0.90 (and probably 0.91 based on last updated date)

rgruebel · Answer 5 · Tue Apr 30 2019 12:17:18 GMT+0800 (China Standard Time)

@boojew I don't think that this error has anything to do with this component.

boojew · Answer 6 · Wed May 01 2019 01:51:59 GMT+0800 (China Standard Time)

Possible - but occurs systematically when I hit update..

…

On Tue, Apr 30, 2019 at 12:17 AM rgruebel ***@***.***> wrote: @boojew <https://github.com/boojew> I don't think that this error has anything to do with this component. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAHX6DSPWD7WWP2PV3X5O6DPS7B47ANCNFSM4HHVGHHA> .

Francisco Trigo · Answer 7 · Sat May 04 2019 14:46:25 GMT+0800 (China Standard Time)

2019-05-03 20:57:03 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for zigbee2mqtt_networkmap 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. 2019-05-03 20:57:04 WARNING (MainThread) [homeassistant.components.http] Configuring api_password via the http component has been deprecated. Use the legacy api password auth provider instead. For instructions, see https://www.home-assistant.io/docs/authentication/providers/#legacy-api-password

Here is the log, doesnt really say much.
I updated everything recently but still not working

Francisco Trigo · Answer 8 · Sun May 05 2019 17:04:07 GMT+0800 (China Standard Time)

I originally changed the mqtt topic that my zigbee2mqtt uses, and reading thru the network map files it seems like it uses the default ones.
All I should need to do is change "DEFAULT_TOPIC" in init.py and zigbee2mqtt_networkmap.py.
And now it works.
I think adding this info to the readme.md would be useful just in case other people also changed their mqtt topic and cant figure it out :)

rgruebel · Answer 9 · Sun May 05 2019 18:31:12 GMT+0800 (China Standard Time)

It is also possible to overwrite the topic via configuration.yaml. But you're right, I should add this in the README
topic: your topic
I've never tested it myself but it's implemented