-
Notifications
You must be signed in to change notification settings - Fork 1
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
AssertionError [ERR_ASSERTION]: Accessories must be created with a non-empty displayName. #12
Comments
I suspect if you set |
I had [Tessie] AssertionError [ERR_ASSERTION]: Accessories must be created with a non-empty displayName. JSON { |
I get the same error. I've tried it with prefixName set to true and false, same error either way
|
Yep same error for me.
|
Ok I believe this happens if you haven't named your vehicle or energy site, 0.4.2 adds default values for both. Please let me know if this release fixes the issue or not. |
Same issue unfortunately.
|
Ok thanks for the updated error log, I moved the fix to cover both places displayName is used. Please try 0.4.3 and let me know again. |
That solved the problem for me, thank you! |
Still not working for me on 0.4.3
|
I'm going to push another release to fix it yet another way, but if you could turn on debug logging the log immediately before the error will tell me what your displayName is trying to be set to, which will help identify why this keeps failing. |
0.4.3
0.4.4 appears to be working fine
|
working for me... thanks |
Describe The Issue:
Plugin starts however get the following error
[27/08/2024, 10:19:40] [Tessie] AssertionError [ERR_ASSERTION]: Accessories must be created with a non-empty displayName.
at new Accessory (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:495:11)
at new PlatformAccessory (/usr/lib/node_modules/homebridge/src/platformAccessory.ts:72:9)
at file:///usr/lib/node_modules/homebridge-tessie/src/platform.ts:134:33
at Array.forEach ()
at file:///usr/lib/node_modules/homebridge-tessie/src/platform.ts:109:30
at processTicksAndRejections (node:internal/process/task_queues:95:5) {
generatedMessage: false,
code: 'ERR_ASSERTION',
actual: undefined,
expected: true,
operator: '=='
To Reproduce:
Every time I start
Expected behavior:
Should load without issue.
Have two Teslas on the account
Logs:
{
"name": "Tessie",
"accessToken": "correct token applied",
"prefixName": false,
"_bridge": {
"username": "######",
"port": 47070
},
"platform": "Tessie"
}
Screenshots:
Environment:
All latest versions
The text was updated successfully, but these errors were encountered: