TV automatically turning on early morning

This seems to be happening fairly regularly now (and has for some time), I’ve only noticed it again as I’m up early and doing something else and then heard my TV + AVR fire up after.

It seems to occur around 3.59am each day - is there a way I can see what’s causing the Vero V to wake up and therefore turn on my TV, Amp etc.?

Is the only way to get more insight to turn on log debugging and then wait till the next day to see what shows in the logs, or is there something in the standard logs I might be able to review?

I was getting this because I back up my Vero every night. When Kodi was restarted, the TV was turning on by CEC. Fixed it by disabling CEC on the TV (which I don’t use). If you turn on CEC debugging you may find something interesting.

I had a quick search but wasn’t able to work out how to turn on CEC debugging, sorry.

I did run cec-client though, I’m not sure if that’s of any help?

x@osmc:~$ cec-client
No device type given. Using 'recording device'
CEC Parser created - libCEC version 6.0.2
no serial port given. trying autodetect:
 path:     /dev/aocec
 com port: AOCEC

opening a connection to the CEC adapter...
DEBUG:   [              65]     Broadcast (F): osd name set to 'Broadcast'
NOTICE:  [              65]     connection opened
DEBUG:   [              66]     processor thread started
DEBUG:   [              66]     << Broadcast (F) -> TV (0): POLL
TRAFFIC: [              66]     << f0
DEBUG:   [              95]     >> POLL sent
DEBUG:   [              95]     TV (0): device status changed into 'present'
DEBUG:   [              95]     << requesting vendor ID of 'TV' (0)
TRAFFIC: [              95]     << f0:8c
DEBUG:   [            1159]     expected response not received (87: device vendor id)
TRAFFIC: [            1160]     << f0:8c
DEBUG:   [            2213]     expected response not received (87: device vendor id)
DEBUG:   [            2213]     registering new CEC client - v6.0.2
DEBUG:   [            2214]     SetClientVersion - using client version '6.0.2'
NOTICE:  [            2214]     setting HDMI port to 1 on device TV (0)
DEBUG:   [            2214]     SetConfiguration: double tap timeout = 200ms, repeat rate = 0ms, release delay = 500ms
DEBUG:   [            2214]     detecting logical address for type 'recording device'
DEBUG:   [            2214]     trying logical address 'Recorder 1'
DEBUG:   [            2214]     << Recorder 1 (1) -> Recorder 1 (1): POLL
TRAFFIC: [            2214]     << 11
WARNING: [            2244]     Write: write failed
TRAFFIC: [            2244]     << 11
WARNING: [            2283]     Write: write failed
DEBUG:   [            2283]     >> POLL not sent
DEBUG:   [            2283]     using logical address 'Recorder 1'
DEBUG:   [            2283]     Recorder 1 (1): device status changed into 'handled by libCEC'
DEBUG:   [            2283]     Recorder 1 (1): power status changed from 'unknown' to 'on'
DEBUG:   [            2283]     Recorder 1 (1): vendor = Pulse Eight (001582)
DEBUG:   [            2283]     Recorder 1 (1): CEC version 1.4
DEBUG:   [            2283]     AllocateLogicalAddresses - device '0', type 'recording device', LA '1'
DEBUG:   [            2284]     Recorder 1 (1): osd name set to 'CECTester'
DEBUG:   [            2284]     Recorder 1 (1): menu language set to 'eng'
DEBUG:   [            2284]     using auto-detected physical address 2300
DEBUG:   [            2284]     Recorder 1 (1): physical address changed from ffff to 2300
DEBUG:   [            2284]     << Recorder 1 (1) -> broadcast (F): physical address 2300
TRAFFIC: [            2284]     << 1f:84:23:00:01
NOTICE:  [            2420]     CEC client registered: libCEC version = 6.0.2, client version = 6.0.2, firmware version = 5, logical address(es) = Recorder 1 (1) , physical address: 2.3.0.0,  compiled on 2023-06-08 00:34:30 by root@osmc on Linux 4.9.269 (armv7l), features: P8_USB, DRM, P8_detect, AOCEC
DEBUG:   [            2420]     << Recorder 1 (1) -> TV (0): OSD name 'CECTester'
TRAFFIC: [            2420]     << 10:47:43:45:43:54:65:73:74:65:72
DEBUG:   [            2704]     << requesting power status of 'TV' (0)
TRAFFIC: [            2704]     << 10:8f
DEBUG:   [            3768]     expected response not received (90: report power status)
TRAFFIC: [            3768]     << 10:8f
waiting for input
DEBUG:   [            4769]     expected response not received (90: report power status)

FWIW I see the same, but not every night. Yes, I have CEC active. I normally use a small keyboard with Kodi, but it is convenient to use teh TV remote at times. I also back up the kodi config every night, but this all started when I go our new Vero V

Have you made any progress on this since then?

No, as I had no feedback on how to turn on CEC debugging.

I’ve since found another thread - which indicates turning on component specific for the libCEC library - is this what I need to keep on permanently and then post the log every day (in case it doesn’t happen every day)?

Yes, this is the exact way you can try. Perhaps, we get some more information for this scenario with this action. Since you don’t suffer from a hang/crash, you only need to transfer the debug log set when you find your TV active the next day/in morning without a reboot; by that way we also should have the matching system journal. Don’t forget to also provide the CEC config as descriped in this post. Thx.

PS: The times when you last switched off your TV and when you you’ve found your TV unexpected active are also nice to have.

Do I need to turn on debug logging, or can I just turn on the component-specific logging? It allows me to do the latter as verbose, without turning on debug logging, but not sure if it’ll capture those events or not. I’ve turned on debug logging for now, although I have just missed the window today.

CEC config is here: https://paste.osmc.tv/ofenebidep

I’m not sure how workable this logging will be though, other than to enable it every night and then check in the morning. Both my AVR + TV are set to power off after 30 minutes / 2 hours, so usually I don’t / won’t know when it happens as I’m usually asleep (tonight aside!).

Turning off those power saving features is maybe an option, but….. we’ve all seen the price of electricity these days! :wink:

I think that’s the way to go.

Is thee something in particular in the log I should look for? I assume there will be some timestamped events somewhere. By sheer (bad) luck last night, I was up doing some other work so sat in the room with the TV; it didn’t auto turn on. Doh.

No, just upload the debug logs once it has happened again and you find the TV running in the morning.

My Samsung tv used to do this until I disabled Samsung SmartThings (or something like that) app from my new Samsung phone. Apparently the app polled Samsung devices in the wee hours and fired the tv up.

Yesterday I connected an Android box to my TV and the setup routine asked me if I wanted to control the TV. Out of interest I chose ‘yes’ and it asked for the make of the TV. Now when I turn off any connected device or even restart Kodi (annoyingly) the TV turns off.

I suspect you need to look at the settings on your TV rather than the Vero. Though it’s still a mystery why it would turn on.

Just to note I’m no further in progressing troubleshooting on this one, but as a result of poor sleep lately the few nights I’ve been awake around the usual time I haven’t noticed it turn on, so the mystery remains! LG OLED, Samsung phone….. couldn’t find any obvious settings to check/change.