# \[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:** 18\
**Page:** 19

<div class="post-metadata">

**Author:** ![B3rt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/b3rt/32/9435_2.png) [@B3rt](https://community.homey.app/u/B3rt)\
**Post date:** [February 9, 2024, 1:26pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/369 "2024-02-09T13:26:35Z")

</div>

the new/other app does not support ambilight, the other one is an android OS app and not specific for Philips as this app.

The currect APP uses the build in API of the TV itself, you can/could control the whole TV with it, including ambilight etc.  
The other app is a android TV app and you only can control the android part of the TV.

---

<div class="post-metadata">

**Author:** ![zakraket](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/zakraket/32/17470_2.png) [@zakraket](https://community.homey.app/u/zakraket)\
**Post date:** [February 9, 2024, 3:47pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/370 "2024-02-09T15:47:17Z")

</div>

That would work for me since we watch TV using an app (Odido, formerly T-mobile)

---

<div class="post-metadata">

**Author:** ![HomeyHiC](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/homeyhic/32/85112_2.png) [@HomeyHiC](https://community.homey.app/u/HomeyHiC)\
**Post date:** [April 21, 2024, 10:17am UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/371 "2024-04-21T10:17:49Z")

</div>

Any fix?

---

<div class="post-metadata">

**Author:** ![Jafar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jafar/32/72066_2.png) [@Jafar](https://community.homey.app/u/Jafar)\
**Post date:** [September 23, 2024, 2:19pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/372 "2024-09-23T14:19:16Z")

</div>

Hi ! Did you managed to make it work now ? I’m having OLED806 TV and can’t even connect it to the App (using static IP), can’t find the device so TV don’t get me any digit pin. My phone is working ok with the TV, but I would prefer to use Homey.

@lucasvdh Is there any way to change port from 1925 to 1926 ?

- Year your TV was made : 2016
- Model name : OLED806
- `http://{your_tv_ip}:1926/system is` is working for me.

```auto
{
"notifyChange": "http",
"menulanguage": "French",
"name": "65OLED806/12",
"country": "France",
"serialnumber_encrypted": "TepCvOyxEGZ5PE8ObS4VxGXM0Q78CrBRCDB4X39yYJ8=\n",
"softwareversion_encrypted": "hl/lNjae86x3IhVA4pQutu9wFcVPEmK9f1IcUFRlI9Air/5GizQRlxsTBK63Fr1n\n",
"model_encrypted": "+EJRHq8+9S2Caie7BnawQKW+XPwTtnj/yQcZghlGVnQ=\n",
"deviceid_encrypted": "dv9DyhL0HMvi7GnfsSbRsRhTVofb+IEYqncSl2cjdu0=\n",
"nettvversion": "10.0.0",
"epgsource": "no_epg",
"api_version": {
"Major": 6,
"Minor": 1,
"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"
}

```

Thanks and have a great day !

---

<div class="post-metadata">

**Author:** ![HomeyHiC](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/homeyhic/32/85112_2.png) [@HomeyHiC](https://community.homey.app/u/HomeyHiC)\
**Post date:** [October 20, 2024, 8:29pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/373 "2024-10-20T20:29:08Z")

</div>

@lucasvdh do you have any update?  
I have a problem with connecting my TV Philips 65OLED909 and Philips 43PUS8546.

---

<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:** [February 21, 2025, 4:48pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/374 "2025-02-21T16:48:16Z")

</div>

Hey everyone,

Sorry for not actively maintaining the app. Life happened, and time got away from me.

Right now, I’m not in a position to work on this project, and I’m not sure when I’ll have the time again. If anyone wants to contribute or take over development, feel free to send me a DM. ✌

---

<div class="post-metadata">

**Author:** ![Mariomark1541](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mariomark1541/32/178160_2.png) [@Mariomark1541](https://community.homey.app/u/Mariomark1541)\
**Post date:** [February 21, 2025, 9:19pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/375 "2025-02-21T21:19:07Z")

</div>

@Vladyslav_Zahorodnii see message above frontlines

---

<div class="post-metadata">

**Author:** ![Glenn\_Dijkstra](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/glenn_dijkstra/32/17251_2.png) [@Glenn\_Dijkstra](https://community.homey.app/u/Glenn_Dijkstra)\
**Post date:** [April 16, 2025, 7:18pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/376 "2025-04-16T19:18:06Z")

</div>

Hi, i tried to add my philips 43PUS8009. It’s found but keeps loading endlessly. Does that mean it’s not supported?

 ![Screenshot_20250416_215704](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/c/9cc21189b97abe8f6d466f5938f85c2f3fecb9b5.jpeg)  
 ![Screenshot_20250417-233132_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/7/4729602f542e706a0b97f0729ce0c599671e2cf8.jpeg)  
 ![Screenshot_20250417-233059_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/6/a6d413d594e0c1a42a9d182c15909f89b9b98e17.jpeg)

---

<div class="post-metadata">

**Author:** ![ExtraKim](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/extrakim/32/85286_2.png) [@ExtraKim](https://community.homey.app/u/ExtraKim)\
**Post date:** [June 25, 2025, 10:43pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/377 "2025-06-25T22:43:42Z")

</div>

![Screenshot_20250626_001631_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/3/b369e277aaa4bf917b9cd91df2fdbc20473fcbb2.jpeg)

Today the app crashed multiple times and then Homey crashed, it used 8.1GB of Ram (I have a bigger Pi in my Homey Pro), removed the app and restarted Homey, now it only use 1.3GB Ram. Something isn’t right.

---

<div class="post-metadata">

**Author:** ![VyseExhale](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vyseexhale/32/123975_2.png) [@VyseExhale](https://community.homey.app/u/VyseExhale)\
**Post date:** [September 22, 2025, 8:44am UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/378 "2025-09-22T08:44:47Z")

</div>

same here, but I think @lucasvdh does not have the time anymore to maintain this

---

<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:** [May 14, 2026, 12:28am UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/379 "2026-05-14T00:28:19Z")

</div>

Hi everyone,

I took a small two-year hiatus from open-source work, but I’m back at it.

2.5.1 has been the live version for that entire stretch and a lot of work has piled up on the test track in the meantime. I’d really like a few of you to try the new build before I publish it.

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

## What’s changed in v3.7.1

### Reliability

- Full TypeScript rewrite (v3.0.0) fixed a lot of the “app stops responding after a while” bugs.
- Much more stable HTTPS communication on Philips Android TVs: fewer crashes of the TV’s internal API service, devices stay marked “available” more consistently, and automatic transport recovery when the TV’s HTTPS service falters mid-session.
- I’ve done a deep-dive into a couple of Philips Restlet quirks that don’t appear to be documented in the wider Jointspace community, digest auth nonce binding to TCP sessions, and a CPU-consumption bug in Restlet’s NIO stack that force-closes connections. This hopefully means that the new app adds less strain on the xtv (jointspace) service causing it to crash less. Working on this both took most of v3.5.

### Pairing

- Auto-discovery for modern Android TVs over mDNS (next to SSDP).
- New Repair flow to re-link a device when the TV’s IP changes, without losing the existing flow references.
- “By IP address” fallback in the diagnostic tool for TVs that aren’t discovered automatically.

### Flow editor

- App icons in the app pickers (lazy-loaded from the TV).
- New trigger “A specific app was opened”.
- New conditions for current app / source / screen.
- New actions: turn the screen on / off.
- New triggers: source changed, screen turned on/off.
- Channel switching with autocomplete (should work on legacy TVs too).
- Source switching if your TV supports it (still has fallback to using Google Assistant to switch source).
- Channel up/down keys actually work now (they were declared but unhandled in the 2.x line).

### Diagnostic report tool

Because every Philips firmware is a little different and historically that meant a lot of back-and-forth on issues.  
The new diagnostic report page in app settings runs in ~5 seconds and produces a Markdown report containing:

- TV model, firmware, API version, OS type (Android / Saphi / legacy)
- The exact response of every endpoint we touch, with status and timing
- The app’s cached settings and store values per device
- SSDP / mDNS discovery state
- ARP / MAC info
- A raw JSON appendix at the bottom

Paste it into a GitHub issue together with a small description of your issue and I should have everything I need to reproduce or pinpoint the problem without a single follow-up question.  
There’s also a “By IP address” tab for TVs that won’t pair, so the report works even when the regular setup path is broken.

The hope is that this will shorten the roundtrip from bug report to fix, for both me and you.

### Other

- Custom screen\_on capability for TVs that support it, turns the screen off while audio keeps playing.
- current\_application and current\_source capabilities, with the former clearing when the TV goes to standby so “current app is Netflix”-style flow conditions stop matching when the TV is off.

### Behind the scenes

- Requires Homey firmware 12.2+
- Node 22 runtime
- Self-correcting transport (HTTP/1925 - HTTPS/1926) so devices recover automatically if firmware changes that shift endpoints.

## What I’d love feedback on

- Anything that used to work in 2.5.1 but doesn’t now (regression check is the main reason for the test period).
- Whether the new pairing / Repair flow finds and links your TV.
- Whether the screen-on/off toggle works (if your model has it).
- App icons rendering correctly in the flow card pickers.
- If the “specific app was opened” flow card trigger works for you.

If things look stable after a week or so I’ll submit 3.7.1 for review.

If you run into any issues, please generate the diagnostic report and post it in a new issue on GitHub: [https://github.com/lucasvdh/codes.lucasvdh.philips-jointspace/issues/new](https://github.com/lucasvdh/codes.lucasvdh.philips-jointspace/issues/new)

Thanks in advance for the help! 🙏

---

<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:** [May 18, 2026, 1:59pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/380 "2026-05-18T13:59:15Z")

</div>

So far, the new version hasn’t crashed for any of the 60 people currently running it.

If no new major issues or bugs are reported, I’ll submit this version for review tomorrow.

---

<div class="post-metadata">

**Author:** ![SamB](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/samb/32/16535_2.png) [@SamB](https://community.homey.app/u/SamB)\
**Post date:** [May 19, 2026, 11:47am UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/381 "2026-05-19T11:47:53Z")

</div>

I submitted a new issue but this may be more a compatibility issue than anything else.

---

<div class="post-metadata">

**Author:** ![Doekse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/doekse/32/109415_2.png) [@Doekse](https://community.homey.app/u/Doekse)\
**Post date:** [May 19, 2026, 12:23pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/382 "2026-05-19T12:23:27Z")

</div>

I’ve been waiting for this one! Great to have you back @lucasvdh

---

<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:** [May 22, 2026, 11:44pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/383 "2026-05-22T23:44:13Z")

</div>

Just pushed a new test version (v3.7.2).

The main thing this fixes is TVs that refused to pair with a 403 on the /system endpoint and it should detect a few more models now too. If you’ve had pairing trouble, give it a try: [https://homey.app/a/codes.lucasvdh.philips-jointspace/](https://homey.app/a/codes.lucasvdh.philips-jointspace/)

If it still doesn’t work for you, please generate a diagnostic report (Settings \> Apps \> Philips TV \> Diagnostic report) and open a GitHub issue so I can take a look. Thanks all!

---

<div class="post-metadata">

**Author:** ![HomeyHiC](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/homeyhic/32/85112_2.png) [@HomeyHiC](https://community.homey.app/u/HomeyHiC)\
**Post date:** [June 27, 2026, 7:51am UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/384 "2026-06-27T07:51:00Z")

</div>

@lucasvdh Hey Lucas. Thank you for the effort to fix the app! I’ve got back to this app and looks like both TVs didn’t have any issues with pairing. However, one TV after pairing has issues with keeping the connection, and when I switch off tv, the TV in Homey gets disconnected (and returning timeouts). When I turn on the TV usually it starts working in Homey as well. On the 2nd tv I don’t have this issue and can switch on tv directly from Homey. I’ve reported this issue on the github with the report from app. Would you be able to look into this?

Thank you!

---

<div class="post-metadata">

**Author:** ![Zakarias\_Mortensen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/zakarias_mortensen/32/55670_2.png) [@Zakarias\_Mortensen](https://community.homey.app/u/Zakarias_Mortensen)\
**Post date:** [August 27, 2026, 9:32pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/385 "2026-08-27T21:32:32Z")

</div>

Cheers for your awesome effort!

Ive seems to work great but the ambilight is flickering between states when i pick a light mode and then turn it off.

77f8887b-3739-4936-96ec-3c80d493cd1c

---

<div class="post-metadata">

**Author:** ![Arne\_Sch](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arne_sch/32/121047_2.png) [@Arne\_Sch](https://community.homey.app/u/Arne_Sch)\
**Post date:** [October 12, 2026, 5:43pm UTC](https://community.homey.app/t/app-pro-philips-tv-jointspace/14064/386 "2026-10-12T17:43:24Z")

</div>

I have the same issue. The tv that has this issue was also not showing up when trying to get it into Homey when it was shut off. The other one could be found when it was turned off.

I’m also a new user on the app, so no other experience so far.

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