Philips TV (2016+) Binding

michaeljoos · August 28, 2023, 5:58pm

Unfortunately not. It’s an older HomeCinema from Samsung.

Test ongoing

morph166955 · August 28, 2023, 6:12pm

That stinks. I’m not sure if that’s something we can/should resolve as part of this binding since it’s related to another system.

michaeljoos · August 28, 2023, 6:19pm

No, I don’t think so. And it is possible to control the volume with a stepper item (screenshot above). For me this is OK.

michaeljoos · August 28, 2023, 6:41pm

No error with latest jar anymore. And overall I have to say everything is working!

Only small thing: Maybe you remenber the flipping power channel. It looks like we still have this. Most probably it depends on the refresh rate. I have recorded a video:

https://www.swisstransfer.com/d/5643ffec-990d-4882-8b4b-6faae9d522dc

We see when I switch on the power channel, that WOL works (Power goes up to about 9W). Then Power Channel goes OFF and a bit later ON again. Finally TV is ON (80 W). Maybe you can find the reason and improve more?

morph166955 · August 28, 2023, 6:44pm

Awesome! Very glad to hear, probably going to drop this into the marketplace shortly.

Does this only happen when waking up with a WOL or does this happen even if the TV is reachable? I think we may be having an issue where the protocols are waking up from the TV being reachable and setting some odd values. Can you get me a trace log to show that happening so I can follow both protocols?

michaeljoos · August 28, 2023, 6:50pm

It only happens with WOL. Last time it even did not power ON the TV: ON → WOL → OFF

This is a trace where WOL did work, but TV did not turn ON:
WOL_OK_TV_notON.log (73.5 KB)

I try to do another one when TV is turning on.

Voilà. This is a trace where evyrthing did work as expected: ON → WOL → TV ON (without flipping to OFF in between):
WOL_OK_TV_OK.log (184.5 KB)

morph166955 · August 28, 2023, 10:29pm

I looked through the logs. Something weird happened with the WOL. It’s like the TV took forever to come back alive.

WOL_OK_TV_notON:

2023-08-28 20:54:34.732 [TRACE] [.androidtv.internal.AndroidTVHandler] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Command received at handler: power ON
2023-08-28 20:54:34.733 [DEBUG] [philipstv.PhilipsTVConnectionManager] - Received channel: androidtv:philipstv:F00DBABE_AA5E_BABA_DADA_70af241424b4:power, command: ON
2023-08-28 20:54:36.836 [DEBUG] [nal.protocol.philipstv.WakeOnLanUtil] - WOL sent to Broadcast-IP /192.168.1.255 with MAC 70:AF:24:14:24:B4
2023-08-28 20:54:44.400 [DEBUG] [tocol.philipstv.service.PowerService] - PowerState Json sent: {"powerstate":"On"}
2023-08-28 20:54:51.036 [TRACE] [philipstv.PhilipsTVConnectionManager] - postUpdateThing OFFLINE NONE TV is not reachable and should therefore be off.
2023-08-28 20:54:51.037 [TRACE] [philipstv.PhilipsTVConnectionManager] - Updating status to OFFLINE NONE TV is not reachable and should therefore be off.
2023-08-28 20:54:51.037 [TRACE] [nternal.AndroidTVTranslationProvider] - Failed to translate: TV is not reachable and should therefore be off.
2023-08-28 20:54:51.038 [TRACE] [philipstv.PhilipsTVConnectionManager] - setStatus to false TV is not reachable and should therefore be off. TV is not reachable and should therefore be off.
2023-08-28 20:54:52.034 [DEBUG] [philipstv.PhilipsTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device Health - Online: false - Logged In: false
2023-08-28 20:54:56.023 [DEBUG] [l.googletv.GoogleTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device Health - Online: true - Logged In: false - Mode: NORMAL
2023-08-28 20:54:56.023 [DEBUG] [l.googletv.GoogleTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device is back online.  Attempting reconnection.
2023-08-28 20:54:56.091 [INFO ] [tocol.googletv.GoogleTVMessageParser] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Login Successful
2023-08-28 20:54:56.156 [DEBUG] [l.googletv.GoogleTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Setting power to false
2023-08-28 20:54:57.036 [DEBUG] [philipstv.PhilipsTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device Health - Online: true - Logged In: false
2023-08-28 20:54:57.036 [DEBUG] [philipstv.PhilipsTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device is back online.  Attempting reconnection.
2023-08-28 20:54:57.104 [TRACE] [philipstv.PhilipsTVConnectionManager] - postUpdateThing ONLINE NONE online.online
2023-08-28 20:54:57.107 [TRACE] [nternal.AndroidTVTranslationProvider] - Translated: online.online as Online
2023-08-28 20:54:57.108 [TRACE] [philipstv.PhilipsTVConnectionManager] - setStatus to true online.online Online
2023-08-28 20:54:57.266 [DEBUG] [protocol.philipstv.ConnectionManager] - {"powerstate":"StandbyKeep"}
2023-08-28 20:54:57.267 [TRACE] [philipstv.PhilipsTVConnectionManager] - postUpdateThing OFFLINE NONE 
2023-08-28 20:54:57.270 [TRACE] [philipstv.PhilipsTVConnectionManager] - Updating status to OFFLINE NONE 
2023-08-28 20:54:57.271 [TRACE] [nternal.AndroidTVTranslationProvider] - Failed to translate: 
2023-08-28 20:54:57.271 [TRACE] [philipstv.PhilipsTVConnectionManager] - setStatus to false
2023-08-28 20:55:02.273 [DEBUG] [philipstv.PhilipsTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device Health - Online: true - Logged In: false

WOL_OK_TV_OK:

2023-08-28 20:58:36.542 [TRACE] [.androidtv.internal.AndroidTVHandler] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Command received at handler: power ON
2023-08-28 20:58:36.544 [DEBUG] [philipstv.PhilipsTVConnectionManager] - Received channel: androidtv:philipstv:F00DBABE_AA5E_BABA_DADA_70af241424b4:power, command: ON
2023-08-28 20:58:38.649 [DEBUG] [nal.protocol.philipstv.WakeOnLanUtil] - WOL sent to Broadcast-IP /192.168.1.255 with MAC 70:AF:24:14:24:B4
2023-08-28 20:58:46.830 [DEBUG] [philipstv.PhilipsTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device Health - Online: true - Logged In: false
2023-08-28 20:58:46.830 [DEBUG] [philipstv.PhilipsTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device is back online.  Attempting reconnection.
2023-08-28 20:58:46.883 [TRACE] [philipstv.PhilipsTVConnectionManager] - postUpdateThing ONLINE NONE online.online
2023-08-28 20:58:46.886 [TRACE] [nternal.AndroidTVTranslationProvider] - Translated: online.online as Online
2023-08-28 20:58:46.887 [TRACE] [philipstv.PhilipsTVConnectionManager] - setStatus to true online.online Online
2023-08-28 20:58:47.272 [DEBUG] [tocol.philipstv.service.PowerService] - PowerState Json sent: {"powerstate":"On"}
2023-08-28 20:58:47.376 [DEBUG] [protocol.philipstv.ConnectionManager] - {"powerstate":"StandbyKeep"}
2023-08-28 20:58:47.376 [TRACE] [philipstv.PhilipsTVConnectionManager] - postUpdateThing OFFLINE NONE 
2023-08-28 20:58:47.382 [TRACE] [philipstv.PhilipsTVConnectionManager] - Updating status to OFFLINE NONE 
2023-08-28 20:58:47.383 [TRACE] [nternal.AndroidTVTranslationProvider] - Failed to translate: 
2023-08-28 20:58:47.383 [TRACE] [philipstv.PhilipsTVConnectionManager] - setStatus to false  
2023-08-28 20:58:47.464 [TRACE] [philipstv.PhilipsTVConnectionManager] - postUpdateThing ONLINE NONE online.online
2023-08-28 20:58:47.470 [TRACE] [nternal.AndroidTVTranslationProvider] - Translated: online.online as Online
2023-08-28 20:58:47.471 [TRACE] [philipstv.PhilipsTVConnectionManager] - setStatus to true online.online Online
2023-08-28 20:58:48.063 [DEBUG] [l.googletv.GoogleTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device Health - Online: true - Logged In: false - Mode: NORMAL
2023-08-28 20:58:48.063 [DEBUG] [l.googletv.GoogleTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device is back online.  Attempting reconnection.
2023-08-28 20:58:52.385 [DEBUG] [philipstv.PhilipsTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device Health - Online: true - Logged In: true
2023-08-28 20:58:53.096 [INFO ] [tocol.googletv.GoogleTVMessageParser] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Login Successful
2023-08-28 20:58:53.197 [DEBUG] [l.googletv.GoogleTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Setting power to true

Notice the different order of operations that happened between the two (be careful to see Philips vs Google in the message). First, I’ve not seen “StandbyKeep” anywhere in the code so far. It’s always been “On” “Off” or “Standby”. So that’s causing some issues there because it knocks the thing offline due to an unknown power state. Second, on the one that failed it looks like the binding didn’t wait long enough to send the On. Notice it sends the On almost exactly 10 seconds after the command is sent to the handler. The thing hadn’t come online yet at that point (it took almost 25 seconds from command to online). In the one that was successful the handler came online in about 10 seconds and the command was sent promptly. I’m wondering if we should hold sending the power on until we get “StandbyKeep” and use that as a trigger. Also notice, GTV logged in first and then PTV. You can see GTV set the power states on each at some point. I think that’s what caused the power state to flip back and forth.

Part of this is because of the way we’re doing health monitoring. Every 5 seconds we poll the device to see if we can make a tcp connection onto the port. The theory is, if we can’t even open a tcp connection then the protocols definitely won’t be able to hook. I’m thinking that we can adjust that to maybe 1 second the moment a power-on command is sent so we keep a closer eye on it.

morph166955 · August 29, 2023, 9:34pm

For anyone watching this, I’ve officially pushed the most recent jar to the AndroidTV marketplace posting. While I’m sure I’ll have some interim test builds, I’ll be doing the more stable ones to there going forward until this is merged into the OH repo.

michaeljoos · August 30, 2023, 4:53am

@morph166955 I have done another test with WOL from network binding and without sending power on command to TV. Just to watch the status of the thing when TV goes out of deep sleep mode.

Enable GoogleTV = ON:

TV in deep sleep mode (0.3W)
Send wake up command to network binding:

 var wolAction = actions.Things.getActions("network","network:pingdevice:881e749a1e");
 wolAction.sendWakeOnLanPacketViaMac();

TV wakes up immediately (~8W)
Thing status does not go Online. The status stays somehow in:

Trace:
WOL_OK_Thing_Offline_GTVProtON.log (144.2 KB)

2nd test with Enable GoogleTV = OFF:

TV in deep sleep mode (0.3W)
Send wake up command to network binding:

 var wolAction = actions.Things.getActions("network","network:pingdevice:881e749a1e");
 wolAction.sendWakeOnLanPacketViaMac();

TV wakes up immediately (~8W)
Thing status does not go Online. The status stays somehow in:
Disable/Enable Thing and status was immediately ONLINE

Trace:
WOL_OK_Thing_Offline_GTVProtOFF_DisableEnableThing.log (223.9 KB)

Maybe it helps to find the WOL issue we have.

morph166955 · August 30, 2023, 3:02pm

Yup, exactly what I was expecting to see. The health monitor definitely saw you do the WOL and is firing off the connection when the port opens. It’s this “StandbyKeep” state. Not sure where that came from but it’s throwing the protocol from online to offline inside of a split second. I think if you were to send a power on once GTV comes up it would power up as expected and the thing would come online.
Everything looks fine from what I can see other than that. I think if I can tune up some of the timers and add StandbyKeep it should clean this up. I have a few ideas, just haven’t had the time to do the code yet. Maybe this afternoon, been a busy week.

2023-08-30 06:22:47.701 [DEBUG] [philipstv.PhilipsTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device Health - Online: false - Logged In: false
2023-08-30 06:22:50.178 [DEBUG] [l.googletv.GoogleTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device Health - Online: false - Logged In: false - Mode: NORMAL

2023-08-30 06:22:53.126 [DEBUG] [philipstv.PhilipsTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device Health - Online: true - Logged In: false
2023-08-30 06:22:53.126 [DEBUG] [philipstv.PhilipsTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device is back online.  Attempting reconnection.

2023-08-30 06:22:53.197 [TRACE] [philipstv.PhilipsTVConnectionManager] - postUpdateThing ONLINE NONE online.online
2023-08-30 06:22:53.198 [DEBUG] [philipstv.PhilipsTVConnectionManager] - Refresh Scheduler already started for Philips TV F00DBABE_AA5E_BABA_DADA_70af241424b4, terminating.
2023-08-30 06:22:53.200 [DEBUG] [philipstv.PhilipsTVConnectionManager] - Starting Refresh Scheduler for Philips TV F00DBABE_AA5E_BABA_DADA_70af241424b4 with refresh rate of 10.
2023-08-30 06:22:53.201 [TRACE] [nternal.AndroidTVTranslationProvider] - Translated: online.online as Online
2023-08-30 06:22:53.202 [TRACE] [philipstv.PhilipsTVConnectionManager] - setStatus to true online.online Online
2023-08-30 06:22:53.203 [DEBUG] [protocol.philipstv.ConnectionManager] - Target Uri is: https://192.168.1.57:1926/6/powerstate
2023-08-30 06:22:53.738 [DEBUG] [protocol.philipstv.ConnectionManager] - ----------------------------------------
2023-08-30 06:22:53.739 [DEBUG] [protocol.philipstv.ConnectionManager] - HTTP/1.1 200 OK
2023-08-30 06:22:53.739 [DEBUG] [protocol.philipstv.ConnectionManager] - {"powerstate":"StandbyKeep"}
2023-08-30 06:22:53.740 [TRACE] [philipstv.PhilipsTVConnectionManager] - postUpdateThing OFFLINE NONE 
2023-08-30 06:22:53.740 [DEBUG] [philipstv.PhilipsTVConnectionManager] - Stopping Refresh Scheduler for Philips TV: F00DBABE_AA5E_BABA_DADA_70af241424b4
2023-08-30 06:22:53.741 [TRACE] [philipstv.PhilipsTVConnectionManager] - Updating status to OFFLINE NONE 
2023-08-30 06:22:53.743 [TRACE] [nternal.AndroidTVTranslationProvider] - Failed to translate: 
2023-08-30 06:22:53.743 [TRACE] [philipstv.PhilipsTVConnectionManager] - setStatus to false  

2023-08-30 06:22:55.181 [DEBUG] [l.googletv.GoogleTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device Health - Online: true - Logged In: false - Mode: NORMAL
2023-08-30 06:22:55.182 [DEBUG] [l.googletv.GoogleTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device is back online.  Attempting reconnection.
2023-08-30 06:22:55.183 [DEBUG] [l.googletv.GoogleTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Attempting to reconnect to the GoogleTV

2023-08-30 06:22:55.272 [INFO ] [tocol.googletv.GoogleTVMessageParser] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Login Successful
2023-08-30 06:22:55.273 [TRACE] [nternal.AndroidTVTranslationProvider] - Translated: online.online as Online
2023-08-30 06:22:55.279 [DEBUG] [l.googletv.GoogleTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Setting power to false

2023-08-30 06:22:55.898 [DEBUG] [l.googletv.GoogleTVConnectionManager] - I/O error while reading from stream: Connection reset
2023-08-30 06:22:55.900 [TRACE] [nternal.AndroidTVTranslationProvider] - Translated: offline.io-error as I/O Error
2023-08-30 06:22:55.902 [DEBUG] [l.googletv.GoogleTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Message reader thread exiting 6466
2023-08-30 06:22:59.245 [DEBUG] [philipstv.PhilipsTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device Health - Online: false - Logged In: false
2023-08-30 06:22:59.246 [DEBUG] [philipstv.PhilipsTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device is offline.
2023-08-30 06:22:59.247 [TRACE] [philipstv.PhilipsTVConnectionManager] - postUpdateThing OFFLINE COMMUNICATION_ERROR offline.communication-error-will-try-to-reconnect
2023-08-30 06:22:59.248 [TRACE] [philipstv.PhilipsTVConnectionManager] - Updating status to OFFLINE COMMUNICATION_ERROR offline.communication-error-will-try-to-reconnect
2023-08-30 06:22:59.250 [TRACE] [nternal.AndroidTVTranslationProvider] - Translated: offline.communication-error-will-try-to-reconnect as Communication error, will try to reconnect
2023-08-30 06:22:59.251 [TRACE] [philipstv.PhilipsTVConnectionManager] - setStatus to false offline.communication-error-will-try-to-reconnect Communication error, will try to reconnect

2023-08-30 06:23:00.733 [DEBUG] [l.googletv.GoogleTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device Health - Online: false - Logged In: false - Mode: NORMAL
2023-08-30 06:23:04.254 [DEBUG] [philipstv.PhilipsTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device Health - Online: true - Logged In: false
2023-08-30 06:23:04.254 [DEBUG] [philipstv.PhilipsTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device is back online.  Attempting reconnection.

2023-08-30 06:23:04.319 [TRACE] [philipstv.PhilipsTVConnectionManager] - postUpdateThing ONLINE NONE online.online
2023-08-30 06:23:04.320 [DEBUG] [philipstv.PhilipsTVConnectionManager] - Refresh Scheduler already started for Philips TV F00DBABE_AA5E_BABA_DADA_70af241424b4, terminating.
2023-08-30 06:23:04.321 [DEBUG] [philipstv.PhilipsTVConnectionManager] - Starting Refresh Scheduler for Philips TV F00DBABE_AA5E_BABA_DADA_70af241424b4 with refresh rate of 10.
2023-08-30 06:23:04.321 [TRACE] [nternal.AndroidTVTranslationProvider] - Translated: online.online as Online
2023-08-30 06:23:04.322 [TRACE] [philipstv.PhilipsTVConnectionManager] - setStatus to true online.online Online
2023-08-30 06:23:04.324 [DEBUG] [protocol.philipstv.ConnectionManager] - Target Uri is: https://192.168.1.57:1926/6/powerstate
2023-08-30 06:23:04.470 [DEBUG] [protocol.philipstv.ConnectionManager] - ----------------------------------------
2023-08-30 06:23:04.470 [DEBUG] [protocol.philipstv.ConnectionManager] - HTTP/1.1 200 OK
2023-08-30 06:23:04.471 [DEBUG] [protocol.philipstv.ConnectionManager] - {"powerstate":"StandbyKeep"}
2023-08-30 06:23:04.471 [TRACE] [philipstv.PhilipsTVConnectionManager] - postUpdateThing OFFLINE NONE 
2023-08-30 06:23:04.473 [DEBUG] [philipstv.PhilipsTVConnectionManager] - Stopping Refresh Scheduler for Philips TV: F00DBABE_AA5E_BABA_DADA_70af241424b4
2023-08-30 06:23:04.475 [TRACE] [philipstv.PhilipsTVConnectionManager] - Updating status to OFFLINE NONE 
2023-08-30 06:23:04.476 [TRACE] [nternal.AndroidTVTranslationProvider] - Failed to translate: 
2023-08-30 06:23:04.476 [TRACE] [philipstv.PhilipsTVConnectionManager] - setStatus to false 

2023-08-30 06:23:05.735 [DEBUG] [l.googletv.GoogleTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device Health - Online: true - Logged In: false - Mode: NORMAL
2023-08-30 06:23:05.736 [DEBUG] [l.googletv.GoogleTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Device is back online.  Attempting reconnection.
2023-08-30 06:23:05.736 [DEBUG] [l.googletv.GoogleTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Attempting to reconnect to the GoogleTV

2023-08-30 06:23:05.804 [INFO ] [tocol.googletv.GoogleTVMessageParser] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Login Successful
2023-08-30 06:23:05.806 [TRACE] [nternal.AndroidTVTranslationProvider] - Translated: online.online as Online
2023-08-30 06:23:05.813 [DEBUG] [l.googletv.GoogleTVConnectionManager] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Setting power to false

morph166955 · September 2, 2023, 8:26pm

Ok, let’s give this a shot for the power…

https://github.com/morph166955/openhab-addons/releases/download/androidtv-beta/org.openhab.binding.androidtv-4.1.0-SNAPSHOT-40ebd69.jar

Trace log please. What should happen now:

We track “StandbyKeep” as the message received after it comes online from low power after a WOL. This should bring the thing online.
We now track that the user requested a power on. In the event that the WOL takes more than the 10 second timer (which was observed in a few of the logs), when the device does come online we send an extra power on command.
The moment a power-on is sent, if the device is in low power (basically if it’s offline), we change the health monitor from 5 seconds to 1 second to get a faster response time. In theory we should see that device come up much quicker now.

michaeljoos · September 3, 2023, 11:36am

I could see different behaviour with latest jar and have done different trace logs. Sometimes Thing did go online and all good. But I could also see that Thing did go Online and then Offline again with GoogleTV Status “I/O:Error”:

status

Enable GoogleTV_Enabled_IOError.log (211.3 KB)

It also happened once that TV did not turn on at all:

Enable GoogleTV_Disabled_TVnotPoweredON.log (239.4 KB)

These two logs are with “Enable GoogleTV = Enabled” and “Enable GoogleTV = Disabled”:
Enable GoogleTV_Enabled.log (197.7 KB)
Enable GoogleTV_Disabled.log (224.3 KB)

morph166955 · September 3, 2023, 6:52pm

I’m not sure why it went to I/O Error and stuck there. I see where it happened…

2023-09-03 11:27:52.446 [DEBUG] [l.googletv.GoogleTVConnectionManager] - I/O error while reading from stream: Connection reset
2023-09-03 11:27:52.447 [TRACE] [nternal.AndroidTVTranslationProvider] - Translated: offline.io-error as I/O Error

But then…

2023-09-03 11:28:19.037 [INFO ] [tocol.googletv.GoogleTVMessageParser] - F00DBABE_AA5E_BABA_DADA_70af241424b4 - Login Successful
2023-09-03 11:28:19.038 [TRACE] [nternal.AndroidTVTranslationProvider] - Translated: online.online as Online

So it should have gone online again. I’ll add some extra debug statements to see what’s happening.

greenjack · September 21, 2023, 8:43am

Hello, I have several points to clarify

is it works with OH 4
is it merged in OH? (meaned is it searcheable from within interface)
I can spent some time to develop (but with some preceeding explanations) any issues, if needed

greenjack · September 28, 2023, 2:23pm

Well, I install the addon, however on/off channel works, but the philips like (such as amblilight) not working

morph166955 · September 28, 2023, 11:29pm

Did you install the last posted here or the AndroidTV binding from the marketplace?

michaeljoos · September 29, 2023, 4:18am

Please don’t expect too much support with this little information. I’m working in a technical support role and the worst thing when people ask for help is “it does not work”.

Please also check how to ask for help:

greenjack · September 29, 2023, 7:59am

Last posted here

greenjack · September 29, 2023, 8:07am

Thanks for template, and even your posts was never like it i will try to fill it here:

Platform
- Hardware: Orange Pi Zero LTS
- Operating System: Armbian
- OpenHAB Version: 4.0.2
- Originating Issue: Philips TV Thing
Issue
- Expected Behavior: (for example) Working of mute switch
- Actual Behavior: not works
- Steps:
  1. Add thing via inbox (Philips thing only)
  2. Pair via openhab console once as philips
  3. Enable google tv, pair again. Since then on/off switch works
What I have done so far
- nothing
Details
- Suppose like the “philips” protocol not work at all

Logs

where can i get the right portion of logs?

michaeljoos · October 1, 2023, 6:55am

Well, it’s not about strictly following the template line by line, but it’s about providing as much information as possible (detailed steps you did, screenshots, log files, etc).

I did quickly double check in my system and have re-added the PhilipsTV-Thing:

It should be OK to add PhilipsTV and do Pin-Process with this Setting:

For GoogleTV you don’t need to do the pin process separately.

But before you delete the thing and add it again, you should first delete the credentials and pin in the command line., e.g.:

sudo rm -R /var/lib/openhab/androidtv

Could be that path is different in your system.

If this does not work, you should definitively share TRACE or DEBUG log files. How to create log files is described in the documentation: Logging | openHAB

Console e.g.

log:set TRACE org.openhab.binding.androidtv

Last point: Not all models have beed tested in the past. What model do you have?

And good to know:
Some things to note: