Hi, thanks for the great work on this project. I am messing around with a more user friendly way to control the Ambilight (65OLED806) for custom colours. Basically I have a small webpage with a colour wheel that allows you to send the appropriate command. However, I'm currently calling a Python subprocess to execute it, which is not very efficient, especially if I want to send a bunch of commands quickly.
Have you thought about adapting pylips to work as a module (i.e. import pylips)? From what I gather the current implementation establishes a new connection for every command that you want to send. Is that a requirement, or could we keep the connection alive?
I suppose for my personal use case it may be even better to use ADB? Eventually I would like to expand the 'remote' to offer a way of customising your preferred settings and having them available as simple buttons on the page, and having scheduled changes to settings (e.g. daytime / nighttime picture modes). Also thinking about incorporating an ambient light sensor to adjust the brightness of the Ambilight. And maybe even replace/expand the built in light sensor.
One final side-question: does anyone know anything about setting Ambilight per side? The official Philips mobile remote app offers this for top and sides only, but not for the bottom. I could not find any mention of this functionality in the commands JSON I got from my tv.
EDIT: I found the ambilight/cached path in the API reference, I assume that's how the colour is set per side!
Hi, thanks for the great work on this project. I am messing around with a more user friendly way to control the Ambilight (65OLED806) for custom colours. Basically I have a small webpage with a colour wheel that allows you to send the appropriate command. However, I'm currently calling a Python subprocess to execute it, which is not very efficient, especially if I want to send a bunch of commands quickly.
Have you thought about adapting pylips to work as a module (i.e. import pylips)? From what I gather the current implementation establishes a new connection for every command that you want to send. Is that a requirement, or could we keep the connection alive?
I suppose for my personal use case it may be even better to use ADB? Eventually I would like to expand the 'remote' to offer a way of customising your preferred settings and having them available as simple buttons on the page, and having scheduled changes to settings (e.g. daytime / nighttime picture modes). Also thinking about incorporating an ambient light sensor to adjust the brightness of the Ambilight. And maybe even replace/expand the built in light sensor.
One final side-question: does anyone know anything about setting Ambilight per side? The official Philips mobile remote app offers this for top and sides only, but not for the bottom. I could not find any mention of this functionality in the commands JSON I got from my tv.
EDIT: I found the ambilight/cached path in the API reference, I assume that's how the colour is set per side!