You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, thank you for this awesome project. I've set it up and My Model 3 has shown up in the Home App successfully.
I noticed the annoying accessory name issue mentioned in the readme. And read the issue of its fix. Found out that you've tried to fix it in 90609b6 but soon reverted in 2e52aad because The "ConfiguredName" characteristic did not behave as expected; it was impossible to set custom names through the Home app that persisted across Homebridge reboots
Then I tried to manually install the version of 90609b6 (which is 4.3.0 on NPM), it worked quite well for me because I do not need to rename them.
Now I am wondering if there could be an config field to optionally enable the fix for general users like myself. For example,
if(config.fixName){// `fixName` can be configured via home bridge UI config pageservice.addOptionalCharacteristic(Characteristic.ConfiguredName);service.setCharacteristic(Characteristic.ConfiguredName,accessoryName);}
I believe many users would be happy for it!
The text was updated successfully, but these errors were encountered:
Hi, thank you for this awesome project. I've set it up and My Model 3 has shown up in the Home App successfully.
I noticed the annoying accessory name issue mentioned in the readme. And read the issue of its fix. Found out that you've tried to fix it in 90609b6 but soon reverted in 2e52aad because
The "ConfiguredName" characteristic did not behave as expected; it was impossible to set custom names through the Home app that persisted across Homebridge reboots
Then I tried to manually install the version of 90609b6 (which is 4.3.0 on NPM), it worked quite well for me because I do not need to rename them.
Now I am wondering if there could be an config field to optionally enable the fix for general users like myself. For example,
I believe many users would be happy for it!
The text was updated successfully, but these errors were encountered: