askovi
commented
4 years ago Click on Reset Connection from the Help menu in the top right corner then rescan the QR code in the Dasboard.
Closed fizulnizam closed 4 years ago
askovi
commented
4 years ago Click on Reset Connection from the Help menu in the top right corner then rescan the QR code in the Dasboard.
fizulnizam
commented
4 years ago That did not worked.... my HOOBS still crash whenever I check the status of the Fan in the Google Home App....
Description I use the Google Smart Home (GSH) plugin with HOOBS, and installed it correctly like how the installation process mentioned, but when I go into the Google Home App on my phone and press of the appliance that I have which runs on the Broadlink RM Mini 3 via homebridge-broadlink-rm plugin, my HOOBS crashes. If I just press "On" or "Off", it works fine. Just crashing whenever I press on the appliance icon to check the status.
Expected behaviour I can see whether the accessory is on or off, in Google Home app on my phone.
Plugin name homebridge-gsh by oznu.
Please report the issue to the plugin developer I have already reported to the developer but he/she redirected this issue to you.
Version 3.2.6
Did you upgrade Please let us know if you upgraded from a previous version.
Pervious version If you upgraded, please let us know your previous version.
Did you originally upgrade to HOOBS 3 from HOOBS 2.1.1? Did you perform an upgrade from HOOBS 2.1.1? Some things are different.
What device are you using? Please let us know the device you are running HOOBS on.
If this is a custom install, what's your operating system? Raspbian on a Pi Zero W
Post your config
Post your log You can get the log from the intercafe. This is in the Log section.
Additional context When I want to check the status of the appliance, HOOBS crashes with the following error in the log:
[Google Smart Home] Received QUERY intent 30/05/2020, 18:54:22 TypeError: log is not a function at Name.getName (/home/hoobs/.hoobs/node_modules/homebridge-platform-helper/dist/serviceManager.js:69:9) at Name.emit (events.js:223:5) at Name.EventEmitter.emit (/usr/local/lib/node_modules/@hoobs/hoobs/node_modules/hap-nodejs/dist/lib/EventEmitter.js:59:38) at Name.Characteristic._this.getValue (/usr/local/lib/node_modules/@hoobs/hoobs/node_modules/hap-nodejs/dist/lib/Characteristic.js:190:23) at /usr/local/lib/node_modules/@hoobs/hoobs/node_modules/hap-nodejs/dist/lib/Accessory.js:753:32 at Array.forEach (<anonymous>:null:null) at Bridge.Accessory._this._handleGetCharacteristics (/usr/local/lib/node_modules/@hoobs/hoobs/node_modules/hap-nodejs/dist/lib/Accessory.js:694:18) at HAPServer.emit (events.js:223:5) at HAPServer.EventEmitter.emit (/usr/local/lib/node_modules/@hoobs/hoobs/node_modules/hap-nodejs/dist/lib/EventEmitter.js:59:38) at HAPServer._this._handleCharacteristics (/usr/local/lib/node_modules/@hoobs/hoobs/node_modules/hap-nodejs/dist/lib/HAPServer.js:664:23) at IncomingMessage.<anonymous> (/usr/local/lib/node_modules/@hoobs/hoobs/node_modules/hap-nodejs/dist/lib/HAPServer.js:227:39) at IncomingMessage.emit (events.js:223:5) at endReadableNT (_stream_readable.js:1185:12) at processTicksAndRejections (internal/process/task_queues.js:81:21) 30/05/2020, 18:54:22 Got SIGTERM, shutting down Bridge... 30/05/2020, 18:54:22 (node:29250) UnhandledPromiseRejectionWarning: Error: socket hang up 30/05/2020, 18:54:22 at connResetException (internal/errors.js:570:14) 30/05/2020, 18:54:22 at Socket.socketOnEnd (_http_client.js:440:23) 30/05/2020, 18:54:22 at Socket.emit (events.js:228:7) 30/05/2020, 18:54:22 at endReadableNT (_stream_readable.js:1185:12) 30/05/2020, 18:54:22 at processTicksAndRejections (internal/process/task_queues.js:81:21) 30/05/2020, 18:54:22 (node:29250) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) 30/05/2020, 18:54:22 (node:29250) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. 30/05/2020, 18:54:41 [Refresh Services] connect ECONNREFUSED 127.0.0.1:51826 30/05/2020, 18:54:41 [Refresh Services] connect ECONNREFUSED 127.0.0.1:51826 30/05/2020, 18:54:41 [Refresh Services] connect ECONNREFUSED 127.0.0.1:51826 30/05/2020, 18:54:41 [Refresh Services] connect ECONNREFUSED 127.0.0.1:51826 30/05/2020, 18:54:41 [Refresh Services] connect ECONNREFUSED 127.0.0.1:51826 30/05/2020, 18:54:41 [Refresh Services] connect ECONNREFUSED 127.0.0.1:51826 30/05/2020, 18:54:41 [Refresh Services] connect ECONNREFUSED 127.0.0.1:51826