# \[APP\]\[Pro\] Philips TV Jointspace

**URL:** <https://community.homey.app/t/app-pro-philips-tv-jointspace/14064>\
**Category:** Apps\
**Tags:** app\
**Created:** [June 4, 2019, 2:39pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064 "2019-06-04T14:39:27Z")\
**Posts on this page:** 20\
**Page:** 9

<div class="post-metadata">

**Author:** ![lucasvdh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lucasvdh/32/54915_2.png) [@lucasvdh](https://community.homey.app/u/lucasvdh)\
**Post date:** [April 5, 2021, 10:35pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/165 "2021-04-05T22:35:59Z")

</div>

> [@lucasvdh](#):
>
> - **More reliable power on behaviour**  
> Power on action will now work via the TV’s Chromecast interface. This does require you te enable the setting “Switch on with Chromecast”.
> - **HDMI source selection flow card action (e.g. Change source to HMDI 1)**  
> Requires an Android TV and Google Assistent to be enabled. This won’t be added as a UI component because there’s no way to detect which source is currently selected.
> - **AmbiHue (Philips Hue Ambilight integration) improvements**  
> Flow card trigger (e.g. AmbiHue was turned off), flow card action (e.g. Turn AmbiHue on) and the toggle button in the app will actually represent if it’s turned on or off.

A new version (`v0.5.0`) containing the features/improvements mentioned above has been released to test. This release also contains a minor pairing fix for models which do not require authentication and provided their pairing type as “none”.

Would be a great help I you guys can test this version before I release it.

[https://homey.app/a/codes.lucasvdh.philips-jointspace/test/](https://homey.app/a/codes.lucasvdh.philips-jointspace/test/)

---

<div class="post-metadata">

**Author:** ![Otter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/otter/32/11467_2.png) [@Otter](https://community.homey.app/u/Otter)\
**Post date:** [April 6, 2021, 6:54am UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/166 "2021-04-06T06:54:08Z")

</div>

installing it now!

@lucasvdh was testing the ambilight + hue function, it turned on once and then couldn’t turn it off again. also by manually turning it off via the TV and turning it on via your app didn’t work anymore.

29b00b4f-3b65-4348-bfa9-136c6448b2b8

---

<div class="post-metadata">

**Author:** ![DaveOne](https://avatars.discourse-cdn.com/v4/letter/d/a8b319/32.png) [@DaveOne](https://community.homey.app/u/DaveOne)\
**Post date:** [April 6, 2021, 7:22am UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/167 "2021-04-06T07:22:22Z")

</div>

Hi Lucas,  
I installed it this morning and it worked at first but after being away for a while and trying again, powering on is failing again.  
I created a diagnostic report, do you need it?  
Dave

---

<div class="post-metadata">

**Author:** ![lucasvdh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lucasvdh/32/54915_2.png) [@lucasvdh](https://community.homey.app/u/lucasvdh)\
**Post date:** [April 6, 2021, 7:38am UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/168 "2021-04-06T07:38:28Z")

</div>

Thanks @Otter and @DaveOne I received the diagnostic reports 👍

I will probably not have time to look at this for some days so if the current test version breaks I’d suggest switching back to `v0.4.1` on live.

---

<div class="post-metadata">

**Author:** ![Otter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/otter/32/11467_2.png) [@Otter](https://community.homey.app/u/Otter)\
**Post date:** [April 6, 2021, 8:05am UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/169 "2021-04-06T08:05:00Z")

</div>

No problem, happy to test. Hopefully Philips is getting back to a source selective input instead of dynamic, i’ve complained about it already maybe that make things easier my harmony setup is a mess because of it.

I’m using a 55OLED935/12

---

<div class="post-metadata">

**Author:** ![Witteflits](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/witteflits/32/34155_2.png) [@Witteflits](https://community.homey.app/u/Witteflits)\
**Post date:** [April 6, 2021, 1:49pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/170 "2021-04-06T13:49:59Z")

</div>

I can’t pair. I have an 65OLED804/12 with the latest firmware. But it won’t pair. Not with the test version and not with version 0.4.1

Here is the json output

```
{
	"notifyChange": "http",
	"menulanguage": "Dutch",
	"name": "TV Woonkamer",
	"country": "Belgium",
	"serialnumber_encrypted": "raRoT1if7aB4bO5K4z/bfSyWid7eO0vlxUHNyUSSOlI=\n",
	"softwareversion_encrypted": "aet+S8/OFqtVtG9c/bwoT4quf+FNqOJpLXT+nEBXkqHUWe2UQocKLrN0dmEb5A38\n",
	"model_encrypted": "rJeSeoaS0GTwP6/J/o9rKmxaeeBlMz6tGeqGzug1R0w=\n",
	"deviceid_encrypted": "2JnRHYenGU2gGlxiiFbMuT02U1a79OwQ2FyVZ3t+UM4=\n",
	"nettvversion": "9.0.0",
	"epgsource": "broadcast",
	"api_version": {
		"Major": 6,
		"Minor": 4,
		"Patch": 0
	},
	"featuring": {
		"jsonfeatures": {
			"editfavorites": [
				"TVChannels",
				"SatChannels"
			],
			"recordings": [
				"List",
				"Schedule",
				"Manage"
			],
			"ambilight": [
				"LoungeLight",
				"Hue",
				"Ambilight",
				"HueStreaming"
			],
			"menuitems": [
				"Setup_Menu"
			],
			"textentry": [
				"not_available"
			],
			"applications": [
				"TV_Apps",
				"TV_Games",
				"TV_Settings"
			],
			"pointer": [
				"not_available"
			],
			"inputkey": [
				"key"
			],
			"activities": [
				"intent"
			],
			"channels": [
				"preset_string"
			],
			"mappings": [
				"server_mapping"
			]
		},
		"systemfeatures": {
			"tvtype": "consumer",
			"content": [
				"dmr",
				"pvr"
			],
			"tvsearch": "intent",
			"pairing_type": "digest_auth_pairing",
			"secured_transport": "true",
			"companion_screen": "true"
		}
	},
	"os_type": "MSAF_2019_P"
}
```

---

<div class="post-metadata">

**Author:** ![JaccoStraaijer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jaccostraaijer/32/11777_2.png) [@JaccoStraaijer](https://community.homey.app/u/JaccoStraaijer)\
**Post date:** [April 6, 2021, 2:51pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/171 "2021-04-06T14:51:39Z")

</div>

Gee Lucas, hope you will have a full recovery soon. Thank you for all your efforts. Just inplemented some flows triggering ambilight and ambihue. Looking promising!

---

<div class="post-metadata">

**Author:** ![HuisCHovens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/huischovens/32/16973_2.png) [@HuisCHovens](https://community.homey.app/u/HuisCHovens)\
**Post date:** [April 6, 2021, 3:12pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/172 "2021-04-06T15:12:44Z")

</div>

@lucasvdh good to have you back. I’m curious if this will fix the pairing error I’ll try it out in a minute.

No, still parrings error, he sees the code on the TV, but if you retype it, nothing happens.

---

<div class="post-metadata">

**Author:** ![lucasvdh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lucasvdh/32/54915_2.png) [@lucasvdh](https://community.homey.app/u/lucasvdh)\
**Post date:** [April 6, 2021, 7:29pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/173 "2021-04-06T19:29:14Z")

</div>

It’s working on my TV and I don’t have acces to any others models … so it’s a bit hard to test. I couldn’t find any errors in the diagnostic report you sent so I might need to add some extra logging before we can get to the bottom of this.

---

<div class="post-metadata">

**Author:** ![HuisCHovens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/huischovens/32/16973_2.png) [@HuisCHovens](https://community.homey.app/u/HuisCHovens)\
**Post date:** [April 6, 2021, 7:36pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/174 "2021-04-06T19:36:06Z")

</div>

is there still a difference with cable or via wifi? I now have the TV on cable.

---

<div class="post-metadata">

**Author:** ![Otter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/otter/32/11467_2.png) [@Otter](https://community.homey.app/u/Otter)\
**Post date:** [April 6, 2021, 7:47pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/175 "2021-04-06T19:47:00Z")

</div>

Happy to test anything. I will try fiddling around a bit to see if there are other things.

I must say it is not the most stable TV os I’ve used. Got some HDMI problems with handshakes and ARC my ambilight + hue loses some lights when configuring. The source selection is rubbish but hey… i’ve got ths ambilight 😉

---

<div class="post-metadata">

**Author:** ![lucasvdh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lucasvdh/32/54915_2.png) [@lucasvdh](https://community.homey.app/u/lucasvdh)\
**Post date:** [April 6, 2021, 7:47pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/176 "2021-04-06T19:47:01Z")

</div>

@DaveOne I was hopeful that [Evgeny](https://github.com/eslavnov)’s solution by powering on the TV via Chromecast would work seeing how multiple people reported it to be a reliable way to wake up their Philips TV.

But after digging a bit deeper I found reports of people saying that even this solution didn’t work for them. This is also the case for me. A reason for this is yet to be found. The TV appears to just completely shut down all of it’s network interfaces (wired and wireless @HuisCHovens) even though(!) it should not be allowed to do this with the “Switch on with Chromecast” setting enabled.

For some people, reinstalling the integrated Chromecast app was the solution to their problems. For others it was activating the Alexa app. ([source](https://github.com/eslavnov/pylips/issues/52#issuecomment-649464222))

I have just reinstalled my Chromecast app and I’m waiting to see if it makes a difference. To any whom it may concern: I suggest you try both possible solutions mentioned above. You can find the Chromecast app under Internal apps in the Android settings.

---

<div class="post-metadata">

**Author:** ![Otter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/otter/32/11467_2.png) [@Otter](https://community.homey.app/u/Otter)\
**Post date:** [April 6, 2021, 7:49pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/177 "2021-04-06T19:49:17Z")

</div>

You’ve got all the other energy saving settings and WoWlan disabled/enabled? And it still goes to poweroff?.

---

<div class="post-metadata">

**Author:** ![lucasvdh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lucasvdh/32/54915_2.png) [@lucasvdh](https://community.homey.app/u/lucasvdh)\
**Post date:** [April 6, 2021, 8:00pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/178 "2021-04-06T20:00:30Z")

</div>

Yeah, it’s real weird. Everything is aimed at maximum power consumption/being always on and it still turns off. However, I’ll post here tomorrow what my findings are regarding the potential Chromecast fix.

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [April 6, 2021, 9:35pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/179 "2021-04-06T21:35:46Z")

</div>

FYI:

I use a different work-around to keep my tv `on`.  
Installed Wakelock Revamp (installed the mobile version via apk) and enabled the `processor` option. This keeps the tv in standby but reachable via network and also ADB.

With this option you can also wake it up with Chromecast.

---

<div class="post-metadata">

**Author:** ![lucasvdh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lucasvdh/32/54915_2.png) [@lucasvdh](https://community.homey.app/u/lucasvdh)\
**Post date:** [April 7, 2021, 2:39pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/180 "2021-04-07T14:39:03Z")

</div>

Thanks for the suggestion, I’ll try this next.

Reinstalling the Chromecast app did not result in the TV staying on for me.

---

<div class="post-metadata">

**Author:** ![HuisCHovens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/huischovens/32/16973_2.png) [@HuisCHovens](https://community.homey.app/u/HuisCHovens)\
**Post date:** [April 7, 2021, 3:29pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/181 "2021-04-07T15:29:06Z")

</div>

i also tried that trick with chromecast but didn’t work for me either.

---

<div class="post-metadata">

**Author:** ![lucasvdh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lucasvdh/32/54915_2.png) [@lucasvdh](https://community.homey.app/u/lucasvdh)\
**Post date:** [April 7, 2021, 7:24pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/182 "2021-04-07T19:24:13Z")

</div>

> [@martijnpoppen](#):
>
> Installed Wakelock Revamp (installed the mobile version via apk) and enabled the `processor` option. This keeps the tv in standby but reachable via network and also ADB.

I can confirm that this solution works for me, thanks @martijnpoppen!

---

<div class="post-metadata">

**Author:** ![lucasvdh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lucasvdh/32/54915_2.png) [@lucasvdh](https://community.homey.app/u/lucasvdh)\
**Post date:** [April 7, 2021, 7:25pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/183 "2021-04-07T19:25:45Z")

</div>

I’m going to suggest the [Wakelock Revamp](https://play.google.com/store/apps/details?id=eu.thedarken.wldonate) app as the main solution to the power on/sleep issue.

Sadly this means that there’s no solution for non-Android TV’s yet and I don’t think we’re going to find one. If any new information surfaces I will reopen the issue.

If, like me, you’re not able to connect to your TV via adb or you don’t know how to: you can install the app from a USB drive ([download from Github](https://github.com/d4rken/wakelock-revamp/releases/latest)) using a file manager app on your TV to open the `.apk` file.

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [April 7, 2021, 7:37pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/184 "2021-04-07T19:37:40Z")

</div>

I saw that for HomeAssistant they’re suggesting the same thing (link: [GitHub - nstrelow/ha\_philips\_android\_tv: Home Assistant custom component for the newer (2016+) Philips Android TVs](https://github.com/nstrelow/ha_philips_android_tv))  
I got this idea from the Home assistant community. Where they where discussing this issue. I think there’s no other way as Phillips completely shuts-down.

Some extra info from the HA integration:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/f/1f2e6c7d4dfddc8fcb8a19afae5f63822c8db8cc.png)

[Previous page](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064.md?page=8)

[Next page](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064.md?page=10)