[APP][Pro] Philips TV Jointspace

lucasvdh · June 4, 2019, 2:39pm

Philips TV (Jointspace) for Homey

Control and monitor your Philips TV from Homey: power, volume, Ambilight, apps, sources, channels, the screen itself, and every remote key, all usable in Flows.

This is the main support and discussion thread for the app. Post here for help, questions and feedback. For bug reports please use GitHub (link at the bottom), this is where issues are tracked and fixed.

Heads up: this is not an official app and is not affiliated with or endorsed by Philips or TP Vision. It works by talking to the TV’s Jointspace API, which the community reverse engineered over the years.

Get the app

Stable: https://homey.app/a/codes.lucasvdh.philips-jointspace/
Test: https://homey.app/a/codes.lucasvdh.philips-jointspace/test/

The app was completely rewritten as of v3.x.

Will it work with my TV?

Most Philips TVs from roughly 2014 to 2025 are supported, both Saphi and Android (MSAF) models. The only requirement is that the Jointspace API is reachable on your network.

Quick check: open http://<TV-IP>:1925/system in a browser on the same network. If you get a JSON response, you are good to go.

If that returns 403 Forbidden, try http://<TV-IP>:1925/1/system and http://<TV-IP>:1925/6/system instead. If either returns JSON your TV is supported; the app probes these version-prefixed paths automatically.

What it can do

On the device and as Flow conditions (capabilities):

Power on/off (uses Wake-on-LAN when the MAC is known)
Volume, mute, volume up/down
Ambilight on/off, Ambilight mode, Ambilight + Hue
Current app and current source (read-only)
Screen on/off, independent of TV power (supported models)
Every remote key (arrows, digits, colour keys, media transport, home, back, and more)

Flow triggers (when):

An app was opened / a specific app was opened
Ambilight, Ambilight mode and AmbiHue changed
Source changed, screen turned on or off (supported models)

Flow actions (then):

Open an application (autocomplete filled from the TV’s own app list)
Open Google Assistant (Android TVs)
Select a source, switch to a channel (autocomplete from the TV)
Send any remote key
Ambilight on/off, Ambilight mode, AmbiHue on/off
Turn the screen on or off while audio keeps playing (supported models)

Pairing

The app discovers TVs automatically over SSDP (older models) and mDNS (Android models). If yours is not found, you can add it by IP address in the pairing wizard.

The app remembers your TV by a stable hardware ID, not its IP address. So if your router later hands the TV a different IP, you do not need to re-pair: open the device, use the three-dot menu, choose Repair, and your Flows keep working.

Troubleshooting

TV will not turn on: in deep sleep some TVs drop off the network entirely and cannot be reached by anything. On models that support it, the recommended approach is to turn the screen off instead of the TV, which keeps the TV reachable. On Android TVs, the Wakelock Revamp app can also keep the network stack alive (at the cost of higher standby power).

Device shows unavailable after an IP change: use Repair (see above), do not delete and re-pair, that would lose your Flow references.

Incorrect pincode / pairing fails: first confirm the Jointspace API is reachable using the check above. If it is and pairing still fails, please file a bug with a diagnostic report.

Reporting a problem

The app has a built-in diagnostic report. In the Homey app go to Settings → Apps → Philips TV, pick your TV and tap Generate report. If the TV is not paired yet, use the By IP address tab. Secrets are redacted automatically. Paste the report into a new GitHub issue:

Issues / bug reports: https://github.com/lucasvdh/codes.lucasvdh.philips-jointspace/issues

Thanks to everyone who has tested, reported issues and contributed over the years. Keep the feedback coming.

Ben_Lens · June 4, 2019, 3:03pm

Hi Lucas,

Doesn’t seem to pair. I have a 49PUS6551/12 from 2017. When connecting for the first time it keeps “loading”

Mickel_Luiten · June 4, 2019, 3:48pm

Hi Lucas,

Same here no pairing on the 49pus7101/12 i will run the app in the cli see what the logs says and test the tv with the code on https://github.com/arzzen/philips-tv/

lucasvdh · June 4, 2019, 10:01pm

@Mickel_Luiten and @Ben_Lens and anyone else whom it might concern.

I’m about to release a new alpha version which should fix some of the pairing issues people are having.

Apparently there are little more versions of the Jointspace API out there then I assumed. I’ve added all versions now and better error handling so it’s clearer what’s going on e.g. incorrect api version.

Let me know if you’re still experiencing issues;

I’m also aware of an issue that might arise with people who have an older version than 6 but still require the authenticated version of the app. I’m looking into solving this.

Tim_Messerschmidt · June 5, 2019, 5:51am

Hi @lucasvdh

Pairing times out. v0.1.2

{message":“socket hang up”:“ECONNRESET”}

55PUS7101/12 YEAR:2016

{“notifyChange”:“http”,
“menulanguage”:“Dutch”,
“name”:“TV Woonkamer”,
“country”:“Netherlands”,
“serialnumber_encrypted”:“ygvm1jxU6BYNkBZbgzItoWaRoSIE4ABw0A8ftRSq+8A=\n”,
“softwareversion_encrypted”:“eyqO3oSosiX9Mf8dKohRZX48ql7bejcyyUZSzhvRGe4=\n”,
“model_encrypted”:“y05qeQWpHgeHtqHOGI4vFxjdD9PeCVmQuxwAebYlLGc=\n”,
“deviceid_encrypted”:“G0t23TyKZrTVd3GuDfnzTmffbdCXdVfmXI3CCYXIVkY=\n”,
“nettvversion”:“8.1.0”,
“epgsource”:“one”,
“api_version”:{
“Major”:6,
“Minor”:2,
“Patch”:0
},
}“featuring”:{“jsonfeatures”:{“editfavorites”:[“TVChannels”,“SatChannels”],“recordings”:[“List”,“Schedule”,“Manage”],“ambilight”:[“LoungeLight”,“Hue”,“Ambilight”],“menuitems”:[“Setup_Menu”],“textentry”:[“context_based”,“initial_string_available”,“editor_info_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”,“dms_tad”],“tvsearch”:“intent”,“pairing_type”:“digest_auth_pairing”,“secured_transport”:“true”}}}

lucasvdh · June 5, 2019, 6:30am

Hi @Tim_Messerschmidt,

What I see from the Json you posted is that your TV doesn’t require authentication. However if this is not the entire Json response, please modify your post to include everything.

I’ll write a fix today so the app uses the system info to determine if authentication is required or not.

Thanks for the feedback!

Tim_Messerschmidt · June 5, 2019, 6:33am

Hi @lucasvdh

added missing info from Json

lucasvdh · June 5, 2019, 9:10am

I’ve just pushed a new test script to the git repository with which you should be able to debug the pairing process more thoroughly.

So if you’ve got node running locally and are having trouble with pairing your TV, you can help me debug this issue by running the test script like this:

~ $ git clone git@github.com:lucasvdh/codes.lucasvdh.philips-jointspace.git\
 && cd codes.lucasvdh.philips-jointspace\
 && git checkout alpha\
 && cd tests
Cloning into 'codes.lucasvdh.philips-jointspace'...
remote: Enumerating objects: 5887, done.
remote: Counting objects: 100% (5887/5887), done.
remote: Compressing objects: 100% (3247/3247), done.
remote: Total 5887 (delta 2229), reused 5816 (delta 2158), pack-reused 0
Receiving objects: 100% (5887/5887), 4.52 MiB | 3.90 MiB/s, done.
Resolving deltas: 100% (2229/2229), done.
Switched to a new branch 'alpha'
~ $ node pairing.js

If this test script fails, please provide the response here.

Tim_Messerschmidt · June 5, 2019, 9:12am

Can’t help you. nothing running locally and not at home currently.

lucasvdh · June 5, 2019, 9:15am

@Tim_Messerschmidt no worries, just mentioning for the people who do.

Mickel_Luiten · June 5, 2019, 2:42pm

HI Lucas, tryed some things. Still on model 49pus7101/12 march2016

First of all the output from tv at http://192.168.2.140:1925/6/system

{
    "notifyChange": "http",
    "menulanguage": "Dutch",
    "name": "tv-philips",
    "country": "Netherlands",
    "serialnumber_encrypted": "1DjCNN8EaOUGsBbxCdx51bsga6hjenEs2pTvGhkQO/c=\n",
    "softwareversion_encrypted": "8a9dSFrH0LfQql5SsdUlns4a+SGPjjtt5XCcXrcmF8o=\n",
    "model_encrypted": "u/Bx4QtqANkTYeKPMGDtGdTJb6tLPcT719zX8YQiJAg=\n",
    "deviceid_encrypted": "Paq+4i+nwwemhiTaD0WOP9pryu1PHPQxf6TBAr8b2Bg=\n",
    "nettvversion": "8.1.3",
    "epgsource": "one",
    "api_version": {
        "Major": 6,
        "Minor": 2,
        "Patch": 0
    },
    "featuring": {
        "jsonfeatures": {
            "editfavorites": [
                "TVChannels",
                "SatChannels"
            ],
            "recordings": [
                "List",
                "Schedule",
                "Manage"
            ],
            "ambilight": [
                "LoungeLight",
                "Hue",
                "Ambilight"
            ],
            "menuitems": [
                "Setup_Menu"
            ],
            "textentry": [
                "context_based",
                "initial_string_available",
                "editor_info_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",
                "dms_tad"
            ],
            "tvsearch": "intent",
            "pairing_type": "digest_auth_pairing",
            "secured_transport": "true"
        }
    }
}

Then the output of your testscript.
? What’s your TV’s IP? 192.168.2.140
? What’s your API version? (1-6) 6
Updating client config
Sending system info call
API version as returned by TV: 6
Starting pairing process
Successfully started pairing process
? What’s the pin code displayed on the tv? 1683
Sending ping: 1683
(node:8640) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.

WIth the testscript the pincode is displayed on the tv.

When i run the app version v0.1.4 on homey and enter tvname(same as in json output) , IPadress and apiversion(6) nothing happens on tv(no pincode is displayed) and homey will endless load.

Hope this helps to find the fix.

lucasvdh · June 5, 2019, 3:03pm

@Mickel_Luiten yes thanks! That helps a lot.

Three question:

does the tests/pairing.js script crash after the DeprecationWarning or do you eventually get a timeout?
does the following url also give you the system response:
https://192.168.2.140:1926/6/system
does your TV run on Android?

(Pro tip: if you wrap pieces of JSON or text in 3 backticks (also known as grave accent ` ) it’ll be displayed in a code block)

    ```
    like this but without the spaces
    ```

Mickel_Luiten · June 5, 2019, 3:18pm

@lucasvdh

1, Scripts hangs after DeprecationWarning and after a while a timeout with error

JointspaceClient response error {“code”:“ECONNRESET”} undefined
An error occurred when trying to confirm the pairing process

{“code”:“ECONNRESET”}
2. No system response with https://192.168.2.140:1926/6/system
3. Yes android

Thanks for the tip

lucasvdh · June 5, 2019, 4:36pm

@Mickel_Luiten thanks for the info, I think I know what the issue is.

I’ve just pushed a new version of the tests/pairing.js script. If not mistaken you should be able to complete the pairing process with that script now. (Get the new version by running git pull origin alpha)

I’ve added manual port selection to the test script. In your case you’d need to select ip 192.168.2.140, api version 6 and port 1925.

Let me know if it works!

Mickel_Luiten · June 5, 2019, 5:05pm

@lucasvdh, pretty sure something wrong.

When i type http://192.168.2.140:1925/6/system in my browse i get a response.
But testscript return "

? What’s your TV’s IP? 192.168.2.140
? What’s your API version? (1 to 6) 6
? What port number should be used? Either 1925 or 1926 1925
Updating client config
Sending system info call
API version as returned by TV: 6
Starting pairing process
Could not reach api endpoint, connection was reset. Incorrect port number?

WHen i do the followiing in the script a get a response but also a error after timeout.
? What’s your TV’s IP? 192.168.2.140
? What’s your API version? (1 to 6) 6
? What port number should be used? Either 1925 or 1926 1926
Updating client config
Sending system info call
API version as returned by TV: 6
Starting pairing process
Successfully started pairing process
? What’s the pin code displayed on the tv? 6209
Sending pin verification: 6209
Unexpected pairing error {“code”:“ECONNRESET”}

lucasvdh · June 10, 2019, 4:11pm

I’ve just published a new version (0.2.0) of the app.

This version fixes the following issues:

Jointspace client not initializing correctly for older Philips TVs which do not require auth
Jointspace client not initializing at all after device or app recovers from a crash
Pairing issues for older TVs
Various bugs when sending commands to tv (I’m working on making these actions available in flows)

The following feature has been added:

Selecting a TV type (Android TV or Other) during pairing

There is still one known issue with Android TVs that prevents you from confirming the pairing process. I’m looking into this but haven’t found a solution yet.

Eduardo_Rodriguez · June 10, 2019, 7:43pm

I have installed the latest version.

In the browser I can enter using ip http://192.168.1.147:1925/1/system, but when I try to pair it in the app it tells me that it can connect to the TV but the api number is incorrect.

In the previous version I managed to match the TV but the application chash after a few seconds.

I have a 65PUS6703/12 whitout android.

lucasvdh · June 11, 2019, 7:32am

@Eduardo_Rodriguez when pairing, what tv type did you select?

Could you also help me by sending the response that you get from the http://192.168.1.147:1925/1/system then I might be able to debug some more.

Thanks in advance.

lucasvdh · June 11, 2019, 7:36am

I currently have some other obligations so I’ll be back in about 2 or 2.5 weeks.

Eduardo_Rodriguez · June 11, 2019, 9:07am

This is my response:

{
	"menulanguage": "Spanish",
	"name": "65PUS6703/12",
	"country": "Spain",
	"serialnumber_encrypted": "K2kseVsmQFgkd15gKkJ+avjDoGct/qJZad6sIi7G+Iw=",
	"softwareversion_encrypted": "K2kseVsmQFgkd15gKkJ+ak3ednbEwu0L3RKYbs0Gj1zjDF1Kd8PWKGcCIghmwRrZ",
	"model_encrypted": "K2kseVsmQFgkd15gKkJ+aomwrvYy3DqdX0gO2ZbGsc4=",
	"deviceid_encrypted": "K2kseVsmQFgkd15gKkJ+avLNWHHkyj1JGMrXxuUbBdo=",
	"nettvversion": "4.6.0.1",
	"epgsource": "ip",
	"api_version": {
		"Major": 6,
		"Minor": 1,
		"Patch": 0
	},
	"featuring": {
		"jsonfeatures": {
			"recordings": [
				"List",
				"Schedule",
				"Manage"
			],
			"ambilight": [
				"Hue",
				"Ambilight"
			],
			"textentry": [
				"context_based",
				"initial_string_available"
			],
			"inputkey": [
				"key",
				"unicode"
			],
			"pointer": [
				"context_based"
			],
			"activities": [
				"browser"
			]
		},
		"systemfeatures": {
			"tvtype": "consumer",
			"content": [
				"dmr"
			],
			"pairing_type": "none",
			"os_type": "Linux"
		}
	}
}

This is the options i set:

And the error:

Topic		Replies	Views
[App][Pro] Sony BRAVIA Android TV Apps homey-pro	120	3266	February 1, 2026
[APP][Pro] Android TV - Take control of your TV experience Apps official , homey-pro	90	4284	June 16, 2026
[APP][Pro] Samsung SmartTV Apps	656	55332	June 17, 2026
[APP][Pro] Android TV - Community (deprecated) Apps homey-pro , community-app	124	6970	February 18, 2025
LG WebOS better integration Apps app	511	27669	May 2, 2026