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

friendly_name including # char causes disconnects from mqtt server #3175

Closed
JasperAlgra opened this issue Mar 22, 2020 · 6 comments
Closed
Labels
stale Stale issues

Comments

@JasperAlgra
Copy link

Bug Report

What happened

I found out that using hashtags in the friendly_name of device in configuration.yaml causes strange behaviour of zigbee2mqtt including dis/reconnect to the MQTT server.

Example from configuration.yaml

  '0x000d6ffffe19412f':
#    friendly_name: 'gu10 dimable white spectrum #1'
    friendly_name: '0x000d6ffffe19412f'

In my case I've got a bulb and a remote. When I push a button on the remote zigbee2mqtt breaks and resets the connection to the MQTT server (maybe more, I cannot see in the debug log).

What did you expect to happen

How to reproduce it (minimal and precise)

add a friendly_name with a hashtag in it. Press a button on the remote or trigger an action through Home Assistant.

Debug Info

zigbee2mqtt version: 1.12.0 (commit #840b9d9
CC253X firmware version: default

Logs:

With errors:
https://hastebin.com/sutavuxiba.pl
Without errors:
https://hastebin.com/owihifojot.apache

@Koenkk
Copy link
Owner

Koenkk commented Mar 23, 2020

MQTT doesn't allow wildcards (+/#) to be used in topic names.

Publishers are not allowed to use the wildcard characters in their topic names.

Source: https://www.eclipse.org/paho/files/mqttdoc/MQTTClient/html/wildcard.html

Latest zigbee2mqtt dev refuses to start when this is set. Thanks!

@stale
Copy link

stale bot commented May 22, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Stale issues label May 22, 2020
@Girbie
Copy link

Girbie commented Aug 9, 2020

@JasperAlgra : I'm facing the same issue now. How did you resolve it? zigbee2mqtt doesn't start anymore and I can't access/change the device name.

@aro-git
Copy link

aro-git commented Oct 18, 2020

I'm facing the same issue right now. I named my device with fancy name with UTF-8 characters and slash (czujnik otwarcia / zamknięcia 3b - drzwi wiatrołap) and now I can't rollback it. I can't rename device and I can't access/change the device name (503: Service Unaviable).

@Koenkk
Copy link
Owner

Koenkk commented Oct 18, 2020

@aro-git I've tried and it works fine in my case:

image

You can always stop zigbee2qmtt, change the name in the configuration.yaml.

@aro-git
Copy link

aro-git commented Oct 18, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Stale issues
Projects
None yet
Development

No branches or pull requests

4 participants