Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Can't receive token

See original GitHub issue

After clicking allow on tv pop up in log receive crash

Dec 04 22:12:47 raspberrypi homebridge[28113]: if (data.token) {
Dec 04 22:12:47 raspberrypi homebridge[28113]: ^
Dec 04 22:12:47 raspberrypi homebridge[28113]: TypeError: Cannot read property 'token' of undefined
Dec 04 22:12:47 raspberrypi homebridge[28113]: at WebSocket.socket.on (/usr/lib/node_modules/homebridge-samsung-tizen/lib/SamsungRemote.js:396:26)
Dec 04 22:12:47 raspberrypi homebridge[28113]: at emitOne (events.js:116:13)
Dec 04 22:12:47 raspberrypi homebridge[28113]: at WebSocket.emit (events.js:211:7)
Dec 04 22:12:47 raspberrypi homebridge[28113]: at Receiver.receiverOnMessage (/usr/lib/node_modules/homebridge-samsung-tizen/node_modules/ws/lib/websocket.js:720:20)
Dec 04 22:12:47 raspberrypi homebridge[28113]: at emitOne (events.js:116:13)
Dec 04 22:12:47 raspberrypi homebridge[28113]: at Receiver.emit (events.js:211:7)
Dec 04 22:12:47 raspberrypi homebridge[28113]: at Receiver.dataMessage (/usr/lib/node_modules/homebridge-samsung-tizen/node_modules/ws/lib/receiver.js:414:14)
Dec 04 22:12:47 raspberrypi homebridge[28113]: at Receiver.getData (/usr/lib/node_modules/homebridge-samsung-tizen/node_modules/ws/lib/receiver.js:346:17)
Dec 04 22:12:47 raspberrypi homebridge[28113]: at Receiver.startLoop (/usr/lib/node_modules/homebridge-samsung-tizen/node_modules/ws/lib/receiver.js:133:22)
Dec 04 22:12:47 raspberrypi homebridge[28113]: at Receiver._write (/usr/lib/node_modules/homebridge-samsung-tizen/node_modules/ws/lib/receiver.js:69:10)```

Issue Analytics

State:
Created 5 years ago
Comments:20 (8 by maintainers)

Top GitHub Comments

1reaction

tavicucommented, Dec 5, 2018

@JonoHaysom Strange … looks like your TV is not returning any info when you press “Allow”. I will get home in ~2 hours and will see then 😃

0reactions

tavicucommented, Dec 8, 2018

@JonoHaysom They are actually using a much slower method. I ping the IP which is very fast when on (~75ms) and when it’s off it has the minimum 1 second timeout of system.

Their method is sending a request to TV which takes 2 seconds when it’s OFF.

Anyway, i have implemented a timeout and now it will respond in less than 250ms 😃 It will go with the next release, probably tomorrow.

I will close this Issue since it was resolved