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
I am running an IPv6 only network. The scrypted server address is set to 2a06:e881:5804:1234:ffff:ffff:ffff:ffff in the settings. Why can't it bind to it's IPv6 address?
The moment I add IPv4 to the scrypted server and the client, everything starts to work.
linux x64 #1 SMP Debian 5.10.178-3 (2023-04-22)
server version: 0.41.0
plugin version: @scrypted/homekit 1.2.29
full
########################
8/16/2023, 4:48:15 PM
########################
node modules /server/volume/plugins/@scrypted/homekit/node18-linux-x64-20230727
plugin loaded
adding Rack
[Rack] Device is in accessory mode and is online. HomeKit services are being published.
adding Tapo C200
[Tapo C200] Device is in accessory mode and is online. HomeKit services are being published.
mdns bind address 2a06:e881:5804:1234:ffff:ffff:ffff:ffff
Removed Recordings: 0: 0 bytes.
Retained Recordings: 0: 0 bytes.
[Rack] HomeKit Connection 2a06:e881:5804:1234:aaaa:aaaa:aaaa:aaaa
[Tapo C200] HomeKit Connection 2a06:e881:5804:1234:bbbb:bbbb:bbbb:bbbb
[Rack] HomeKit Connection 2a06:e881:5804:1234:bbbb:bbbb:bbbb:bbbb
[Tapo C200] HomeKit Connection 2a06:e881:5804:1234:aaaa:aaaa:aaaa:aaaa
unhandledRejection Error: bind EINVAL 2a06:e881:5804:1234:ffff:ffff:ffff:ffff
at node:dgram:362:20
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
errno: -22,
code: 'EINVAL',
syscall: 'bind',
address: '2a06:e881:5804:1234:ffff:ffff:ffff:ffff'
}
[Tapo C200@Setup Endpoints] The write handler for the characteristic 'Setup Endpoints' on the accessory 'Tapo C200' was slow to respond!
[Tapo C200@Setup Endpoints] The write handler for the characteristic 'Setup Endpoints' on the accessory 'Tapo C200' didn't respond at all!. Please check that you properly call the callback!
[Tapo C200] handleStreamRequest { sessionID: '017fe39b-a116-4aa7-827b-f7cefeccffff', type: 'stop' }
This discussion was converted from issue #1021 on August 16, 2023 18:30.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am running an IPv6 only network. The scrypted server address is set to
2a06:e881:5804:1234:ffff:ffff:ffff:ffff
in the settings. Why can't it bind to it's IPv6 address?The moment I add IPv4 to the scrypted server and the client, everything starts to work.
Beta Was this translation helpful? Give feedback.
All reactions