Comments (12)
commented on June 16, 2024
has anyone faced similar kind of issues..
from hap-nodejs.
NorthernMan54
commented on June 16, 2024
Pls share a similar log showing the issue occurring. Ie open home app, light on characteristic register for events, change light setting locally, code logging light change, and light change event not being sent or missing.
from hap-nodejs.
commented on June 16, 2024
Since there are no hap connections open no logs are seen in the log _file.I can only see the following logs after the connection is closed. I am calling updateValue method on the line "set device state externally from device".
` set device state externally from device true
set device state externally from device false
HAP-NodeJS:EventedHTTPServer Currently 0 hap connections open: +1m
set device state externally from device true
set device state externally from device false
HAP-NodeJS:EventedHTTPServer Currently 0 hap connections open: +1m
HAP-NodeJS:EventedHTTPServer Currently 0 hap connections open: +1m
HAP-NodeJS:EventedHTTPServer Currently 0 hap connections open: +1m
``
You can also go through the full logs again.
`[info] "2023-04-11T10:45:16.637Z" 'Loading knx: KNXnet/IP protocol implementation for Node(>=4.x), version: 2.3.8'
HAP-NodeJS:Advertiser Initializing HAP-NodeJS v0.11.0 ... +0ms
HAP-NodeJS:Advertiser Preparing Advertiser for 'Infiware E3A1' using bonjour-hap backend! +0ms
HAP-NodeJS:EventedHTTPServer Server listening on [::]:47219 +0ms
HAP-NodeJS:Advertiser Starting to advertise 'Infiware E3A1' using bonjour-hap backend! +37ms
HAP-NodeJS:EventEmitter [::ffff:192.168.1.40] Registered event 'REQUEST' (total: 1) at EventedHTTPServer.onConnection (/usr/local/bin/11iot-server/iot-server/node_modules/hap-nodejs/src/lib/util/eventedhttp.ts:231:16) +0ms
HAP-NodeJS:EventEmitter [::ffff:192.168.1.40] Registered event 'AUTHENTICATED' (total: 1) at EventedHTTPServer.onConnection (/usr/local/bin/11iot-server/iot-server/node_modules/hap-nodejs/src/lib/util/eventedhttp.ts:234:16) +5ms
HAP-NodeJS:EventEmitter [::ffff:192.168.1.40] Registered event 'CLOSED' (total: 1) at EventedHTTPServer.onConnection (/usr/local/bin/11iot-server/iot-server/node_modules/hap-nodejs/src/lib/util/eventedhttp.ts:235:16) +8ms
HAP-NodeJS:EventedHTTPServer [::ffff:192.168.1.40] New connection from client on interface eth0 (::ffff:192.168.1.41) +2s
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] Internal HTTP server listening on 127.0.0.1:35125 +0ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] Internal HTTP socket connected. HAPConnection now fully set up! +15ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /pair-verify +13ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: POST /pair-verify +0ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] Pair verify step 1/2 +10ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +326ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /pair-verify +135ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: POST /pair-verify +450ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] Pair verify step 2/2 +2ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] Client 523AD553-C777-4854-B5D1-1F6CF096339D verification complete +86ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +99ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /accessories +17ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: GET /accessories +28ms
HAP-NodeJS:EventedHTTPServer [::ffff:192.168.1.40] Muting event '68.11' notification for this connection since it originated here. +632ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +34ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +48ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +82ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":68,"iid":11,"ev":true},{"aid":68,"iid":12,"ev":true},{"aid":68,"iid":10,"ev":true}]} +0ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "Position State" on "Infiware E3A1" for events +3ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "Target Position" on "Infiware E3A1" for events +1ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "Current Position" on "Infiware E3A1" for events +1ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +12ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] Client connection closed +5s
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP connection was closed +34ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP server was closed +3ms
HAP-NodeJS:EventEmitter [::ffff:192.168.1.40] Registered event 'REQUEST' (total: 1) at EventedHTTPServer.onConnection (/usr/local/bin/11iot-server/iot-server/node_modules/hap-nodejs/src/lib/util/eventedhttp.ts:231:16) +34s
HAP-NodeJS:EventEmitter [::ffff:192.168.1.40] Registered event 'AUTHENTICATED' (total: 1) at EventedHTTPServer.onConnection (/usr/local/bin/11iot-server/iot-server/node_modules/hap-nodejs/src/lib/util/eventedhttp.ts:234:16) +5ms
HAP-NodeJS:EventEmitter [::ffff:192.168.1.40] Registered event 'CLOSED' (total: 1) at EventedHTTPServer.onConnection (/usr/local/bin/11iot-server/iot-server/node_modules/hap-nodejs/src/lib/util/eventedhttp.ts:235:16) +4ms
HAP-NodeJS:EventedHTTPServer [::ffff:192.168.1.40] New connection from client on interface eth0 (::ffff:192.168.1.41) +34s
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] Internal HTTP server listening on 127.0.0.1:46315 +28s
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] Internal HTTP socket connected. HAPConnection now fully set up! +6ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /pair-verify +3ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: POST /pair-verify +34s
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] Pair verify step 1/2 +3ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +198ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /pair-verify +17ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: POST /pair-verify +212ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] Pair verify step 2/2 +3ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] Client 523AD553-C777-4854-B5D1-1F6CF096339D verification complete +151ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +168ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /accessories +21ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: GET /accessories +35ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +41ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +24ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +65ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":64,"iid":10,"ev":true}]} +34s
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "On" on "Infiware E3A1" for events +1ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +8ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +8ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +16ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":65,"iid":11,"ev":true},{"aid":65,"iid":10,"ev":true}]} +16ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "Rotation Speed" on "Infiware E3A1" for events +1ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "On" on "Infiware E3A1" for events +1ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +13ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +7ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +20ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":67,"iid":10,"ev":true}]} +17ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "On" on "Infiware E3A1" for events +1ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +8ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +7ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +15ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":66,"iid":10,"ev":true}]} +14ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "On" on "Infiware E3A1" for events +1ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +8ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +8ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +15ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":68,"iid":11,"ev":true},{"aid":68,"iid":12,"ev":true},{"aid":68,"iid":10,"ev":true}]} +14ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "Position State" on "Infiware E3A1" for events +2ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "Target Position" on "Infiware E3A1" for events +1ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "Current Position" on "Infiware E3A1" for events +1ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +9ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics?id=68.10,66.10,65.10,68.12,67.10,64.10,65.11 +8ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: GET /characteristics?id=68.10,66.10,65.10,68.12,67.10,64.10,65.11 +17ms
currentPosition GET: 0
HAP-NodeJS:Accessory [Infiware E3A1] Got Characteristic "Current Position" value: "0" +26ms
HAP-NodeJS:Accessory [Infiware E3A1] Got Characteristic "On" value: "0" +0ms
HAP-NodeJS:Accessory [Infiware E3A1] Got Characteristic "On" value: "0" +1ms
HAP-NodeJS:Accessory [Infiware E3A1] Got Characteristic "Target Position" value: "0" +0ms
HAP-NodeJS:Accessory [Infiware E3A1] Got Characteristic "On" value: "0" +1ms
HAP-NodeJS:Accessory [Infiware E3A1] Got Characteristic "On" value: "0" +0ms
HAP-NodeJS:Accessory [Infiware E3A1] Got Characteristic "Rotation Speed" value: "0" +0ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +23ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +8ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +31ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":67,"iid":10,"ev":true}]} +16ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +6ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +7ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +13ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":65,"iid":11,"ev":true},{"aid":65,"iid":10,"ev":true}]} +14ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +7ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +7ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +15ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":66,"iid":10,"ev":true}]} +14ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +7ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +7ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +13ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":68,"iid":11,"ev":true},{"aid":68,"iid":12,"ev":true},{"aid":68,"iid":10,"ev":true}]} +13ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +6ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +7ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +14ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":64,"iid":10,"ev":true}]} +21ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +14ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] Client connection closed +5s
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP connection was closed +3ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP server was closed +2ms
HAP-NodeJS:EventEmitter [::ffff:192.168.1.40] Registered event 'REQUEST' (total: 1) at EventedHTTPServer.onConnection (/usr/local/bin/11iot-server/iot-server/node_modules/hap-nodejs/src/lib/util/eventedhttp.ts:231:16) +12s
HAP-NodeJS:EventEmitter [::ffff:192.168.1.40] Registered event 'AUTHENTICATED' (total: 1) at EventedHTTPServer.onConnection (/usr/local/bin/11iot-server/iot-server/node_modules/hap-nodejs/src/lib/util/eventedhttp.ts:234:16) +3ms
HAP-NodeJS:EventEmitter [::ffff:192.168.1.40] Registered event 'CLOSED' (total: 1) at EventedHTTPServer.onConnection (/usr/local/bin/11iot-server/iot-server/node_modules/hap-nodejs/src/lib/util/eventedhttp.ts:235:16) +2ms
HAP-NodeJS:EventedHTTPServer [::ffff:192.168.1.40] New connection from client on interface eth0 (::ffff:192.168.1.41) +12s
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] Internal HTTP server listening on 127.0.0.1:33875 +7s
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] Internal HTTP socket connected. HAPConnection now fully set up! +5ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /pair-verify +3ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: POST /pair-verify +12s
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] Pair verify step 1/2 +3ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +112ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /pair-verify +18ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: POST /pair-verify +127ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] Pair verify step 2/2 +2ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] Client 523AD553-C777-4854-B5D1-1F6CF096339D verification complete +60ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +66ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /accessories +12ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: GET /accessories +16ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +23ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +24ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +47ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":64,"iid":10,"value":1}]} +12s
HAP-NodeJS:EventedHTTPServer [::ffff:192.168.1.40] Muting event '64.10' notification for this connection since it originated here. +275ms
HAP-NodeJS:Accessory [Infiware E3A1] Setting Characteristic "On" to value 1 +12ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +17ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +7ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +24ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":66,"iid":10,"ev":true}]} +12ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "On" on "Infiware E3A1" for events +1ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +4ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +6ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +11ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":65,"iid":11,"ev":true},{"aid":65,"iid":10,"ev":true}]} +10ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "Rotation Speed" on "Infiware E3A1" for events +0ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "On" on "Infiware E3A1" for events +1ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +4ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +6ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +9ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":67,"iid":10,"ev":true}]} +8ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "On" on "Infiware E3A1" for events +1ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +3ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +5ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +8ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":64,"iid":10,"ev":true}]} +7ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "On" on "Infiware E3A1" for events +1ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +4ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +5ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +9ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":68,"iid":11,"ev":true},{"aid":68,"iid":12,"ev":true},{"aid":68,"iid":10,"ev":true}]} +8ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "Position State" on "Infiware E3A1" for events +1ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "Target Position" on "Infiware E3A1" for events +0ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "Current Position" on "Infiware E3A1" for events +0ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +4ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +3s
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +3s
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":64,"iid":10,"value":0}]} +3s
HAP-NodeJS:EventedHTTPServer [::ffff:192.168.1.40] Muting event '64.10' notification for this connection since it originated here. +3s
HAP-NodeJS:Accessory [Infiware E3A1] Setting Characteristic "On" to value 0 +6ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +16ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] Client connection closed +5s
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP connection was closed +4ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP server was closed +2ms
HAP-NodeJS:EventEmitter [::ffff:192.168.1.40] Registered event 'REQUEST' (total: 1) at EventedHTTPServer.onConnection (/usr/local/bin/11iot-server/iot-server/node_modules/hap-nodejs/src/lib/util/eventedhttp.ts:231:16) +9s
HAP-NodeJS:EventEmitter [::ffff:192.168.1.40] Registered event 'AUTHENTICATED' (total: 1) at EventedHTTPServer.onConnection (/usr/local/bin/11iot-server/iot-server/node_modules/hap-nodejs/src/lib/util/eventedhttp.ts:234:16) +3ms
HAP-NodeJS:EventEmitter [::ffff:192.168.1.40] Registered event 'CLOSED' (total: 1) at EventedHTTPServer.onConnection (/usr/local/bin/11iot-server/iot-server/node_modules/hap-nodejs/src/lib/util/eventedhttp.ts:235:16) +3ms
HAP-NodeJS:EventedHTTPServer [::ffff:192.168.1.40] New connection from client on interface eth0 (::ffff:192.168.1.41) +6s
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] Internal HTTP server listening on 127.0.0.1:46007 +356ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] Internal HTTP socket connected. HAPConnection now fully set up! +5ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /pair-verify +2ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: POST /pair-verify +6s
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] Pair verify step 1/2 +3ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +100ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /pair-verify +17ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: POST /pair-verify +115ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] Pair verify step 2/2 +2ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] Client 523AD553-C777-4854-B5D1-1F6CF096339D verification complete +66ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +75ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /accessories +12ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: GET /accessories +19ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +19ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +23ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +42ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":64,"iid":10,"value":1}]} +6s
HAP-NodeJS:EventedHTTPServer [::ffff:192.168.1.40] Muting event '64.10' notification for this connection since it originated here. +266ms
HAP-NodeJS:Accessory [Infiware E3A1] Setting Characteristic "On" to value 1 +12ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +21ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +5ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +26ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":64,"iid":10,"ev":true}]} +14ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "On" on "Infiware E3A1" for events +1ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +5ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +5ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +10ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":66,"iid":10,"ev":true}]} +9ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "On" on "Infiware E3A1" for events +1ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +5ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +7ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +11ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":65,"iid":11,"ev":true},{"aid":65,"iid":10,"ev":true}]} +11ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "Rotation Speed" on "Infiware E3A1" for events +1ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "On" on "Infiware E3A1" for events +0ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +6ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +5ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +12ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":68,"iid":11,"ev":true},{"aid":68,"iid":12,"ev":true},{"aid":68,"iid":10,"ev":true}]} +10ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "Position State" on "Infiware E3A1" for events +1ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "Target Position" on "Infiware E3A1" for events +1ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "Current Position" on "Infiware E3A1" for events +1ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +8ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +5ms
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +12ms
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":67,"iid":10,"ev":true}]} +10ms
HAP-NodeJS:Accessory [::ffff:192.168.1.40] Registered Characteristic "On" on "Infiware E3A1" for events +1ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +5ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP request: /characteristics +2s
HAP-NodeJS:HAPServer [B6:B9:26:67:73:85] HAP Request: PUT /characteristics +2s
HAP-NodeJS:Accessory [Infiware E3A1] Processing characteristic set: {"characteristics":[{"aid":64,"iid":10,"value":0}]} +2s
HAP-NodeJS:EventedHTTPServer [::ffff:192.168.1.40] Muting event '64.10' notification for this connection since it originated here. +2s
HAP-NodeJS:Accessory [Infiware E3A1] Setting Characteristic "On" to value 0 +12ms
HAP-NodeJS:EventedHTTPServer Currently 1 hap connections open: ::ffff:192.168.1.40:49200 +6ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP Response is finished +25ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] Client connection closed +5s
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP connection was closed +4ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.40] HTTP server was closed +2ms
set device state externally from device true
set device state externally from device false
HAP-NodeJS:EventedHTTPServer Currently 0 hap connections open: +1m
set device state externally from device true
set device state externally from device false
HAP-NodeJS:EventedHTTPServer Currently 0 hap connections open: +1m
HAP-NodeJS:EventedHTTPServer Currently 0 hap connections open: +1m
HAP-NodeJS:EventedHTTPServer Currently 0 hap connections open: +1m
`
from hap-nodejs.
commented on June 16, 2024
I have noticed that only bridged accessories does not update status but in case of single accessory status are updated and connections remains open. @NorthernMan54
from hap-nodejs.
NorthernMan54
commented on June 16, 2024
I had made a very long post the other day, but I think I forgot to hit enter
This is from my homebridge-tasmota plugin, demonstrating event notifications working correctly. This is from within homebridge, so it is a bridged accessory.
Opening the Home App to the Room with the device
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.62] HTTP request: /characteristics +9s
HAP-NodeJS:HAPServer [AA:BB:CC:DD:EE:02] HAP Request: PUT /characteristics +9s
HAP-NodeJS:Accessory [Heisenberg 1F10] Processing characteristic set: {"characteristics":[{"aid":4,"iid":10,"ev":true},{"aid":4,"iid":11,"ev":true},{"aid":4,"iid":14,"ev":true}]} +0ms
HAP-NodeJS:Accessory [::ffff:192.168.1.62] Registered Characteristic "On" on "Heisenberg 1F10" for events +1ms
HAP-NodeJS:Accessory [::ffff:192.168.1.62] Registered Characteristic "Configured Name" on "Heisenberg 1F10" for events +1ms
HAP-NodeJS:Accessory [::ffff:192.168.1.62] Registered Characteristic "Outlet In Use" on "Heisenberg 1F10" for events +0ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.62] HTTP Response is finished +5ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.62] HTTP request: /characteristics +4ms
HAP-NodeJS:HAPServer [AA:BB:CC:DD:EE:02] HAP Request: PUT /characteristics +9ms
HAP-NodeJS:Accessory [Heisenberg 1F10] Processing characteristic set: {"characteristics":[{"aid":5,"iid":10,"ev":true},{"aid":5,"iid":11,"ev":true},{"aid":5,"iid":14,"ev":true},{"aid":5,"iid":15,"ev":true},{"aid":5,"iid":16,"ev":true}]} +6ms
HAP-NodeJS:Accessory [::ffff:192.168.1.62] Registered Characteristic "On" on "Heisenberg 1F10" for events +0ms
HAP-NodeJS:Accessory [::ffff:192.168.1.62] Registered Characteristic "Configured Name" on "Heisenberg 1F10" for events +0ms
HAP-NodeJS:Accessory [::ffff:192.168.1.62] Registered Characteristic "On" on "Heisenberg 1F10" for events +0ms
HAP-NodeJS:Accessory [::ffff:192.168.1.62] Registered Characteristic "Rotation Speed" on "Heisenberg 1F10" for events +0ms
HAP-NodeJS:Accessory [::ffff:192.168.1.62] Registered Characteristic "Configured Name" on "Heisenberg 1F10" for events +0ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.62] HTTP Response is finished +2ms
Home App Requesting Status of Devices
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.62] HTTP request: /characteristics?id=4.10,5.10,5.14,5.15 +129ms
HAP-NodeJS:HAPServer [AA:BB:CC:DD:EE:02] HAP Request: GET /characteristics?id=4.10,5.10,5.14,5.15 +132ms
HAP-NodeJS:Accessory [Heisenberg 1F10] Got Characteristic "On" value: "1" +132ms
HAP-NodeJS:Accessory [Heisenberg 1F10] Got Characteristic "On" value: "0" +0ms
HAP-NodeJS:Accessory [Heisenberg 1F10] Got Characteristic "On" value: "0" +0ms
HAP-NodeJS:Accessory [Heisenberg 1F10] Got Characteristic "Rotation Speed" value: "0" +0ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.62] HTTP Response is finished +4ms
Local Control of the accessory
Tasmota:mqtt emit tasmota_F52066/tele/STATE {"Time":"2023-04-11T23:46:24","Uptime":"1T03:58:09","UptimeSec":100689,"Heap":26,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":2,"POWER":"OFF","Wifi":{"AP":2,"SSId":"The_Beach","BSSId":"20:C9:D0:1A:CA:85","Channel":1,"Mode":"11n","RSSI":56,"Signal":-72,"LinkCount":1,"Downtime":"0T00:00:06"}} +19s
Tasmota:switch MQTT tasmota_F52066/tele/STATE {"Time":"2023-04-11T23:46:24","Uptime":"1T03:58:09","UptimeSec":100689,"Heap":26,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":2,"POWER":"OFF","Wifi":{"AP":2,"SSId":"The_Beach","BSSId":"20:C9:D0:1A:CA:85","Channel":1,"Mode":"11n","RSSI":56,"Signal":-72,"LinkCount":1,"Downtime":"0T00:00:06"}} +0ms
[Tasmota] Updating 'Washer Power:On' to false
Homebridge sending event notification of change in status
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.62] Sending HAP event notifications [ { aid: 4, iid: 10, value: 0 } ] +14s
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.62] HTTP request: /characteristics?id=4.10,5.14,5.15,5.10 +1s
HAP-NodeJS:HAPServer [AA:BB:CC:DD:EE:02] HAP Request: GET /characteristics?id=4.10,5.14,5.15,5.10 +15s
HAP-NodeJS:Accessory [Heisenberg 1F10] Got Characteristic "On" value: "0" +15s
HAP-NodeJS:Accessory [Heisenberg 1F10] Got Characteristic "On" value: "0" +0ms
HAP-NodeJS:Accessory [Heisenberg 1F10] Got Characteristic "Rotation Speed" value: "0" +0ms
HAP-NodeJS:Accessory [Heisenberg 1F10] Got Characteristic "On" value: "0" +0ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.62] HTTP Response is finished +3ms
Local Control of the accessory
Tasmota:mqtt emit tasmota_F52066/tele/STATE {"Time":"2023-04-11T23:46:29","Uptime":"1T03:58:14","UptimeSec":100694,"Heap":26,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":2,"POWER":"ON","Wifi":{"AP":2,"SSId":"The_Beach","BSSId":"20:C9:D0:1A:CA:85","Channel":1,"Mode":"11n","RSSI":50,"Signal":-75,"LinkCount":1,"Downtime":"0T00:00:06"}} +5s
Tasmota:switch MQTT tasmota_F52066/tele/STATE {"Time":"2023-04-11T23:46:29","Uptime":"1T03:58:14","UptimeSec":100694,"Heap":26,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":2,"POWER":"ON","Wifi":{"AP":2,"SSId":"The_Beach","BSSId":"20:C9:D0:1A:CA:85","Channel":1,"Mode":"11n","RSSI":50,"Signal":-75,"LinkCount":1,"Downtime":"0T00:00:06"}} +5s
[Tasmota] Updating 'Washer Power:On' to true
Homebridge sending event notification of change in status
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.62] Sending HAP event notifications [ { aid: 4, iid: 10, value: 1 } ] +4s
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.62] HTTP request: /characteristics?id=4.10,5.15,5.14,5.10 +1s
HAP-NodeJS:HAPServer [AA:BB:CC:DD:EE:02] HAP Request: GET /characteristics?id=4.10,5.15,5.14,5.10 +5s
HAP-NodeJS:Accessory [Heisenberg 1F10] Got Characteristic "On" value: "1" +5s
HAP-NodeJS:Accessory [Heisenberg 1F10] Got Characteristic "Rotation Speed" value: "0" +0ms
HAP-NodeJS:Accessory [Heisenberg 1F10] Got Characteristic "On" value: "0" +0ms
HAP-NodeJS:Accessory [Heisenberg 1F10] Got Characteristic "On" value: "0" +0ms
HAP-NodeJS:EventedHTTPServer:Connection [::ffff:192.168.1.62] HTTP Response is finished +3ms
from hap-nodejs.
commented on June 16, 2024
This is how I publish
Homebridge bridge accessory
class HomeBridgeService {
constructor(userName, pincode, deviceList = []) {
this.deviceList = deviceList
this.userName = userName
this.pincode = pincode
// this.setupId = setupId
this.bridgeAccessory = new Accessory(" Bridge Accessory", hap.uuid.generate(" bridge"))
this.bridgeAccessory._isBridge = true
this.addBridgedAccessories()
this.publishAccessories()
}
addBridgedAccessories = () => {
this.accessories = this.createAccessories()
this.bridgeAccessory.addBridgedAccessories(this.accessories.map(accessory => accessory.getAccessory()))
}
createAccessories = () => {
return this.deviceList.map(device => this.createAccessory(device))
}
createAccessory = (device) => {
switch (device.type) {
case 'light':
return new LightBulbAccessory(device.name, device.uuid, device.attribute, ['dim', 'ramp'].includes(device.attribute), false)
case 'rgbLight':
return new LightBulbAccessory(device.name, device.uuid,'rgbLight', true, true)
case 'fan':
return new FanAccessory(device.name, device.uuid, device.attribute)
case 'shutter':
return new WindowCoveringAccessory(device.name, device.uuid, device.attribute)
case 'AC':
case 'ACIntesis':
return new HVACAccessory(device.name, device.uuid, device.attribute)
}
}
publishAccessories = () => this.bridgeAccessory.publish({
username: this.userName,
pincode: this.pincode,
// setupID:this.setupId,
port: 47219,
category: this.bridgeAccessory.category
})
setAccessoryState = (deviceId, type, status) => {
const accessory = this.accessories.find(accessory1 => accessory1.uuid == deviceId)
if(accessory==undefined||accessory==null) {return}
switch (accessory.type) {
case 'light':
// const attrib = type == 'switch' ? value ? 'ON' : 'OFF' : 'RAMP'
accessory.setAccessoryState(type, status)
break
case 'rgbLight':
const rgbLightAttrib = ''
accessory.setAccessoryState(rgbLightAttrib, status)
break
case 'fan':
const fanAttrib = ''
accessory.setAccessoryState(fanAttrib, status)
break
case 'shutter':
const shutterAttrib = ''
accessory.setAccessoryState(shutterAttrib, status)
break
case 'AC':
case 'ACIntesis':
accessory.setAccessoryState(type, status)
break
}
}
}`
from hap-nodejs.
ebaauw
commented on June 16, 2024
Make sure to power-cycle your home hub(s), especially when on the new HomeKit architecture. Under the old architecture, each Apple device running HomeKit would connect to each accessory (or bridge) directly, under the new architecture, the Apple devices only connect through the home hub. So for changes, the accessory (through Homebridge) notifies the home hub, and the home hub notifies the HomeKit on your phone.
from hap-nodejs.
commented on June 16, 2024
when I publish single accessory I get updates without closing and opening the Homekit app.Only in case of bridge accessory I am unable to get the status.
from hap-nodejs.
NorthernMan54
commented on June 16, 2024
Pls share a link to your GitHub repo.
from hap-nodejs.
github-actions
commented on June 16, 2024
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
from hap-nodejs.
github-actions
commented on June 16, 2024
This issue has been closed as no further activity has occurred.
from hap-nodejs.
mrjackyliang
commented on June 16, 2024
This looks like the same exact issue that I'm having.
from hap-nodejs.
Related Issues (20)
- handleSnapshotRequest reason sometimes passed in as "undefined" HOT 2
- allow to specify a different IP in mDSN advertisement HOT 2
- Special Characters in Name HOT 6
- Node 16 to 18 update - Alpine - Docker - Synology
- node.js update HOT 1
- Node.js Update HOT 1
- Minimum Current Ambient Light Level warning HOT 1
- Lot of mDNS queries HOT 7
- Test permissions on "persist" storage location before publish
- `updateCharacteristic` won't work after `Client connection closed` HOT 11
- "ControllerStorage for accessory XXX was already initialized!" HOT 1
- How to run HAP-NodeJS inside Docker container HOT 5
- How to update the device status HOT 5
- TypeError: crypto_1.default.getCiphers is not a function at Object../node_modules/hap-nodejs/dist/lib/util/hapCrypto.js HOT 6
- v0.11.0 fails on Synology HOT 15
- VOC Density characteristic incorrectly set as a float and limited to 1000 HOT 4
- Setting Characteristic minValue via setProps results in debug error if the current value is lower than the new minValue HOT 6
- TypeScript plugins do not build with noImplicitAny: true in 1.6.0 HOT 11
- Interpreting Siri Commands HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from hap-nodejs.