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

Entity_Not_Found error after assigning friendly names #5618

Closed
lazynomad opened this issue Jan 8, 2021 · 5 comments
Closed

Entity_Not_Found error after assigning friendly names #5618

lazynomad opened this issue Jan 8, 2021 · 5 comments
Labels
problem Something isn't working

Comments

@lazynomad
Copy link

lazynomad commented Jan 8, 2021

What happened

After assigning a friendly name to Ikea Fyrtur blinds, I get "Entity_Not_Found" error. Frontend shows the correct friendly name, however all the actions throw "entity_not_found" error. Zigbee2Mqtt has been setup as a hassio add-on.
Debug logs after issuing "Open" request: https://pastebin.com/FEMRbaFr

Note: Tried restarting zigbee2mqtt and even hassio several times with no luck.
Tried mosquitto_pub instead of frontend to assign a friendly name but didn't help.
Deleted the device from hassio devices to force update. Didn't work.

Once, we get to this point, the only way to remove the device is by issuing mosquitto_pub delete request.

What did you expect to happen

Devices must work as expected irrespective of the friendly name assignment.
Note that I did not have any issues assigning friendly name to Aqara temperature sensor. However, these sensors are read-only and there's no action to perform over them (if that matters).

How to reproduce it (minimal and precise)

Pair an Ikea Fyrtur blind, rename from the IEEE address to a friendly name. The device stops working.

Debug info

Zigbee2MQTT version:
Adapter hardware: Conbee II
Adapter firmware version:

@lazynomad lazynomad added the problem Something isn't working label Jan 8, 2021
@Koenkk
Copy link
Owner

Koenkk commented Jan 8, 2021

The friendly_name is not allowed to end with /center (since this can also be an endpoint name). All below are not allowed:

[
    'left', 'right', 'center', 'bottom_left', 'bottom_right', 'default',
    'top_left', 'top_right', 'white', 'rgb', 'cct', 'system', 'top', 'bottom', 'center_left', 'center_right',
    'ep1', 'ep2', 'row_1', 'row_2', 'row_3', 'row_4', 'relay',
    'l1', 'l2', 'l3', 'l4', 'l5', 'l6', 'l7', 'l8',
    'button_1', 'button_2', 'button_3', 'button_4', 'button_5',
    'button_6', 'button_7', 'button_8', 'button_9', 'button_10',
    'button_11', 'button_12', 'button_13', 'button_14', 'button_15',
    'button_16', 'button_17', 'button_18', 'button_19', 'button_20',
    'button_light', 'button_fan_high', 'button_fan_med', 'button_fan_low',
    'heat', 'cool', 'water',
]

This was however not properly checked but has been fixed now. I suggest you rename your device to living_room/blinds_center.

Changes will be available in the latest dev branch in a few hours (https://www.zigbee2mqtt.io/how_tos/how-to-switch-to-dev-branch.html)

@lazynomad
Copy link
Author

Thank you. That seems to work for the new devices.
Is there a way to fix the name for the existing corrupted device ? Or is the only way to re-pair it ? I cannot find a clean way to delete the corrupted (in terms of name) device as I get the same "entity_not_found" error.

@Koenkk
Copy link
Owner

Koenkk commented Jan 8, 2021

Stop zigbee2mqtt and change name manually in the configuration.yaml

@lazynomad
Copy link
Author

Sorry if it's a basic question. I am new to Zigbee2Mqtt.
When you say configuration.yaml, do you mean devices.yaml because that is where I see the devices and their friendly names. I can access the file over the ssh-addon of hassio.

@Koenkk
Copy link
Owner

Koenkk commented Jan 8, 2021

yes, devices.yaml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants