Open sushenmathur opened 5 years ago
Having this issue also with lights, seems that the setSaturation
method isn't defined
Me too, same error on air conditioner:
[2019-5-28 22:26:21] [Broadlink RM] Air Conditioner Advanced setCurrentHeatingCoolingState: 0 May 28 22:26:21 octopi homebridge[3484]: Unhandled Command: 114
Me too, same error on air conditioner: [2019-5-28 22:26:21] [Broadlink RM] Air Conditioner Advanced setCurrentHeatingCoolingState: 0 May 28 22:26:21 octopi homebridge[3484]: Unhandled Command: 114
Same exactly error. What are we doing bad? I only have two settings on A/C: "defaultCoolTemperature": 25, "defaultHeatTemperature": 23,
What can be the reason? thanks
Is everyone getting this error using an RM Mini? I've been looking around under the hood and this error seems to happen when receiving data back from the device - which, other than learning codes and the initial negotiation, doesn't happen to my knowledge on an RM Mini.
Hi , got the sema error on my RM Pro Plus. the only thing that has changes is a firmware upgrade on the RM. Any clue ?
Hey, this is due to receiving a command back from the RM devices that we don't recognise. I guess it's a new one. It anyone actually seeing issues because of it?
I'm seeing this too. I suspect Broadlink have added an acknowledgment response. I haven't been able to find anything to support this theory but I only see this on successful commands. i.e. If I send a code when the Broadlink is off the network I don't get this message.
Hello! Getting the same error on a successful command with my Broadlink RM Mini. Anybody has some ideas/insights?
Noticed the Error a couple of days ago as well. Using also RM Mini 3 Unhandled Command: 114
This morning I had a command fail to send at 5:30 which I then successfully resent at 5:34 by cycling the switch off then on again. The logs show no "Unhandled Command" for the failed command, but it's there for the successful one. This backs up my theory of it being a 'command sent' acknowledgement from the RM Mini.
Mar 11 05:29:57 homebridge[6738]: [Broadlink RM] Photo Frame getSwitchState: false
Mar 11 05:29:57 homebridge[6738]: [Broadlink RM] Photo Frame setSwitchState: true
Mar 11 05:29:57 homebridge[6738]: [Broadlink RM] Photo Frame sendHex (192.168.21.53; 34:ea:34:6f:bb:f7) 2600580000012996121411151213121312381213111312131239113912381238121312381239113812381238123812391238121312131213121312131214121311141238123812381200052200012b4b12000c560001294c12000d05
Mar 11 05:29:57 homebridge[6738]: [Broadlink RM] Photo Frame sendHex (192.168.21.53; 34:ea:34:6f:bb:f7) 2600580000012996121411151213121312381213111312131239113912381238121312381239113812381238123812391238121312131213121312131214121311141238123812381200052200012b4b12000c560001294c12000d05
Mar 11 05:34:10 homebridge[6738]: [Broadlink RM] Photo Frame getSwitchState: true
Mar 11 05:34:10 homebridge[6738]: [Broadlink RM] Photo Frame setSwitchState: false
Mar 11 05:34:10 homebridge[6738]: [Broadlink RM] Photo Frame sendHex (192.168.21.53; 34:ea:34:6f:bb:f7) 2600580000012996121411151213121312381213111312131239113912381238121312381239113812381238123812391238121312131213121312131214121311141238123812381200052200012b4b12000c560001294c12000d05
Mar 11 05:34:10 homebridge[6738]: [Broadlink RM] Photo Frame getSwitchState: false
Mar 11 05:34:10 homebridge[6738]: [Broadlink RM] Photo Frame setSwitchState: true
Mar 11 05:34:10 homebridge[6738]: [Broadlink RM] Photo Frame sendHex (192.168.21.53; 34:ea:34:6f:bb:f7) 2600580000012996121411151213121312381213111312131239113912381238121312381239113812381238123812391238121312131213121312131214121311141238123812381200052200012b4b12000c560001294c12000d05
Mar 11 05:34:10 homebridge[6738]: Unhandled Command: 114
Mar 11 05:34:11 homebridge[6738]: Unhandled Command: 114
It would be amazing if my theory could be confirmed and we could add a retry if a command is sent without acknowledgement.
Any updates on this issue?
Getting an error "Unhandled Command: 114" for command send using RM mini. Using the plugin for both RM pro and Rm mini, no error with RM pro.
A snippet of the log file
[2/11/2019, 11:22:25 AM] [Broadlink RM] Bed TV Volume Down sendHex (192.168.0.6; 78::0:F::77::1:9::F9::3:9) 260050000001289413121213121213121312131213121312133713371337133712371312133713371337133713371337121213121337131213121312131213121337133712131237130005440001264b13000d050000000000000000 Unhandled Command: 114 [2/11/2019, 11:22:25 AM] [Broadlink RM] Bed TV Volume Down sendHex (192.168.0.6; 78::0:F::77::1:9::F9::3:9) 260050000001289413121213121213121312131213121312133713371337133712371312133713371337133713371337121213121337131213121312131213121337133712131237130005440001264b13000d050000000000000000 Unhandled Command: 114 [2/11/2019, 11:22:26 AM] [Broadlink RM] Bed TV Volume Down sendHex (192.168.0.6; 78::0:F::77::1:9::F9::3:9) 260050000001289413121213121213121312131213121312133713371337133712371312133713371337133713371337121213121337131213121312131213121337133712131237130005440001264b13000d050000000000000000 [2/11/2019, 11:22:26 AM] [Broadlink RM] Bed TV Volume Down setSwitchState: (automatically turn off in 2.5 seconds) Unhandled Command: 114 [2/11/2019, 11:22:28 AM] [Broadlink RM] Bed TV Volume Down setSwitchState: false