Coder Social home page Coder Social logo

homebridge-tv-cec's People

Contributors

dominick-han avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

homebridge-tv-cec's Issues

Getting an error when trying to start homebridge

Here is my log:

[2019-4-9 02:52:46] Error: spawn cec-client ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)
at onErrorNT (internal/child_process.js:362:16)
at _combinedTickCallback (internal/process/next_tick.js:139:11)
at process._tickCallback (internal/process/next_tick.js:181:9)
at Function.Module.runMain (module.js:696:11)
at startup (bootstrap_node.js:204:16)
at bootstrap_node.js:625:3

My JSON file is also below:

{
"bridge": {
"name": "Homebridge",
"username": "CC:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154"
},

"description": "This is an example configuration file with one fake accessory and one fake platform. You can use this as a template for creating your own configuration file containing devices you actually own.",
"ports": {
	"start": 52100,
	"end": 52150,
	"comment": "This section is used to control the range of ports that separate accessory (like camera or television) should be bind to."
},
"accessories": [{}],

"platforms": [{
	"platform": "CEC",
	"sources": [{
			"name": "Raspberry Pi",
			"address": "2.0.0.0"
		},
		{
			"platform": "Camera-ffmpeg",
			"cameras": [{
				"name": "BasementCam",
				"videoConfig": {
					"source": "-f v4l2 -r 30 -s 1280x720 -i /dev/video0",
					"maxStreams": 2,
					"maxWidth": 1280,
					"maxHeight": 720,
					"maxFPS": 30,
					"vcodec": "h264_omx"
				}
			}]
		}
	]

}]

}

Switch to "television service"

As IOS 12.2 is finally released, would it be possible to implement the new television service into this plugin instead of switch service? Volume and source selection could also be implemented over cec protocol.

Failed to create symbolic link '/usr/bin/cec-client'

I have installed CEC Client with "sudo apt-get install cec-utils” through my Homebridge Terminal

However when I run "sudo ln -s /usr/osmc/bin/cec-client-4.0.2 /usr/bin/cec-client” to link as per the guide I get the following:

pi@homebridge:/var/lib/homebridge $ sudo ln -s /usr/osmc/bin/cec-client-4.0.2 /usr/bin/cec-client
ln: failed to create symbolic link '/usr/bin/cec-client': File exists

When I manually try to run - "cec-client -d 8”

I get:

pi@homebridge:/var/lib/homebridge $ cec-client -d 8
log level set to 8
No device type given. Using 'recording device'
CEC Parser created - libCEC version 4.0.7
no serial port given. trying autodetect:
path: Raspberry Pi
com port: RPI

opening a connection to the CEC adapter...
unable to open the device on port RPI
pi@homebridge:/var/lib/homebridge $

My Log keeps having the following error which is crashing the whole Homebridge:

[28/11/2021, 16:23:33] [Living Room TV] Initializing TVCECControl platform...
[28/11/2021, 16:23:33] [Living Room TV] Initializing TV service
[28/11/2021, 16:23:33] [Living Room TV] Hooking into cec-client process
[28/11/2021, 16:23:34] TypeError: Cannot read property 'inputNumber' of undefined
at /usr/local/lib/node_modules/homebridge-cec-tv-control/src/platform.ts:587:29
at Array.forEach ()
at CECTVControl.setupInputSources (/usr/local/lib/node_modules/homebridge-cec-tv-control/src/platform.ts:584:17)
at new CECTVControl (/usr/local/lib/node_modules/homebridge-cec-tv-control/src/platform.ts:403:10)
at /usr/local/lib/node_modules/homebridge/src/server.ts:440:40
at Array.forEach ()
at Server.loadPlatforms (/usr/local/lib/node_modules/homebridge/src/server.ts:372:27)
at Server.start (/usr/local/lib/node_modules/homebridge/src/server.ts:159:29)
[28/11/2021, 16:23:34] Got SIGTERM, shutting down Homebridge...
[28/11/2021, 16:23:39] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[28/11/2021, 16:23:44] [HB Supervisor] Restarting Homebridge...
[28/11/2021, 16:23:44] [HB Supervisor] Starting Homebridge with extra flags: -I
[28/11/2021, 16:23:44] [HB Supervisor] Started Homebridge v1.3.4 with PID: 11082
Initializing HAP-NodeJS v0.9.4…

Any ideas @dominick-han ?

Many thanks in advance,
Alex

fail to work with systemd

Hi

I'm running homebridge on Rpi 3 and configure to run it with systemd.

The only way that I success to run this plugin and switch inputs, Only when i run:

~ $ homebridge -U /var/homebridge/

But If homebridge is runing as usual with homebridge service,
When I want to switch Input from the app, I get an error and hombridge crush

Log:

Oct 20 15:51:35 Homebridge_RPI systemd[1]: Started Node.js HomeKit Server.
Oct 20 15:51:38 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:38] Loaded config.json with 1 accessories and 2 platforms.
Oct 20 15:51:38 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:38] ---
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:39] Loaded plugin: homebridge-config-ui-x
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:39] Registering platform 'homebridge-config-ui-x.config'
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:39] ---
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:39] Loaded plugin: homebridge-hdmi-cec
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:39] Registering platform 'homebridge-hdmi-cec.CEC'
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:39] ---
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:39] Loading 2 platforms...
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:39] [Config] Initializing config platform...
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:39] [Config] Spawning homebridge-config-ui-x with PID 6966
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:39] [CEC] Initializing CEC platform...
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:39] [CEC] Initializing platform accessory 'TV'...
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:39] [CEC] Initialized Power Switch
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:39] [CEC] Initializing platform accessory 'Apple TV'...
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:39] [CEC] Initialized Source: Apple TV at 10:00
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:39] [CEC] Initializing platform accessory 'HDMI Switcher'...
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:39] [CEC] Initialized Source: HDMI Switcher at 20:00
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:39] [CEC] Initializing platform accessory 'Yes'...
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:39] [CEC] Initialized Source: Yes at 30:00
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:39] [CEC] Initializing platform accessory 'HDMI Side'...
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:39] [CEC] Initialized Source: HDMI Side at 40:00
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: Setup Payload:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: X-HM://0023ISK4UD3O0
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: Scan this code with your HomeKit app on your iOS device to pair with Homebridge:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: Or enter this code with your HomeKit app on your iOS device to pair with Homebridge:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: ┌────────────┐
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: │ 333-22-999 │
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: └────────────┘
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]:
Oct 20 15:51:39 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:39] Homebridge is running on port 51826.
Oct 20 15:51:45 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:45] [Config] Using Form Authentication
Oct 20 15:51:45 Homebridge_RPI homebridge[6946]: [2018-10-20 15:51:45] [Config] Console v3.8.11 is listening on port 8080.

############## HERE I PRESS THE IPNUT BUTTON FROM THE APP ################

Oct 20 15:52:01 Homebridge_RPI homebridge[6946]: Error: This socket is closed
Oct 20 15:52:01 Homebridge_RPI homebridge[6946]: at Socket._writeGeneric (net.js:733:18)
Oct 20 15:52:01 Homebridge_RPI homebridge[6946]: at Socket._write (net.js:787:8)
Oct 20 15:52:01 Homebridge_RPI homebridge[6946]: at doWrite (_stream_writable.js:396:12)
Oct 20 15:52:01 Homebridge_RPI homebridge[6946]: at writeOrBuffer (_stream_writable.js:382:5)
Oct 20 15:52:01 Homebridge_RPI homebridge[6946]: at Socket.Writable.write (_stream_writable.js:290:11)
Oct 20 15:52:01 Homebridge_RPI homebridge[6946]: at Socket.write (net.js:711:40)
Oct 20 15:52:01 Homebridge_RPI homebridge[6946]: at Source.setState (/usr/lib/node_modules/homebridge-hdmi-cec/index.js:175:20)
Oct 20 15:52:01 Homebridge_RPI homebridge[6946]: at emitMany (events.js:147:13)
Oct 20 15:52:01 Homebridge_RPI systemd[1]: homebridge.service: Main process exited, code=exited, status=1/FAILURE
Oct 20 15:52:01 Homebridge_RPI systemd[1]: homebridge.service: Unit entered failed state.
Oct 20 15:52:01 Homebridge_RPI systemd[1]: homebridge.service: Failed with result 'exit-code'.
Oct 20 15:52:11 Homebridge_RPI systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
Oct 20 15:52:11 Homebridge_RPI systemd[1]: Stopped Node.js HomeKit Server.
Oct 20 15:52:11 Homebridge_RPI systemd[1]: Started Node.js HomeKit Server.

config.json file:

{

"bridge": {
"name": "Homebridge",
"username": "CC:2A:3B:E1:CE:3A",
"port": 51826,
"pin": "333-22-999"
},
"description": "My Home",
"platforms": [
{
"name": "Config",
"port": 8080,
"auth": "form",
"theme": "blue",
"restart": "sudo -n systemctl restart homebridge",
"tempUnits": "c",
"sudo": true,
"log": {
"method": "systemd",
"service": "homebridge"
},
"platform": "config"
},
{
"platform": "CEC",
"manufacturer": "Test",
"model": "V1.1",
"sources": [
{
"name": "Apple TV",
"manufacturer": "Apple Inc",
"model": "4K",
"address": "1.0.0.0"
},
{
"name": "HDMI Switcher",
"manufacturer": "Test",
"model": "Test",
"address": "2.0.0.0"
},
{
"name": "Yes",
"manufacturer": "Yes",
"model": "Max",
"address": "3.0.0.0"
},
{
"name": "HDMI Side",
"manufacturer": "Panasonic",
"model": "ST55",
"address": "4.0.0.0"
}
]
}
],
"accessories": [
{
}
]
}

Hope that anyone can help :)

Cannot call write after a stream was destroyed

Error happens when i try to turn on/off the TV.

[12/13/2019, 10:32:08 PM] [TV] Checking TV power status
[12/13/2019, 10:32:08 PM] Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
at doWrite (_stream_writable.js:411:19)
at writeOrBuffer (_stream_writable.js:399:5)
at Socket.Writable.write (_stream_writable.js:299:11)
at TV.getPowerStatus (/usr/local/lib/node_modules/homebridge-tv-cec/index.js:89:20)
at Characteristic.Active.emit (events.js:198:13)
at Characteristic.Active.Characteristic.getValue (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Characteristic.js:164:10)
at Bridge. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:771:20)
at Array.forEach ()
at Bridge.Accessory._handleGetCharacteristics (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:735:8)
at HAPServer.emit (events.js:198:13)
[12/13/2019, 10:32:08 PM] Got SIGTERM, shutting down Homebridge...

Below my CEC log:

hoobs@hoobs:~ $ cec-client -d 8
log level set to 8
No device type given. Using 'recording device'
CEC Parser created - libCEC version 4.0.4
no serial port given. trying autodetect:
path: Raspberry Pi
com port: RPI

opening a connection to the CEC adapter...
TRAFFIC: [ 357] << e0
TRAFFIC: [ 447] << e0
TRAFFIC: [ 539] << 11
TRAFFIC: [ 812] << 11
TRAFFIC: [ 1088] << 1f:84:20:00:01
TRAFFIC: [ 1243] << 10
TRAFFIC: [ 1336] << 10
TRAFFIC: [ 1432] << 10
TRAFFIC: [ 1525] << 10
waiting for input
TRAFFIC: [ 7789] >> 0f:87:00:e0:91
TRAFFIC: [ 7790] << 1f:87:00:15:82
TRAFFIC: [ 8030] << 1f:87:00:15:82
TRAFFIC: [ 22929] >> 0f:87:00:e0:91
TRAFFIC: [ 22929] << 1f:87:00:e0:91
TRAFFIC: [ 23173] << 1f:87:00:e0:91
TRAFFIC: [ 38086] >> 0f:87:00:e0:91
TRAFFIC: [ 38086] << 1f:87:00:e0:91
TRAFFIC: [ 38357] << 1f:87:00:e0:91
TRAFFIC: [ 53218] >> 0f:87:00:e0:91
TRAFFIC: [ 53218] << 1f:87:00:e0:91
TRAFFIC: [ 53609] << 1f:87:00:e0:91
TRAFFIC: [ 68371] >> 0f:87:00:e0:91
TRAFFIC: [ 68371] << 1f:87:00:e0:91
TRAFFIC: [ 68582] << 1f:87:00:e0:91
TRAFFIC: [ 83523] >> 0f:87:00:e0:91
TRAFFIC: [ 83523] << 1f:87:00:e0:91
TRAFFIC: [ 83764] << 1f:87:00:e0:91
TRAFFIC: [ 98658] >> 0f:87:00:e0:91
TRAFFIC: [ 98658] << 1f:87:00:e0:91
TRAFFIC: [ 98898] << 1f:87:00:e0:91

cec-client -d 1
log level set to 1
No device type given. Using 'recording device'
CEC Parser created - libCEC version 4.0.4
no serial port given. trying autodetect:
path: Raspberry Pi
com port: RPI

opening a connection to the CEC adapter...
waiting for input
scan
requesting CEC bus information ...
CEC bus information

device #1: Recorder 1
address: 2.0.0.0
active source: no
vendor: LG
osd string: CECTester
CEC version: 1.4
power status: on
language: eng

currently active source: unknown (-1)
cec-client -d 1
log level set to 1
No device type given. Using 'recording device'
CEC Parser created - libCEC version 4.0.4
no serial port given. trying autodetect:
path: Raspberry Pi
com port: RPI

opening a connection to the CEC adapter...
waiting for input
waiting for input
scan
requesting CEC bus information ...
CEC bus information

device #1: Recorder 1
address: 2.0.0.0
active source: no
vendor: LG
osd string: CECTester
CEC version: 1.4
power status: on
language: eng
waiting for input
waiting for input
waiting for input
waiting for input
waiting for input
waiting for input
waiting for input
waiting for input
requesting CEC bus information ...
^Csignal caught: 2 - exiting
CEC bus information

device #0: TV
address: 0.0.0.0
active source: no
vendor: LG
osd string: TV
CEC version: 1.3a
power status: unknown
language: eng

device #1: Recorder 1
address: 2.0.0.0
active source: no
vendor: LG
osd string: CECTester
CEC version: 1.3a
power status: on
language: eng

TV won't stay detected in home app

I have a Magnavox model "32ME303V/F7 A". I just installed your plugin. There are 2 HDMI ports and it seems to reliably switch to the one I select, but its status in the home app turns immediately back off even though it switched ports correctly. (Maybe that's what it's supposed to do?)

However, what's more is that the first time I tried turning the TV off, it immediately turned off, but the progress wheel on the icon kept spinning and the button grays out and gets an exclamation point. Further attempts to use it have no effect to either turn it on or off. I can't turn the tv on or off with the button in the home app. When I turn the TV off again with the remote, the button tells me the TV is on. If I hard-press on the button, it tells me there's no response from the device.

But then, sometimes, I can get the button to work. I cannot figure out a pattern, but suffice it to say, I cannot get the home app to reliably turn the TV on or off.

Homebridge shuts down after trying tu turn it off or on

I get this output:
Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed Feb 11 20:22:10 raspberrypi homebridge[4435]: at doWrite (_stream_writable.js:411:19) Feb 11 20:22:10 raspberrypi homebridge[4435]: at writeOrBuffer (_stream_writable.js:399:5) Feb 11 20:22:10 raspberrypi homebridge[4435]: at Socket.Writable.write (_stream_writable.js:299:11) Feb 11 20:22:10 raspberrypi homebridge[4435]: at Power.getState (/usr/local/lib/node_modules/homebridge-hdmi-cec/index.js:93:21) Feb 11 20:22:10 raspberrypi homebridge[4435]: at Characteristic.On.emit (events.js:197:13) Feb 11 20:22:10 raspberrypi homebridge[4435]: at Characteristic.On.Characteristic.getValue (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Characteristic.js:164:10) Feb 11 20:22:10 raspberrypi homebridge[4435]: at Bridge.<anonymous> (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:762:20) Feb 11 20:22:10 raspberrypi homebridge[4435]: at Array.forEach (<anonymous>) Feb 11 20:22:10 raspberrypi homebridge[4435]: at Bridge.Accessory._handleGetCharacteristics (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:726:8) Feb 11 20:22:10 raspberrypi homebridge[4435]: at HAPServer.emit (events.js:197:13) Feb 11 20:22:10 raspberrypi homebridge[4435]: [2/11/2019, 8:22:10 PM] Got SIGTERM, shutting down Homebridge...
any Help would be greatly appreciated.
Also my current config:
{ "bridge": { "name": "Homebridge", "username": "CC:22:3D:E3:CE:30", "port": 51826, "pin": "031-45-154" }, "accessories": [ ], "platforms": [ { "name": "Config", "port": 8080, "auth": "form", "theme": "blue", "tempUnits": "c", "sudo": true, "log": { "method": "custom", "command": "sudo journalctl -u homebridge" }, "platform": "config" }, { "platform": "Hue", "users": { "001788FFFEAE0E7D": "6KojUwv7OgVPDyR11Z5lv7mAz7TezInT7iq-yp6N" }, "lights": true }, { "platform": "ZP", "service": "fan" }, { "platform": "CEC", "sources": [ { "name": "Samsung", "address": "0.0.0.0" } ] } ] }

New power state is not retrieved correctly after state change

Hi all, I've only just installed this plugin, but am having an issue with the detection of the new power state of the TV after changing the state using the Home app.

Take the below output as an example of the issue:

*toggle power On in Home app*
[5/20/2020, 12:16:51] [TV] Turning TV on
[5/20/2020, 12:17:21] [TV] TV is not turning on
*TV is marked as 'No Response' in the Home app*
*close and reopen Home app*
[5/20/2020, 12:17:43] [TV] Checking TV power status
[5/20/2020, 12:17:43] [TV] TV is on

The state is not detected correctly after changing until closing and reopening the Home app, forcing a re-check.

The same is true of toggling the power Off:

*toggle power Off in Home app*
[5/20/2020, 12:17:54] [TV] Turning TV fff
[5/20/2020, 12:18:24] [TV] TV is not turning off
*TV is marked as 'No Response' in the Home app*
*close and reopen Home app*
[5/20/2020, 12:19:28] [TV] Checking TV power status
[5/20/2020, 12:19:29] [TV] TV is off

Unfortunately I am not familiar enough with nodeJS to make the change myself, but is there a way to call the getPowerStatus() and return that result at the end of setPowerStatus()?

Panasonic viera link issues

Hi Dominick, any chance to get his plugin work with panasonic viera link TV? Since previous plugin homebridge-hdmi-cec works just fine, using this one I am not able to control tv at all.
Can you please take a quick look at it?
Thanks

panasonic TX-55DX603E
Here is my log:

log level set to 8
No device type given. Using 'recording device'
CEC Parser created - libCEC version 4.0.4
no serial port given. trying autodetect:
path: Raspberry Pi
com port: RPI

opening a connection to the CEC adapter...
TRAFFIC: [ 182] << e0
TRAFFIC: [ 242] << e0:8c
TRAFFIC: [ 489] >> 0f:87:00:80:45
TRAFFIC: [ 489] << 44
TRAFFIC: [ 819] << 88
TRAFFIC: [ 1089] << 88
TRAFFIC: [ 1360] << 8f:84:30:00:04
TRAFFIC: [ 1512] << 80:47:43:45:43:54:65:73:74:65:72
TRAFFIC: [ 1812] << 80:8f
TRAFFIC: [ 1980] >> 08:00:47:00
TRAFFIC: [ 2242] >> 08:90:01
waiting for input
TRAFFIC: [ 2437] >> 08:89:10:01:05
TRAFFIC: [ 3039] >> 08:a0:00:80:45:06:05
TRAFFIC: [ 4289] >> 08:a0:00:80:45:06:05
TRAFFIC: [ 5539] >> 08:a0:00:80:45:06:05
tx 10:04
TRAFFIC: [ 9561] << 10:04
TRAFFIC: [ 9939] >> 0f:a0:00:80:45:20:00:01
waiting for input
TRAFFIC: [ 11062] << 80:89:10:02:ff:ff:00:05:05:45:55:5c:58:32
TRAFFIC: [ 541826] >> 0f:82:00:00
TRAFFIC: [ 542667] >> 0f:80:00:00:10:00
TRAFFIC: [ 543022] >> 0f:82:00:00
TRAFFIC: [ 543484] >> 0f:80:10:00:20:00
TRAFFIC: [ 543822] >> 4f:a6:06:10:56:10
TRAFFIC: [ 543969] >> 4f:84:10:00:04
TRAFFIC: [ 544045] >> 4f:85
TRAFFIC: [ 544172] >> 0f:86:20:00
TRAFFIC: [ 544260] >> 4f:90:01
TRAFFIC: [ 544647] >> 0f:84:00:00:00
TRAFFIC: [ 544647] << 8f:84:30:00:04
TRAFFIC: [ 545372] >> 4f:87:00:10:fa
TRAFFIC: [ 546075] >> 08:8c
TRAFFIC: [ 546075] << 8f:87:00:80:45
TRAFFIC: [ 546549] >> 08:89:10:01:05
TRAFFIC: [ 546549] << 80:89:10:02:ff:ff:00:05:05:45:55:5c:58:32
TRAFFIC: [ 547500] >> 08:a0:00:80:45:06:05
TRAFFIC: [ 548749] >> 08:a0:00:80:45:06:05
TRAFFIC: [ 549999] >> 08:a0:00:80:45:06:05
TRAFFIC: [ 561338] >> 0f:82:00:00
TRAFFIC: [ 561571] >> 0f:80:20:00:10:00
TRAFFIC: [ 562226] >> 0f:86:10:00
TRAFFIC: [ 562698] >> 4f:a6:06:10:56:10
TRAFFIC: [ 562845] >> 4f:84:10:00:04
TRAFFIC: [ 562921] >> 4f:85
TRAFFIC: [ 563026] >> 4f:90:01
TRAFFIC: [ 563482] >> 0f:84:00:00:00
TRAFFIC: [ 563482] << 8f:84:30:00:04
TRAFFIC: [ 564366] >> 4f:90:00
TRAFFIC: [ 564644] >> 4f:82:10:00
TRAFFIC: [ 564975] >> 4f:87:00:10:fa
TRAFFIC: [ 565425] >> 08:8c
TRAFFIC: [ 565425] << 8f:87:00:80:45
TRAFFIC: [ 565902] >> 08:89:10:01:05
TRAFFIC: [ 565903] << 80:89:10:02:ff:ff:00:05:05:45:55:5c:58:32
TRAFFIC: [ 566854] >> 08:a0:00:80:45:06:05
TRAFFIC: [ 568100] >> 08:a0:00:80:45:06:05
TRAFFIC: [ 569354] >> 08:a0:00:80:45:06:05
TRAFFIC: [ 576684] >> 0f:82:00:00

use the home app control the tv only "on" work

I AM SOORY,
my english so bad,
but i need your help
Uploading Snipaste_2019-05-04_20-28-23.png…
use the home app control the tv only "on" work
but use the entity remote control the tv,it can feedback the tv circumstances in home app
my english so bad

Usually takes 2 tries

When I issue a command to Siri to either turn the TV on or off or switch HDMI inputs, Siri either:

  1. Fails at executing the command and she tells me it failed (e.g. Siri tries to turn on the TV and eventually tells me there was a problem)
  2. Fails at executing the command, but she thinks she succeeded (e.g. Siri tries to turn on the TV and thinks it turned on, but it didn't)

When I re-issue the same command to Siri, she either:

  1. Succeeds at executing the command but she tells me it failed (e.g. Siri tries to turn on the TV, the TV turns on, and Siri eventually tells me there was a problem)
  2. Succeeds at executing the command and she thinks she succeeded (e.g. Siri tries to turn on the TV, the TV turns on, and Siri confirms that the TV turned on)

It seems like, this occurs a couple times a day. After I've experienced the above behavior once, subsequent commands seem to work correctly until the next time I sit down to use the TV (say the next morning or after I get home from work).

What's the best way to debug what's going on here?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.