Skip to content

Add support for v6 features to philips js integration #16628

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
balloob merged 7 commits into from
Feb 26, 2021
Merged

Add support for v6 features to philips js integration #16628

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
756bc5d
Update documentation somewhat for paired support
elupus Feb 17, 2021
9ab28a2
Adjust linting
elupus Feb 17, 2021
99a5eab
Update source/_integrations/philips_js.markdown
elupus Feb 18, 2021
dcbefd6
Adjust known issues
elupus Feb 20, 2021
e922142
Add aa table with feature support
elupus Feb 23, 2021
52e2bf8
Lint fix
elupus Feb 23, 2021
89438db
Drop known issues
elupus Feb 23, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 24 additions & 3 deletions source/_integrations/philips_js.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,10 +11,31 @@ ha_domain: philips_js
ha_config_flow: true
---

The `philips_js` platform allows you to control Philips TVs which expose the [jointSPACE](http://jointspace.sourceforge.net/) JSON-API. Instructions on how to activate the API and if your model is supported can be found [here](http://jointspace.sourceforge.net/download.html). Note that not all listed, jointSPACE-enabled devices will have JSON-interface running on port 1925. This is true at least for some models before year 2011.
The `philips_js` platform allows you to control Philips TVs which expose the [jointSPACE](http://jointspace.sourceforge.net/) JSON-API.

To enable the integration go to **Configuration** -> **Integrations**
Instructions on how to activate the API and if your model is supported can be found [here](http://jointspace.sourceforge.net/download.html). Note that not all listed, jointSPACE-enabled devices will have JSON-interface running on port 1925. This is true at least for some models before year 2011.

{% include integrations/config_flow.md %}

### Features

| Feature | 1 | 5 | 6 (Android) | 6 (Saphi) |
| ------------------ | ---------------- | --- | ------------------ | ---------------- |
| Power On | WOL / IR Blaster | ? | Yes (if always on) | WOL / IR Blaster |
| Volume Detect | Yes | ? | Yes (not over CEC) | ? |
| Volume Up/Down | Yes | ? | Yes | No |
| Volume Set | Yes | ? | Yes | ? |
| Source Select | Yes | ? | Yes | No |
| Source Detect | Yes | ? | No | No |
| Channel Select | Yes | ? | Yes | ? |
| Channel Detect | Yes | ? | Yes | ? |
| Channel Favorites | No | ? | Yes | ? |
| Application Select | No | ? | Yes | No |
| Application Detect | No | ? | Yes | No |
| Browse URL | No | No | No | No |
| Send Key | No | No | No | No |
| Ambilight Control | No | No | No | No |

### Turn on device

The Philips TV does not support turning on via the API. You can either turn it on via IR blaster to or on som models WOL. To trigger this command from the entities, the integration exposes a `device trigger` that can be setup to execute when the `media_player` is asked to turn on.
The Philips TV does not always support turning on via the API. You can either turn it on via IR blaster or on som models WOL. To trigger this command from the entities, the integration exposes a `device trigger` that can be setup to execute when the `media_player` is asked to turn on.