newt10/homebridge-broadlink-rm-enhanced

Unable to Change Oscillation for Current Fan Speed

Closed this issue · 1 comments

When I enable/disable the oscillation on any specific fan speed, it prints a very long error in the logs. In order to apply the oscillation right now, I have to switch fan speed to something else and return back to what it was and then it works.

(node:28569) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'length' of undefined
at /usr/local/lib/node_modules/homebridge-broadlink-rm-enhanced/accessories/accessory.js:52:40
at catchDelayCancelError (/usr/local/lib/node_modules/homebridge-broadlink-rm-enhanced/helpers/catchDelayCancelError.js:8:20)
at FanAccessory.performSend (/usr/local/lib/node_modules/homebridge-broadlink-rm-enhanced/accessories/accessory.js:50:11)
at FanAccessory.setSwingMode (/usr/local/lib/node_modules/homebridge-broadlink-rm-enhanced/accessories/fan.js:132:16)
at FanAccessory.setCharacteristicValue (/usr/local/lib/node_modules/homebridge-broadlink-rm-enhanced/base/accessory.js:138:10)
at SwingMode.emit (events.js:315:20)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/Characteristic.js:867:47
at new Promise (:null:null)
at SwingMode. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/Characteristic.js:865:51)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
at Object.next (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:124:57)
at /usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:117:75
at new Promise (:null:null)
at Object.__awaiter (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:113:16)
at SwingMode.Characteristic.handleSetRequest (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/Characteristic.js:791:24)
at Bridge. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/Accessory.js:1534:58)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
at Object.next (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:124:57)
at /usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:117:75
at new Promise (:null:null)
at Object.__awaiter (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:113:16)
at Bridge.Accessory.handleCharacteristicWrite (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/Accessory.js:1454:24)
at _loop_2 (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/Accessory.js:1414:20)
at Bridge.Accessory.handleSetCharacteristics (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/Accessory.js:1442:17)
at HAPServer.emit (events.js:315:20)
at HAPServer.handleCharacteristics (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/HAPServer.js:779:18)
at IncomingMessage. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/HAPServer.js:286:21)
at IncomingMessage.emit (events.js:327:22)
at endReadableNT (internal/streams/readable.js:1327:12)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

(Use node --trace-warnings ... to show where the warning was created)
(node:28569) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:28569) [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.