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

Plugin not displaying Outlet names in Homekit #37

Closed
Fastasabadger opened this issue Jun 19, 2021 · 4 comments
Closed

Plugin not displaying Outlet names in Homekit #37

Fastasabadger opened this issue Jun 19, 2021 · 4 comments
Labels
bug Something isn't working no-issue-activity

Comments

@Fastasabadger
Copy link

Fastasabadger commented Jun 19, 2021

I have the issue where most of my devices are just displaying as switch_1 in the Apple Home app.

IMG_1763

They are however named in the Tuya App and appear correctly on the IoT. I can see that the Tuya Plugin is aware of the name of the device, but displays it as switch_1

It appears that the bulbs I use appear to populate their names correctly but none of the outlets or switches do.

LOG EXAMPLE FOR AN ACCESSORY DISPLAYING AS SWITCH_1

"model":"MK11","name":"Immersion Heater","online":true,"owner_id":"489372","product_id":"qCY4YFq02AP0i1Uu","product_name":"海贝通用定时器MK11","status":[{"code":"switch_1","value":false},{"code":"countdown_1","value":0}],"sub":false,"time_zone":"+01:00","uid":"eu1510862576411uv6Ld","update_time":1624098269,"uuid":"02200434dc4f221a50ed"},

Adding: Immersion Heater (cz / 02200434dc4f221a50ed) Existing Accessory found Immersion Heater 02200434dc4f221a50ed 5c27c49f-377a-4309-9413-bf521d06453c

@Hanh94 Hanh94 added the bug Something isn't working label Jun 21, 2021
@Hanh94
Copy link
Contributor

Hanh94 commented Jun 21, 2021

Hi @Fastasabadger ,Thank you for your feedback.
We believe that your device object was created by a plugin prior to v1.1.9, which does not support subService. When you update to v1.1.9, that there will be a conflict. Please try to remove the cache that created the device object previously, and restart the plugin and configuration.

@unike
Copy link

unike commented Jun 21, 2021

Hello, I have the same issue and I’m on version 1.1.9, just removed the cached accessories but the issue remains.

@Hanh94
Copy link
Contributor

Hanh94 commented Jun 21, 2021

Hello, I have the same issue and I’m on version 1.1.9, just removed the cached accessories but the issue remains.

Hi @unike ,
The correct deviceconfig.name is assigned to accessory.displayName when you create an accessory object, and you can also set the name of the accessory when you reconfigure it to the Home app.

@github-actions
Copy link

Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.

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

No branches or pull requests

3 participants