Ankündigung

**fabian82** · 22.07.2019, 19:18

Ah ok, muss es also nur angeschlossen werden, dass der HS “zufrieden“ ist. Der Befehl, bzw. die Aktion wird aber im Hintergrund ausgeführt. (Will es ja auch verstehen)

**derPaul** · 23.07.2019, 09:50

Korrekt!

**fabian82** · 24.07.2019, 07:16

Also bei mir mit der HS Firmware 4.5 funktioniert es leider nicht.
So sieht die Logik im HS aus:
Philips.jpg
Dummy Auswertung Philips TV = 16Bit EIS10
Input Philips Baustein = 14Bytes

**derPaul** · 24.07.2019, 09:16

Und was kommt bei Dummy Auswertung Philips TV an ?

**fabian82** · 24.07.2019, 11:56

Habe ich mir nicht anzeigen lassen, mache ich bei Gelegenheit mal rein.

**cevers** · 25.07.2019, 08:09

Zitat von EugenDo Beitrag anzeigen

The problem will be Digest. Mostly MD5 is needed... I don't think the HS can do that? Or is there an LBS?

MD5 is available, either with the MD5 lib or the haslib

**geo77** · 04.08.2019, 17:23

I control my Philips 55PFS8109/60 via Gira homeserver. If you have questions, I will try to help.
https://youtu.be/tUmFnwfCoVk?t=71

Angehängte Dateien

**fabian82** · 05.08.2019, 08:08

geo77 your TV dosn't use https, or?
The controls for the QC are very nice, where did you get them from?

**geo77** · 05.08.2019, 18:38

Zitat von fabian82 Beitrag anzeigen

your TV dosn't use https, or?

My TV works with http and https.
I used http.
I installed the Android application "Philips TV Remote"https://play.google.com/store/apps/d...ipstvapp&hl=de. Then I analyzed the traffic between the application and the TV via Wireshark

Zitat von fabian82 Beitrag anzeigen

The controls for the QC are very nice, where did you get them from?

I bought them. https://www.knet.bayern/produkte-1/f...fernbedienung/

**fabian82** · 22.08.2019, 14:49

Zitat von derPaul Beitrag anzeigen

Und was kommt bei Dummy Auswertung Philips TV an ?

Sorry, hat was gedauert. Aber der Wert meines Dummys ist immer 0

**stianj** · 23.08.2019, 07:40

Hmm. Does http://<hs ip>/hslist#Exceptions say anything?

**fabian82** · 30.09.2021, 17:16

Das Thema habe ich nun lange beiseite gelegt und nun erneut angegangen, ich komme jedoch nicht weiter.
Inzwischen hat der HS die Version 4.11.1, nun sollte https ja kein Problem mehr darstellen.

Allerdings bekomme ich es einfach nicht hin.

Mit dem Philips Baustein passiert leider nichts, es kommt auch nichts beim http Request am Ausgang raus.

Zitat von stianj Beitrag anzeigen

Hmm. I think your error is that you try to use basic auth, while the TV needs Digest auth. I use the following curl-commando:

curl -X POST --digest --insecure -u username

assword https://192.168.xxx.yyy:1926/6/ambilight/power -d '{power:Off}' --trace-ascii -

to find the correct headers. Works like a charm for me, Expert 4.8.1.

Have not even thought about this as a possibility before I saw your post, so thank you

Wenn ich dies eingebe kommt folgendes raus:

Code:

curl -X POST --digest --insecure -u smujdQWZlbDfJ8DG:2d963e84e21
23d0796d9bc8e7901b05f02fe9ab33bfae6ed32dff23ff6780 87f https://192.168.178.51:192
6/6/ambilight/power -d '{power:Off}' --trace-ascii -
Note: Unnecessary use of -X or --request, POST is already inferred.
== Info: Trying 192.168.178.51:1926...
== Info: Connected to 192.168.178.51 (192.168.178.51) port 1926 (#0)
== Info: ALPN, offering h2
== Info: ALPN, offering http/1.1
=> Send SSL data, 5 bytes (0x5)
0000: .....
== Info: TLSv1.3 (OUT), TLS handshake, Client hello (1):
=> Send SSL data, 512 bytes (0x200)
0000: ......n.......al......y....L..q^.. .j} ....Bz..J.B,.T....(B.fS..
0040: .j.z.H..>.......,.0.........+./...$.(.k.#.'.g.....9.....3.....=.
0080: <.5./.....u........................3t.........h2.http/1.1.......
00c0: ..1.....0......................................... ........+.....
0100: .......-.....3.&.$... p..N.S.su.....a">%..b....:o...............
0140: .................................................. ..............
0180: .................................................. ..............
01c0: .................................................. ..............
<= Recv SSL data, 5 bytes (0x5)
0000: ....[
== Info: TLSv1.3 (IN), TLS handshake, Server hello (2):
<= Recv SSL data, 91 bytes (0x5b)
0000: ...W..aU.`..;2.3l..-..[i...v..r.:.E.$. .4T./@.6d.......J.....h.0
0040: 6..........................
<= Recv SSL data, 5 bytes (0x5)
0000: .....
== Info: TLSv1.2 (IN), TLS handshake, Certificate (11):
<= Recv SSL data, 3261 bytes (0xcbd)
0000: .........60..20.............`L$J.m0...*.H........0 ..1.0...U....I
0040: N1.0...U....Karnataka1.0...U....Bengaluru1"0 ..U....TP VISION In
0080: dia Pvt. Ltd.1.0...U....Smart TV1.0...U....ca.tpvision.com0...15
00c0: 0519105153Z..421004105153Z0..1.0...U....IN1.0...U. ...Karnataka1.
0100: 0...U....Bengaluru1"0 ..U....TP VISION India Pvt. Ltd.1.0...U...
0140: .Smart TV1.0...U....restfultv.tpvision.com0.."0...*.H.... .......
0180: ..0.........m.....7.r......,....p..a....>.Ts.9/l.........$.. ..H
01c0: n;.M...z.&...go..1Y,...uH.eB...M......c...nb.%.... ..;d......;B..
0200: K....E......e0.F'....j...i=i.O.....).|`..f.G.....I ..e(.....[4-..
0240: #...c.y?.d.<~T.".Z.⌂.Oi..]...o.2.....n.\i.)x3PD&.?.!.......p...}
0280: ...(.1..}..........0..0...U.#..0...f.r...}a..lZ... .....0...U....
02c0: 0.0...U........@..ET.lD.w...N.(..0I..U...B0@..rest fultv.tpvision
0300: .com..xtv.tpvision.com..droidtv.tpvision.com0...*. H.............
0340: zj.".:....1....@7@......\....C.G...5Q.........|... P.YpKS....\4..
0380: ..y.......@.^.. '.%..........L.........u.k.....j./..7...h.AYBd..
03c0: ]3..E.⌂.*!i.;K.-z../..A.$...:r&...]1.w.,5X"....L.e......:......t
0400: ....O~@.-v.....F_.........=...sh..2..8..\.}.iuzS.N.,z.....G 6..!.
0440: ...0...0...............V...0...*.H........0..1.0.. .U....IN1.0...
0480: U....Karnataka1.0...U....Bengaluru1"0 ..U....TP VISION India Pvt
04c0: . Ltd.1.0...U....TP VISION1.0...U....www.tpvision.com0...1505191
0500: 04457Z..421004104457Z0..1.0...U....IN1.0...U....Ka rnataka1.0...U
0540: ....Bengaluru1"0 ..U....TP VISION India Pvt. Ltd.1.0...U....Smar
0580: t TV1.0...U....ca.tpvision.com0.."0...*.H........... ..0.........
05c0: .t.....*F......L...J.f.........`=<]%.....d..F..K#J.\.a..I.u....*
0600: ..."kg.D%t%=T|...7U..I.5..C.D~E...\6p7<rT.e.....YC .)..bD...w..G+
0640: ..=:..0..........9.E...a.]z..S'.t.....l%.>...d...j.A...`.n.g..Pa
0680: .A.7......_.........=~{\0..P.E..G)..E......6.Z.... ....h....;.<%.
06c0: .....V0T0...U.#..0........u.aV..u...T~.I10...U.... ..f.r...}a..lZ
0700: ........0...U.......0.......0...*.H............... ...d ....).*.$
0740: \..SJ..5..v^./..IsC.`).{...(O..Cw7...........U'b#..*6B....&.P..F
0780: ']Q.E.`..c/...I..Z..e/......'...;$.-^.H..t......@wM..w......F_.X
07c0: ....................b2.j..M..l.*m..U......oF7⌂1m%. C..&..<...../.
0800: .-...t.=!..0.J.G..Yn...^..jre.$.....+.v.⌂aL_IKKc...0 ...0..n.....
0840: ........`..0...*.H........0..1.0...U....IN1.0...U. ...Karnataka1.
0880: 0...U....Bengaluru1"0 ..U....TP VISION India Pvt. Ltd.1.0...U...
08c0: .TP VISION1.0...U....www.tpvision.com0...150519102346Z ..42100410
0900: 2346Z0..1.0...U....IN1.0...U....Karnataka1.0...U.. ..Bengaluru1"0
0940: ..U....TP VISION India Pvt. Ltd.1.0...U....TP VISION1.0...U....
0980: www.tpvision.com0.."0...*.H.............0......... JE(....=..J..f
09c0: s]...y..x*4y.....Z..(...`k.RE......^.L.*....B../...98....]yko...
0a00: .........<%....06.bH....bI&.L.q.A.Z+....b.^.sD.?.+ .N..w..g..[.O.
0a40: ....*.f.u...L..⌂i..42.nu8qP<....1..v...R.i.':....! .=^.....v.....
0a80: .).G.7,.....r.].J...cy.R#.d.@.e${...A..\..c@S..?.........0..0...
0ac0: U...........u.aV..u...T~.I10....U.#...0.........u. aV..u...T~.I1.
0b00: .....0..1.0...U....IN1.0...U....Karnataka1.0...U.. ..Bengaluru1"0
0b40: ..U....TP VISION India Pvt. Ltd.1.0...U....TP VISION1.0...U....
0b80: www.tpvision.com........`..0...U....0....0...*.H.. ..............
0bc0: q2......~,...Y. ...3.f.!..)@...i..8...IxS......':...C..t.d0..aS.
0c00: ]...(....[.X|.....,..#.>....=.Y......jf.<D.R..........}..<.. ^...
0c40: ..m%....{q...wR....T.⌂.mWreE.@T....2?PR.L...C..!.. ..Tl...U_.I...
0c80: qY..tj.7C....@...@E.'~`k=....i7..q..%R......k....V Y.(..2.p.@.
<= Recv SSL data, 5 bytes (0x5)
0000: ....,
== Info: TLSv1.2 (IN), TLS handshake, Server key exchange (12):
<= Recv SSL data, 300 bytes (0x12c)
0000: ...(... ........U.f...C.P..j.S....$.w.......'.....].7.).C..9..gL
0040: ;Y..G......:W...>......@w"........hj.⌂..d.D.M0f.8F >h....Z.....>%
0080: K...-SW....q{.4=.XX..`2.⌂...!..#.....zx.]........nO.!r.)..y.RFO.
00c0: .5N+.^.MN..!....... .. x.<r..>...1}.&.⌂...F.g...^..C.....J......
0100: .....!18.....1......0.\........?..._....VI.C
<= Recv SSL data, 5 bytes (0x5)
0000: .....
== Info: TLSv1.2 (IN), TLS handshake, Server finished (14):
<= Recv SSL data, 4 bytes (0x4)
0000: ....
=> Send SSL data, 5 bytes (0x5)
0000: ....%
== Info: TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
=> Send SSL data, 37 bytes (0x25)
0000: ...! ...<.....,v(&|Q⌂.c..fV....)..Po.
=> Send SSL data, 5 bytes (0x5)
0000: .....
== Info: TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
=> Send SSL data, 1 bytes (0x1)
0000: .
=> Send SSL data, 5 bytes (0x5)
0000: ....
== Info: TLSv1.2 (OUT), TLS handshake, Finished (20):
=> Send SSL data, 16 bytes (0x10)
0000: ....,..`..a....#
<= Recv SSL data, 5 bytes (0x5)
0000: .....
<= Recv SSL data, 5 bytes (0x5)
0000: ....
== Info: TLSv1.2 (IN), TLS handshake, Finished (20):
<= Recv SSL data, 16 bytes (0x10)
0000: .......l.._...l.
== Info: SSL connection using TLSv1.2 / ECDHE-RSA-CHACHA20-POLY1305
== Info: ALPN, server did not agree to a protocol
== Info: Server certificate:
== Info: subject: C=IN; ST=Karnataka; L=Bengaluru; O=TP VISION India Pvt. Ltd.;
OU=Smart TV; CN=restfultv.tpvision.com
== Info: start date: May 19 10:51:53 2015 GMT
== Info: expire date: Oct 4 10:51:53 2042 GMT
== Info: issuer: C=IN; ST=Karnataka; L=Bengaluru; O=TP VISION India Pvt. Ltd.;
OU=Smart TV; CN=ca.tpvision.com
== Info: SSL certificate verify result: self signed certificate in certificate
chain (19), continuing anyway.
== Info: Server auth using Digest with user 'smujdQWZlbDfJ8DG'
=> Send SSL data, 5 bytes (0x5)
0000: .....
=> Send header, 169 bytes (0xa9)
0000: POST /6/ambilight/power HTTP/1.1
0022: Host: 192.168.178.51:1926
003d: User-Agent: curl/7.77.0
0056: Accept: */*
0063: Content-Length: 0
0076: Content-Type: application/x-www-form-urlencoded
00a7:
<= Recv SSL data, 5 bytes (0x5)
0000: .....
== Info: Mark bundle as not supporting multiuse
<= Recv header, 27 bytes (0x1b)
0000: HTTP/1.1 401 Unauthorized
<= Recv header, 43 bytes (0x2b)
0000: Date: Thu, 30 Sep 2021 16:10:08 GMT+00:00
<= Recv header, 22 bytes (0x16)
0000: Accept-Ranges: bytes
<= Recv header, 34 bytes (0x22)
0000: Server: Restlet-Framework/2.3.12
<= Recv header, 151 bytes (0x97)
0000: WWW-Authenticate: Digest realm="XTV", domain="/", nonce="MTYzMzA
0040: xODIwODM5MDplOWQ0NDEwZmQ2MDgxYjNkYzc5NzRhZGFjNWI3Z TgwZQ==", algo
0080: rithm=MD5, qop="auth"
<= Recv header, 21 bytes (0x15)
0000: Content-Length: 424
<= Recv header, 40 bytes (0x28)
0000: Content-Type: text/html; charset=UTF-8
<= Recv header, 2 bytes (0x2)
0000:
== Info: Ignoring the response-body
<= Recv data, 424 bytes (0x1a8)
0000: <html>.<head>. <title>Status page</title>.</head>.<body style=
0040: "font-family: sans-serif;">.<p style="font-size: 1.2em;font-weig
0080: ht: bold;margin: 1em 0px;">Unauthorized</p>.<p>The request requi
00c0: res user authentication</p>.<p>You can get technical details <a
0100: href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec
0140: 10.4.2">here</a>.<br>.Please continue your visit at our <a href=
0180: "/">home page</a>..</p>.</body>.</html>.
== Info: Connection #0 to host 192.168.178.51 left intact
== Info: Issue another request to this URL: 'https://192.168.178.51:1926/6/ambil
ight/power'
== Info: Found bundle for host 192.168.178.51: 0x75b918 [serially]
== Info: Can not multiplex, even if we wanted to!
== Info: Re-using existing connection! (#0) with host 192.168.178.51
== Info: Connected to 192.168.178.51 (192.168.178.51) port 1926 (#0)
== Info: Server auth using Digest with user 'smujdQWZlbDfJ8DG'
=> Send SSL data, 5 bytes (0x5)
0000: .....
=> Send header, 454 bytes (0x1c6)
0000: POST /6/ambilight/power HTTP/1.1
0022: Host: 192.168.178.51:1926
003d: Authorization: Digest username="smujdQWZlbDfJ8DG",realm="XTV",no
007d: nce="MTYzMzAxODIwODM5MDplOWQ0NDEwZmQ2MDgxYjNkYzc5N zRhZGFjNWI3ZTg
00bd: wZQ==",uri="/6/ambilight/power",cnonce="6e4cbf7c125c06a5004929cc
00fd: 93ca53d1",nc=00000001,algorithm=MD5,response="a005 db76e10b230d59
013d: 6d4a5c948c4e13",qop="auth"
0159: User-Agent: curl/7.77.0
0172: Accept: */*
017f: Content-Length: 13
0193: Content-Type: application/x-www-form-urlencoded
01c4:
=> Send data, 13 bytes (0xd)
0000: '{power:Off}'
<= Recv SSL data, 5 bytes (0x5)
0000: .....
== Info: Mark bundle as not supporting multiuse
<= Recv header, 17 bytes (0x11)
0000: HTTP/1.1 200 OK
<= Recv header, 43 bytes (0x2b)
0000: Date: Thu, 30 Sep 2021 16:10:08 GMT+00:00
<= Recv header, 22 bytes (0x16)
0000: Accept-Ranges: bytes
<= Recv header, 34 bytes (0x22)
0000: Server: Restlet-Framework/2.3.12
<= Recv header, 32 bytes (0x20)
0000: Access-Control-Allow-Origin: *
<= Recv header, 19 bytes (0x13)
0000: Content-Length: 0
<= Recv header, 2 bytes (0x2)
0000:
== Info: Connection #0 to host 192.168.178.51 left intact

**fabian82** · 03.10.2021, 16:14

So, ein erster Lichtblick! Diese beiden Befehle funktionieren (vom PC aus):

Ambilight an:

Code:

curl -XPOST -u smujdQWZlbDfJ8DG:2d963e84e2123d0796d9bc8e7901b05f02fe9ab33bfae6ed32dff23ff678087f https://192.168.178.51:1926/6/ambilight/currentconfiguration -d "{"styleName":"FOLLOW_VIDEO","isExpert":false,"menuSetting":"IMMERSIVE"}" -k --digest -v

Ambilight aus:

Code:

curl -XPOST -u smujdQWZlbDfJ8DG:2d963e84e2123d0796d9bc8e7901b05f02fe9ab33bfae6ed32dff23ff678087f https://192.168.178.51:1926/6/ambilight/power -d "{'power': 'Off'}" -k --digest -v

Nur wie bekomme ich diese Befehle mit dem HS gesendet?

Da sich mein TV scheinbar nicht anpingen lässt und der HS somit nicht weiß, wann er an ist bekommt man mit diesem Aufruf

Code:

https://smujdQWZlbDfJ8DG:2d963e84e2123d0796d9bc8e7901b05f02fe9ab33bfae6ed32dff23ff678087f@192.168.178.51:1926/6/powerstate

im Browser

Code:

{"powerstate":"On"}

**fabian82** · 09.10.2021, 10:17

Immer wieder mal probiere ich hier rum, mit diversen Programmen ala Postman oder HS, allerdings bekomme ich es über diesen weg nicht hin.
Bei den cUrl Befehlen habe ich noch ein wenig rum gespielt, das X vor dem Post kann ich auch (ohne für mich erkennbare) Wirkung im Befehl weg lassen, ich glaube so steht es auch in der Ausgabe vom TV.
Das -v kann ebenso weg gelassen werden, dann kommt jedoch keine Antwort vom Fernseher, geschalten wird aber.
Die Befehle sehen gekürzt dann so aus:

Ambilight an:

Code:

curl -POST -u smujdQWZlbDfJ8DG:2d963e84e2123d0796d9bc8e7901b05f02fe9ab33bfae6ed32dff23ff678087f https://192.168.178.51:1926/6/ambilight/currentconfiguration -d "{"styleName":"FOLLOW_VIDEO","isExpert":false,"menuSetting":"IMMERSIVE"}" -k --digest

Ambilight aus:

Code:

curl -POST -u smujdQWZlbDfJ8DG:2d963e84e2123d0796d9bc8e7901b05f02fe9ab33bfae6ed32dff23ff678087f https://192.168.178.51:1926/6/ambilight/power -d "{'power': 'Off'}" -k --digest

Ein erfolgreicher cUrl Befehl (mit -v) gibt dann folgendes aus:

Code:

C:\Users\Fabian>curl -XPOST -u smujdQWZlbDfJ8DG:2d963e84e2123d0796d9bc8e7901b05f
02fe9ab33bfae6ed32dff23ff678087f https://192.168.178.51:1926/6/ambilight/current
configuration -d "{"styleName":"FOLLOW_VIDEO","isExpert":false,"men uSetting":"IM
MERSIVE"}" -k --digest -v
Note: Unnecessary use of -X or --request, POST is already inferred.
* Trying 192.168.178.51:1926...
* Connected to 192.168.178.51 (192.168.178.51) port 1926 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-CHACHA20-POLY1305
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: C=IN; ST=Karnataka; L=Bengaluru; O=TP VISION India Pvt. Ltd.; OU=Sma
rt TV; CN=restfultv.tpvision.com
* start date: May 19 10:51:53 2015 GMT
* expire date: Oct 4 10:51:53 2042 GMT
* issuer: C=IN; ST=Karnataka; L=Bengaluru; O=TP VISION India Pvt. Ltd.; OU=Smar
t TV; CN=ca.tpvision.com
* SSL certificate verify result: self-signed certificate in certificate chain (
19), continuing anyway.
* Server auth using Digest with user 'smujdQWZlbDfJ8DG'
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
> POST /6/ambilight/currentconfiguration HTTP/1.1
> Host: 192.168.178.51:1926
> User-Agent: curl/7.79.1
> Accept: */*
> Content-Length: 0
> Content-Type: application/x-www-form-urlencoded
>
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Mark bundle as not supporting multiuse
< HTTP/1.1 401 Unauthorized
< Date: Sat, 09 Oct 2021 08:56:49 GMT+00:00
< Accept-Ranges: bytes
< Server: Restlet-Framework/2.3.12
< WWW-Authenticate: Digest realm="XTV", domain="/", nonce="MTYzMzc2OTgwOTI0MToxY
mM1MTk4ZjcyMzA5MGM0YWQyNzIwMGU0Y2I1M2QwYw==", algorithm=MD5, qop="auth"
< Content-Length: 424
< Content-Type: text/html; charset=UTF-8
<
* Ignoring the response-body
* Connection #0 to host 192.168.178.51 left intact
* Issue another request to this URL: 'https://192.168.178.51:1926/6/ambilight/cu
rrentconfiguration'
* Found bundle for host 192.168.178.51: 0x719260 [serially]
* Can not multiplex, even if we wanted to!
* Re-using existing connection! (#0) with host 192.168.178.51
* Connected to 192.168.178.51 (192.168.178.51) port 1926 (#0)
* Server auth using Digest with user 'smujdQWZlbDfJ8DG'
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
> POST /6/ambilight/currentconfiguration HTTP/1.1
> Host: 192.168.178.51:1926
> Authorization: Digest username="smujdQWZlbDfJ8DG",realm="XTV",nonce="MTY zMzc2O
TgwOTI0MToxYmM1MTk4ZjcyMzA5MGM0YWQyNzIwMGU0Y2I1M2Q wYw==",uri="/6/ambilight/curre
ntconfiguration",cnonce="88a9fca8f182ead25ae75a151 60609df",nc=00000001,algorithm
=MD5,response="a357d309e72ff61c9c35f21d8799a00b",q op="auth"
> User-Agent: curl/7.79.1
> Accept: */*
> Content-Length: 61
> Content-Type: application/x-www-form-urlencoded
>
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Sat, 09 Oct 2021 08:56:49 GMT+00:00
< Accept-Ranges: bytes
< Server: Restlet-Framework/2.3.12
< Access-Control-Allow-Origin: *
< Content-Length: 0
<
* Connection #0 to host 192.168.178.51 left intact

C:\Users\Fabian>

Nur mit dem HS bekomme ich es nicht hin, kann mir da jemand helfen?

**EugenDo** · 09.10.2021, 11:02

fabian82

ich glaube, dass deine Herausforderung die Digest Authentifizierung sein wird … das kann der HS mWn aktuell nur bei den Kameras… dann musst du ja schon 2 Abfragen in Serie bauen, damit das klappt… dazwischen musst du aus der ersten Antwort den richtigen Auth-Header für die zweite Anfrage zusammen bauen … wie man die Digest Header zusammenbauen kann, muss man halt googeln… vllt. kann man aber bei dem Fernseher die Authentifizierung abstellen.

Ankündigung

Philips Android TV über IP (HS) steuern

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar