Test Adapter Philips-TV v0.2.x
-
Hallo ich habe einen 55pus7100/r2
Adapter alpha 07 und 6er Api …leider bleibt auch bei mir der Adapter auf Gelb.
https://ip:1926/system ergibt folgendes
! {"notifyChange":"http","menulanguage":"German","name":"PhilipsTV","country":"Germany","serialnumber_encrypted":"Cf0h48SyQzPD+lQSoZVfNVE7AfK/Gmy8pquN/Akd3lc=\n","softwareversion_encrypted":"K1EHxhvIY7n4W2lRCkgean1NCYUo/JtZ9E1xDpftz/Q=\n","model_encrypted":"Jo29ZcjddaSn5mLyyCDZpmGPCWa/oimynXxvsb8Q1Yc=\n","deviceid_encrypted":"Y09p4wF166IWQDMuDRZb3RfuV+UdxF8WL+1fF4EZqso=\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"}}}
Log-Auszug:
! refresh pausedelete delete_foreverLOG HERUNTERLADENLog-Größe: 0.09 MB
! Zeit
! Meldung
! admin.0 2018-11-24 18:16:04.875 info Repository received successfully.
! host.ioBroker-RasPi 2018-11-24 18:16:03.992 info Update repository "default" under "http://download.iobroker.net/sources-dist.json"
! admin.0 2018-11-24 18:16:03.890 info Request actual repository…
! host.ioBroker-RasPi 2018-11-24 17:57:29.343 info instance system.adapter.philips-tv.0 terminated with code 0 (OK)
! philips-tv.0 2018-11-24 17:57:29.306 info terminating
! host.ioBroker-RasPi 2018-11-24 17:57:29.288 info stopInstance system.adapter.philips-tv.0 killing pid 2499
! host.ioBroker-RasPi 2018-11-24 17:57:29.287 info stopInstance system.adapter.philips-tv.0
! host.ioBroker-RasPi 2018-11-24 17:57:29.286 info "system.adapter.philips-tv.0" disabled
! host.ioBroker-RasPi 2018-11-24 17:57:29.285 info object change system.adapter.philips-tv.0
! philips-tv.0 2018-11-24 17:57:26.483 info starting. Version 0.3.0-alpha7 in /opt/iobroker/node_modules/iobroker.philips-tv, node: v8.11.1
! philips-tv.0 2018-11-24 17:57:26.398 info States connected to redis: 127.0.0.1:6379
! host.ioBroker-RasPi 2018-11-24 17:57:24.582 info instance system.adapter.philips-tv.0 started with pid 2499
! host.ioBroker-RasPi 2018-11-24 17:57:22.098 info instance system.adapter.philips-tv.0 terminated with code 0 (OK)
! philips-tv.0 2018-11-24 17:57:22.068 info terminating
! host.ioBroker-RasPi 2018-11-24 17:57:22.050 info stopInstance system.adapter.philips-tv.0 killing pid 2308
! host.ioBroker-RasPi 2018-11-24 17:57:22.050 info stopInstance system.adapter.philips-tv.0
! host.ioBroker-RasPi 2018-11-24 17:57:22.049 info object change system.adapter.philips-tv.0
! philips-tv.0 2018-11-24 17:57:20.720 debug attempt 1 of 3
! philips-tv.0 2018-11-24 17:57:20.719 debug checking if connection is alive
! philips-tv.0 2018-11-24 17:57:20.718 debug initializing connection to 192.168.178.66
! philips-tv.0 2018-11-24 17:57:10.715 debug state with id philips-tv.0.info.apiVersion updated: ack=true; val=not found
! philips-tv.0 2018-11-24 17:57:10.714 debug redis pmessage io.philips-tv.0.* io.philips-tv.0.info.apiVersion {"val":"not found","ack":true,"ts":1543078630706,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057484988}
! philips-tv.0 2018-11-24 17:57:10.712 debug Could not initialize connection. Reason: No connection to host 192.168.178.66
! philips-tv.0 2018-11-24 17:57:10.705 debug connection is DEAD. Reason: [undefined] Error: ETIMEDOUT
! philips-tv.0 2018-11-24 17:57:10.704 debug no further attempts
! philips-tv.0 2018-11-24 17:57:10.703 debug error is not recoverable
! philips-tv.0 2018-11-24 17:57:10.703 debug attempt 1 failed with code undefined
! philips-tv.0 2018-11-24 17:57:05.696 debug attempt 1 of 3
! philips-tv.0 2018-11-24 17:57:05.695 debug checking if connection is alive
! philips-tv.0 2018-11-24 17:57:05.694 debug initializing connection to 192.168.178.66
! philips-tv.0 2018-11-24 17:56:55.692 debug state with id philips-tv.0.info.apiVersion updated: ack=true; val=not found
! philips-tv.0 2018-11-24 17:56:55.691 debug redis pmessage io.philips-tv.0.* io.philips-tv.0.info.apiVersion {"val":"not found","ack":true,"ts":1543078615682,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057484988}
! philips-tv.0 2018-11-24 17:56:55.688 debug Could not initialize connection. Reason: No connection to host 192.168.178.66
! philips-tv.0 2018-11-24 17:56:55.680 debug connection is DEAD. Reason: [undefined] Error: ETIMEDOUT
! philips-tv.0 2018-11-24 17:56:55.680 debug no further attempts
! philips-tv.0 2018-11-24 17:56:55.679 debug error is not recoverable
! philips-tv.0 2018-11-24 17:56:55.678 debug attempt 1 failed with code undefined
! philips-tv.0 2018-11-24 17:56:50.668 debug attempt 1 of 3
! philips-tv.0 2018-11-24 17:56:50.667 debug checking if connection is alive
! philips-tv.0 2018-11-24 17:56:50.666 debug initializing connection to 192.168.178.66
! philips-tv.0 2018-11-24 17:56:40.665 debug state with id philips-tv.0.info.apiVersion updated: ack=true; val=not found
! philips-tv.0 2018-11-24 17:56:40.664 debug redis pmessage io.philips-tv.0.* io.philips-tv.0.info.apiVersion {"val":"not found","ack":true,"ts":1543078600652,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057484988}
! philips-tv.0 2018-11-24 17:56:40.662 debug Could not initialize connection. Reason: No connection to host 192.168.178.66
! philips-tv.0 2018-11-24 17:56:40.650 debug connection is DEAD. Reason: [undefined] Error: ETIMEDOUT
! philips-tv.0 2018-11-24 17:56:40.649 debug no further attempts
! philips-tv.0 2018-11-24 17:56:40.648 debug error is not recoverable
! philips-tv.0 2018-11-24 17:56:40.647 debug attempt 1 failed with code undefined
! philips-tv.0 2018-11-24 17:56:35.640 debug attempt 1 of 3
! philips-tv.0 2018-11-24 17:56:35.639 debug checking if connection is alive
! philips-tv.0 2018-11-24 17:56:35.638 debug initializing connection to 192.168.178.66
! philips-tv.0 2018-11-24 17:56:25.635 debug state with id philips-tv.0.info.apiVersion updated: ack=true; val=not found
! philips-tv.0 2018-11-24 17:56:25.634 debug redis pmessage io.philips-tv.0.* io.philips-tv.0.info.apiVersion {"val":"not found","ack":true,"ts":1543078585627,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057484988}
! philips-tv.0 2018-11-24 17:56:25.632 debug Could not initialize connection. Reason: No connection to host 192.168.178.66
! philips-tv.0 2018-11-24 17:56:25.625 debug connection is DEAD. Reason: [undefined] Error: ETIMEDOUT
! philips-tv.0 2018-11-24 17:56:25.624 debug no further attempts
! philips-tv.0 2018-11-24 17:56:25.624 debug error is not recoverable
! philips-tv.0 2018-11-24 17:56:25.623 debug attempt 1 failed with code undefined
! philips-tv.0 2018-11-24 17:56:20.612 debug attempt 1 of 3
! philips-tv.0 2018-11-24 17:56:20.611 debug checking if connection is alive
! philips-tv.0 2018-11-24 17:56:20.610 debug initializing connection to 192.168.178.66
! philips-tv.0 2018-11-24 17:56:10.608 debug state with id philips-tv.0.info.apiVersion updated: ack=true; val=not found
! philips-tv.0 2018-11-24 17:56:10.607 debug redis pmessage io.philips-tv.0.* io.philips-tv.0.info.apiVersion {"val":"not found","ack":true,"ts":1543078570600,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057484988}
! philips-tv.0 2018-11-24 17:56:10.605 debug Could not initialize connection. Reason: No connection to host 192.168.178.66
! philips-tv.0 2018-11-24 17:56:10.598 debug connection is DEAD. Reason: [undefined] Error: ETIMEDOUT
! philips-tv.0 2018-11-24 17:56:10.598 debug no further attempts
! philips-tv.0 2018-11-24 17:56:10.597 debug error is not recoverable
! philips-tv.0 2018-11-24 17:56:10.596 debug attempt 1 failed with code undefined
! philips-tv.0 2018-11-24 17:56:05.586 debug attempt 1 of 3
! philips-tv.0 2018-11-24 17:56:05.585 debug checking if connection is alive
! philips-tv.0 2018-11-24 17:56:05.584 debug initializing connection to 192.168.178.66
! philips-tv.0 2018-11-24 17:56:03.841 debug system.adapter.admin.0: logging true
! philips-tv.0 2018-11-24 17:56:03.840 debug redis pmessage io..logging io.system.adapter.admin.0.logging {"val":true,"ack":true,"ts":1543078563839,"q":0,"from":"system.adapter.admin.0","lc":1543078563839}
! philips-tv.0 2018-11-24 17:55:55.582 debug state with id philips-tv.0.info.apiVersion updated: ack=true; val=not found
! philips-tv.0 2018-11-24 17:55:55.581 debug redis pmessage io.philips-tv.0. io.philips-tv.0.info.apiVersion {"val":"not found","ack":true,"ts":1543078555577,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057484988}
! philips-tv.0 2018-11-24 17:55:55.580 debug Could not initialize connection. Reason: No connection to host 192.168.178.66
! philips-tv.0 2018-11-24 17:55:55.575 debug connection is DEAD. Reason: [undefined] Error: ETIMEDOUT
! philips-tv.0 2018-11-24 17:55:55.575 debug no further attempts
! philips-tv.0 2018-11-24 17:55:55.574 debug error is not recoverable
! philips-tv.0 2018-11-24 17:55:55.573 debug attempt 1 failed with code undefined
! philips-tv.0 2018-11-24 17:55:50.566 debug attempt 1 of 3
! philips-tv.0 2018-11-24 17:55:50.566 debug checking if connection is alive
! philips-tv.0 2018-11-24 17:55:50.565 debug initializing connection to 192.168.178.66
! philips-tv.0 2018-11-24 17:55:40.563 debug state with id philips-tv.0.info.apiVersion updated: ack=true; val=not found
! philips-tv.0 2018-11-24 17:55:40.562 debug redis pmessage io.philips-tv.0.* io.philips-tv.0.info.apiVersion {"val":"not found","ack":true,"ts":1543078540558,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057484988}
! philips-tv.0 2018-11-24 17:55:40.560 debug Could not initialize connection. Reason: No connection to host 192.168.178.66
! philips-tv.0 2018-11-24 17:55:40.556 debug connection is DEAD. Reason: [undefined] Error: ETIMEDOUT
! philips-tv.0 2018-11-24 17:55:40.555 debug no further attempts
! philips-tv.0 2018-11-24 17:55:40.555 debug error is not recoverable
! philips-tv.0 2018-11-24 17:55:40.554 debug attempt 1 failed with code undefined
! philips-tv.0 2018-11-24 17:55:35.542 debug attempt 1 of 3
! philips-tv.0 2018-11-24 17:55:35.542 debug checking if connection is alive
! philips-tv.0 2018-11-24 17:55:35.541 debug initializing connection to 192.168.178.66
! philips-tv.0 2018-11-24 17:55:25.539 debug state with id philips-tv.0.info.apiVersion updated: ack=true; val=not found
! philips-tv.0 2018-11-24 17:55:25.538 debug redis pmessage io.philips-tv.0.* io.philips-tv.0.info.apiVersion {"val":"not found","ack":true,"ts":1543078525534,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057484988}
! philips-tv.0 2018-11-24 17:55:25.536 debug Could not initialize connection. Reason: No connection to host 192.168.178.66
! philips-tv.0 2018-11-24 17:55:25.532 debug connection is DEAD. Reason: [undefined] Error: ETIMEDOUT
! philips-tv.0 2018-11-24 17:55:25.531 debug no further attempts
! philips-tv.0 2018-11-24 17:55:25.531 debug error is not recoverable
! philips-tv.0 2018-11-24 17:55:25.529 debug attempt 1 failed with code undefined
! philips-tv.0 2018-11-24 17:55:20.519 debug attempt 1 of 3
! philips-tv.0 2018-11-24 17:55:20.518 debug checking if connection is alive
! philips-tv.0 2018-11-24 17:55:20.517 debug initializing connection to 192.168.178.66
! philips-tv.0 2018-11-24 17:55:10.515 debug state with id philips-tv.0.info.apiVersion updated: ack=true; val=not found
! philips-tv.0 2018-11-24 17:55:10.514 debug redis pmessage io.philips-tv.0.* io.philips-tv.0.info.apiVersion {"val":"not found","ack":true,"ts":1543078510509,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057484988}
! philips-tv.0 2018-11-24 17:55:10.512 debug Could not initialize connection. Reason: No connection to host 192.168.178.66
! philips-tv.0 2018-11-24 17:55:10.508 debug connection is DEAD. Reason: [undefined] Error: ETIMEDOUT
! philips-tv.0 2018-11-24 17:55:10.507 debug no further attempts
! philips-tv.0 2018-11-24 17:55:10.507 debug error is not recoverable
! philips-tv.0 2018-11-24 17:55:10.506 debug attempt 1 failed with code undefined
! philips-tv.0 2018-11-24 17:55:05.495 debug attempt 1 of 3
! philips-tv.0 2018-11-24 17:55:05.494 debug checking if connection is alive
! philips-tv.0 2018-11-24 17:55:05.493 debug initializing connection to 192.168.178.66
! philips-tv.0 2018-11-24 17:54:55.491 debug state with id philips-tv.0.info.apiVersion updated: ack=true; val=not found
! philips-tv.0 2018-11-24 17:54:55.490 debug redis pmessage io.philips-tv.0.* io.philips-tv.0.info.apiVersion {"val":"not found","ack":true,"ts":1543078495486,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057484988}
! philips-tv.0 2018-11-24 17:54:55.489 debug Could not initialize connection. Reason: No connection to host 192.168.178.66
! philips-tv.0 2018-11-24 17:54:55.485 debug connection is DEAD. Reason: [undefined] Error: ETIMEDOUT
! philips-tv.0 2018-11-24 17:54:55.484 debug no further attempts
! philips-tv.0 2018-11-24 17:54:55.483 debug error is not recoverable
! philips-tv.0 2018-11-24 17:54:55.482 debug attempt 1 failed with code undefined
! philips-tv.0 2018-11-24 17:54:50.472 debug attempt 1 of 3
! philips-tv.0 2018-11-24 17:54:50.471 debug checking if connection is alive
! philips-tv.0 2018-11-24 17:54:50.470 debug initializing connection to 192.168.178.66
! philips-tv.0 2018-11-24 17:54:40.468 debug state with id philips-tv.0.info.apiVersion updated: ack=true; val=not found
! philips-tv.0 2018-11-24 17:54:40.467 debug redis pmessage io.philips-tv.0.* io.philips-tv.0.info.apiVersion {"val":"not found","ack":true,"ts":1543078480463,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057484988}
! philips-tv.0 2018-11-24 17:54:40.465 debug Could not initialize connection. Reason: No connection to host 192.168.178.66
! philips-tv.0 2018-11-24 17:54:40.461 debug connection is DEAD. Reason: [undefined] Error: ETIMEDOUT
! philips-tv.0 2018-11-24 17:54:40.460 debug no further attempts
! philips-tv.0 2018-11-24 17:54:40.460 debug error is not recoverable
! philips-tv.0 2018-11-24 17:54:40.459 debug attempt 1 failed with code undefined
! philips-tv.0 2018-11-24 17:54:35.453 debug attempt 1 of 3
! philips-tv.0 2018-11-24 17:54:35.452 debug checking if connection is alive
! philips-tv.0 2018-11-24 17:54:35.451 debug initializing connection to 192.168.178.66
! philips-tv.0 2018-11-24 17:54:25.450 debug state with id philips-tv.0.info.apiVersion updated: ack=true; val=not found
! philips-tv.0 2018-11-24 17:54:25.449 debug redis pmessage io.philips-tv.0.* io.philips-tv.0.info.apiVersion {"val":"not found","ack":true,"ts":1543078465444,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057484988}
! philips-tv.0 2018-11-24 17:54:25.447 debug Could not initialize connection. Reason: No connection to host 192.168.178.66
! philips-tv.0 2018-11-24 17:54:25.443 debug connection is DEAD. Reason: [undefined] Error: ETIMEDOUT
! philips-tv.0 2018-11-24 17:54:25.442 debug no further attempts
! philips-tv.0 2018-11-24 17:54:25.442 debug error is not recoverable
! philips-tv.0 2018-11-24 17:54:25.441 debug attempt 1 failed with code undefined
! philips-tv.0 2018-11-24 17:54:20.428 debug attempt 1 of 3
! philips-tv.0 2018-11-24 17:54:20.427 debug checking if connection is alive
! philips-tv.0 2018-11-24 17:54:20.426 debug initializing connection to 192.168.178.66
! philips-tv.0 2018-11-24 17:54:10.425 debug state with id philips-tv.0.info.apiVersion updated: ack=true; val=not found
! philips-tv.0 2018-11-24 17:54:10.424 debug redis pmessage io.philips-tv.0.* io.philips-tv.0.info.apiVersion {"val":"not found","ack":true,"ts":1543078450420,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057484988}
! philips-tv.0 2018-11-24 17:54:10.422 debug Could not initialize connection. Reason: No connection to host 192.168.178.66
! philips-tv.0 2018-11-24 17:54:10.418 debug connection is DEAD. Reason: [undefined] Error: ETIMEDOUT
! philips-tv.0 2018-11-24 17:54:10.418 debug no further attempts
! philips-tv.0 2018-11-24 17:54:10.417 debug error is not recoverable
! philips-tv.0 2018-11-24 17:54:10.416 debug attempt 1 failed with code undefined
! philips-tv.0 2018-11-24 17:54:05.402 debug attempt 1 of 3
! philips-tv.0 2018-11-24 17:54:05.402 debug checking if connection is alive
! philips-tv.0 2018-11-24 17:54:05.401 debug initializing connection to 192.168.178.66
! philips-tv.0 2018-11-24 17:53:55.398 debug state with id philips-tv.0.info.apiVersion updated: ack=true; val=not found
! philips-tv.0 2018-11-24 17:53:55.398 debug redis pmessage io.philips-tv.0.* io.philips-tv.0.info.apiVersion {"val":"not found","ack":true,"ts":1543078435393,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057484988}
! philips-tv.0 2018-11-24 17:53:55.396 debug Could not initialize connection. Reason: No connection to host 192.168.178.66
! philips-tv.0 2018-11-24 17:53:55.391 debug connection is DEAD. Reason: [undefined] Error: ETIMEDOUT
! philips-tv.0 2018-11-24 17:53:55.390 debug no further attempts
! philips-tv.0 2018-11-24 17:53:55.390 debug error is not recoverable
! philips-tv.0 2018-11-24 17:53:55.389 debug attempt 1 failed with code undefined
! philips-tv.0 2018-11-24 17:53:50.376 debug attempt 1 of 3
! philips-tv.0 2018-11-24 17:53:50.375 debug checking if connection is alive
! philips-tv.0 2018-11-24 17:53:50.374 debug initializing connection to 192.168.178.66
! philips-tv.0 2018-11-24 17:53:40.372 debug state with id philips-tv.0.info.apiVersion updated: ack=true; val=not found
! philips-tv.0 2018-11-24 17:53:40.371 debug redis pmessage io.philips-tv.0.* io.philips-tv.0.info.apiVersion {"val":"not found","ack":true,"ts":1543078420367,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057484988}
! philips-tv.0 2018-11-24 17:53:40.369 debug Could not initialize connection. Reason: No connection to host 192.168.178.66
! philips-tv.0 2018-11-24 17:53:40.365 debug connection is DEAD. Reason: [undefined] Error: ETIMEDOUT
! philips-tv.0 2018-11-24 17:53:40.364 debug no further attempts
! philips-tv.0 2018-11-24 17:53:40.364 debug error is not recoverable
! philips-tv.0 2018-11-24 17:53:40.363 debug attempt 1 failed with code undefined
! philips-tv.0 2018-11-24 17:53:35.350 debug attempt 1 of 3
! philips-tv.0 2018-11-24 17:53:35.349 debug checking if connection is alive
! philips-tv.0 2018-11-24 17:53:35.348 debug initializing connection to 192.168.178.66
! philips-tv.0 2018-11-24 17:53:25.346 debug state with id philips-tv.0.info.apiVersion updated: ack=true; val=not found
! philips-tv.0 2018-11-24 17:53:25.345 debug redis pmessage io.philips-tv.0.* io.philips-tv.0.info.apiVersion {"val":"not found","ack":true,"ts":1543078405341,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057484988}
! philips-tv.0 2018-11-24 17:53:25.343 debug Could not initialize connection. Reason: No connection to host 192.168.178.66
! philips-tv.0 2018-11-24 17:53:25.339 debug connection is DEAD. Reason: [undefined] Error: ETIMEDOUT
! philips-tv.0 2018-11-24 17:53:25.339 debug no further attempts
! philips-tv.0 2018-11-24 17:53:25.338 debug error is not recoverable
! philips-tv.0 2018-11-24 17:53:25.337 debug attempt 1 failed with code undefined
! philips-tv.0 2018-11-24 17:53:20.329 debug attempt 1 of 3
! philips-tv.0 2018-11-24 17:53:20.328 debug checking if connection is alive
! philips-tv.0 2018-11-24 17:53:20.327 debug initializing connection to 192.168.178.66
! philips-tv.0 2018-11-24 17:53:10.325 debug state with id philips-tv.0.info.apiVersion updated: ack=true; val=not found
! philips-tv.0 2018-11-24 17:53:10.324 debug redis pmessage io.philips-tv.0.* io.philips-tv.0.info.apiVersion {"val":"not found","ack":true,"ts":1543078390320,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057484988}
! philips-tv.0 2018-11-24 17:53:10.322 debug Could not initialize connection. Reason: No connection to host 192.168.178.66
! philips-tv.0 2018-11-24 17:53:10.318 debug connection is DEAD. Reason: [undefined] Error: ETIMEDOUT
! philips-tv.0 2018-11-24 17:53:10.317 debug no further attempts
! philips-tv.0 2018-11-24 17:53:10.317 debug error is not recoverable
! philips-tv.0 2018-11-24 17:53:10.316 debug attempt 1 failed with code undefined
! philips-tv.0 2018-11-24 17:53:05.301 debug attempt 1 of 3
! philips-tv.0 2018-11-24 17:53:05.300 debug checking if connection is alive
! philips-tv.0 2018-11-24 17:53:05.299 debug initializing connection to 192.168.178.66
! philips-tv.0 2018-11-24 17:52:55.297 debug state with id philips-tv.0.info.apiVersion updated: ack=true; val=not found
! philips-tv.0 2018-11-24 17:52:55.296 debug redis pmessage io.philips-tv.0.* io.philips-tv.0.info.apiVersion {"val":"not found","ack":true,"ts":1543078375292,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057484988}
! philips-tv.0 2018-11-24 17:52:55.294 debug Could not initialize connection. Reason: No connection to host 192.168.178.66
! philips-tv.0 2018-11-24 17:52:55.290 debug connection is DEAD. Reason: [undefined] Error: ETIMEDOUT
! philips-tv.0 2018-11-24 17:52:55.289 debug no further attempts
! philips-tv.0 2018-11-24 17:52:55.289 debug error is not recoverable
! philips-tv.0 2018-11-24 17:52:55.288 debug attempt 1 failed with code undefined
! philips-tv.0 2018-11-24 17:52:50.275 debug attempt 1 of 3
! philips-tv.0 2018-11-24 17:52:50.275 debug checking if connection is alive
! philips-tv.0 2018-11-24 17:52:50.273 debug initializing connection to 192.168.178.66
! philips-tv.0 2018-11-24 17:52:40.269 debug state with id philips-tv.0.info.apiVersion updated: ack=true; val=not found
! philips-tv.0 2018-11-24 17:52:40.268 debug redis pmessage io.philips-tv.0.* io.philips-tv.0.info.apiVersion {"val":"not found","ack":true,"ts":1543078360259,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057484988}
! philips-tv.0 2018-11-24 17:52:40.263 debug Could not initialize connection. Reason: No connection to host 192.168.178.66
! philips-tv.0 2018-11-24 17:52:40.253 debug connection is DEAD. Reason: [undefined] Error: ETIMEDOUT
! philips-tv.0 2018-11-24 17:52:40.253 debug no further attempts
! philips-tv.0 2018-11-24 17:52:40.252 debug error is not recoverable
! philips-tv.0 2018-11-24 17:52:40.251 debug attempt 1 failed with code undefined
! philips-tv.0 2018-11-24 17:52:35.233 debug state with id philips-tv.0.info.connection updated: ack=true; val=false
! philips-tv.0 2018-11-24 17:52:35.228 debug redis pmessage io.philips-tv.0.* io.philips-tv.0.info.connection {"val":false,"ack":true,"ts":1543078355226,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057479953}
! philips-tv.0 2018-11-24 17:52:35.210 debug attempt 1 of 3
! philips-tv.0 2018-11-24 17:52:35.207 debug checking if connection is alive
! philips-tv.0 2018-11-24 17:52:35.200 debug initializing connection to 192.168.178.66
! philips-tv.0 2018-11-24 17:52:35.134 info starting. Version 0.3.0-alpha7 in /opt/iobroker/node_modules/iobroker.philips-tv, node: v8.11.1
! philips-tv.0 2018-11-24 17:52:35.052 info States connected to redis: 127.0.0.1:6379
! philips-tv.0 2018-11-24 17:52:35.045 debug statesDB connected
! philips-tv.0 2018-11-24 17:52:35.013 debug objectDB connected
! host.ioBroker-RasPi 2018-11-24 17:52:33.209 info instance system.adapter.philips-tv.0 started with pid 2308
! host.ioBroker-RasPi 2018-11-24 17:52:33.183 info object change system.adapter.philips-tv.0
! host.ioBroker-RasPi 2018-11-24 17:52:31.474 info instance system.adapter.philips-tv.0 terminated with code 0 (OK)
! philips-tv.0 2018-11-24 17:52:31.446 info terminating
! host.ioBroker-RasPi 2018-11-24 17:52:31.432 info stopInstance system.adapter.philips-tv.0 killing pid 2252
! host.ioBroker-RasPi 2018-11-24 17:52:31.431 info stopInstance system.adapter.philips-tv.0
! host.ioBroker-RasPi 2018-11-24 17:52:31.431 info "system.adapter.philips-tv.0" disabled
! host.ioBroker-RasPi 2018-11-24 17:52:31.430 info object change system.adapter.philips-tv.0
! philips-tv.0 2018-11-24 17:52:21.887 debug state with id philips-tv.0.info.apiVersion updated: ack=true; val=not found
! philips-tv.0 2018-11-24 17:52:21.886 debug redis pmessage io.philips-tv.0.* io.philips-tv.0.info.apiVersion {"val":"not found","ack":true,"ts":1543078341878,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057484988}
! philips-tv.0 2018-11-24 17:52:21.882 debug Could not initialize connection. Reason: No connection to host 192.168.178.66
! philips-tv.0 2018-11-24 17:52:21.873 debug connection is DEAD. Reason: [undefined] Error: ETIMEDOUT
! philips-tv.0 2018-11-24 17:52:21.872 debug no further attempts
! philips-tv.0 2018-11-24 17:52:21.872 debug error is not recoverable
! philips-tv.0 2018-11-24 17:52:21.871 debug attempt 1 failed with code undefined
! philips-tv.0 2018-11-24 17:52:16.852 debug state with id philips-tv.0.info.connection updated: ack=true; val=false
! philips-tv.0 2018-11-24 17:52:16.847 debug redis pmessage io.philips-tv.0.* io.philips-tv.0.info.connection {"val":false,"ack":true,"ts":1543078336845,"q":0,"from":"system.adapter.philips-tv.0","lc":1543057479953}
! philips-tv.0 2018-11-24 17:52:16.829 debug attempt 1 of 3
! philips-tv.0 2018-11-24 17:52:16.826 debug checking if connection is alive
! philips-tv.0 2018-11-24 17:52:16.819 debug initializing connection to 192.168.178.66
! philips-tv.0 2018-11-24 17:52:16.765 info starting. Version 0.3.0-alpha7 in /opt/iobroker/node_modules/iobroker.philips-tv, node: v8.11.1
! philips-tv.0 2018-11-24 17:52:16.699 info States connected to redis: 127.0.0.1:6379
! philips-tv.0 2018-11-24 17:52:16.692 debug statesDB connected
! philips-tv.0 2018-11-24 17:52:16.648 debug objectDB connected
! host.ioBroker-RasPi 2018-11-24 17:52:14.853 info instance system.adapter.philips-tv.0 started with pid 2252
! host.ioBroker-RasPi 2018-11-24 17:52:12.368 info instance system.adapter.philips-tv.0 terminated with code 0 (OK)
! philips-tv.0 2018-11-24 17:52:12.339 info terminating
! host.ioBroker-RasPi 2018-11-24 17:52:12.323 info stopInstance system.adapter.philips-tv.0 killing pid 2197
! host.ioBroker-RasPi 2018-11-24 17:52:12.323 info stopInstance system.adapter.philips-tv.0
! host.ioBroker-RasPi 2018-11-24 17:52:12.322 info object change system.adapter.philips-tv.0
! philips-tv.0 2018-11-24 17:50:49.290 info starting. Version 0.3.0-alpha7 in /opt/iobroker/node_modules/iobroker.philips-tv, node: v8.11.1
! philips-tv.0 2018-11-24 17:50:49.202 info States connected to redis: 127.0.0.1:6379
! host.ioBroker-RasPi 2018-11-24 17:50:47.412 info instance system.adapter.philips-tv.0 started with pid 2197
! host.ioBroker-RasPi 2018-11-24 17:50:44.923 info instance system.adapter.philips-tv.0 terminated with code 0 (OK)
! philips-tv.0 2018-11-24 17:50:44.896 info terminating
! host.ioBroker-RasPi 2018-11-24 17:50:44.884 info stopInstance system.adapter.philips-tv.0 killing pid 1274
! host.ioBroker-RasPi 2018-11-24 17:50:44.884 info stopInstance system.adapter.philips-tv.0
! host.ioBroker-RasPi 2018-11-24 17:50:44.883 info object change system.adapter.philips-tv.0
! /spoiler] -
` > No connection to host 192.168.178.66
philips-tv.0 2018-11-24 17:57:10.705 debug connection is DEAD. Reason: [undefined] Error: ETIMEDOUT `
Stimmt die IP-Adresse in den Einstellungen? -
Jup, ich kann mich ja auch mit der ip im Browser einwählen
-
Ich glaube ich weiß warum, irgendwie kann ich den TV nicht vom Raspberry PI (Terminal) anpingen aber von einem anderen Gerät schon. Komisch ist nur, dass ich vom Pi zb mein Handy anpingen kann.
Meine Sonoffs erreiche ich ja auch mit dem PI.
Mmmh irgendwo ist da was faul.
Edit:
Es war doch simpler als gedacht, ein sudo apt-get update sowie ein sudo apt-get upgrade, haben das Problem behoben.
Frage
Wie kann ich jetzt das Ambilight steuern?
Wie ist das mit der Lautstärke, wenn ich den TV mit Lautsprecher und Easy-Connect verbunden habe?
Vielen Dank für den tollen Adapter
-
Hallo Leute,
ich habe ein anderes Problem mit meinem Philips TV (denke, passt aber ebenfalls in den Thread).
Der Fernseher Philips 55OLED803) ist permanent vom Pi anpingbar. Auch wenn ich den Fernseher <u>ausgeschaltet</u> habe.
Auch über den PING-Adapter und TR-064-Adapter wird "true" gemeldet.
Wie kann man das ändern? Weiss jemand Rat?
Danke und Gruß,
Andi
-
Hilfe Al :oops:
Ich habe einen Ambilight mit V6.
Nach ewigen hin und her habe ich es geschafft mit dem Python Skript den Fernseher zu pairen und Passwort und User rauszufinden.
Dein Skript habe ich auch durchlaufen lassen (kam kein Fehler im Log).
Adapter bleibt trotzdem gelb. Komischerweise zeigt er bei den Objekten das an
[urlBildschirmfoto 2018-12-23 um 01.53.26.png]
Und, erfreulicherweise, ist auch bei den Objekten im Adapter was drinnen. Aber wenn ich z. B. Mute anwähle kommt im Log auf Silly:
` > philips-tv.0 2018-12-23 01:56:27.874 debug system.adapter.admin.0: logging true
philips-tv.0 2018-12-23 01:56:27.874 silly inMem message *.logging system.adapter.admin.0.logging
philips-tv.0 2018-12-23 01:52:55.073 debug system.adapter.admin.0: logging false
philips-tv.0 2018-12-23 01:52:55.073 silly inMem message *.logging system.adapter.admin.0.logging val=false, ack=true, ts=1545526375068, q=0, from=system.adapter.admin.0, lc=1545526375068
philips-tv.0 2018-12-23 01:50:03.187 error Error handling state change philips-tv.0.pressKey => Mute: 404 - "\n\n <title>Status page</title>\n\n\n
philips-tv.0 2018-12-23 01:50:03.162 debug state with id philips-tv.0.pressKey updated: ack=false; val=Mute
philips-tv.0 2018-12-23 01:50:03.154 silly inMem message philips-tv.0.* philips-tv.0.pressKey val=Mute, ack=false, ts=1545526203148, q=0, from=system.adapter.admin.0, lc=1545526203148
philips-tv.0 2018-12-23 01:48:03.099 info starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.philips-tv, node: v8.12.0 `
Bzw. könnte mir jemand sagen ob man mit dem Adapter direkt Ambilight (letzter Modus) und Ambi und Hue ein- und ausschalten kann. Bräuchte den Philips Adapter nur deswegen, weil das mit dem Harmony Adapter relativ unzuverlässig funktioniert.
2548_bildschirmfoto_2018-12-23_um_01.53.26.png -
Der Fernseher Philips 55OLED803) ist permanent vom Pi anpingbar. Auch wenn ich den Fernseher <u>ausgeschaltet</u> habe. `
Ist bei mir teilweise auch so… Ich glaube der Fernseher ist nicht vollständig ausgeschaltet auch wenn er "aus" ist.
Gesendet von unterwegs
-
Hallöchen zusammen,
danke erstmal für die Mühen
Hab eben den Adapter aus GitHub installiert und direkt die IP-Adresse eingetragen (ist vom Host pingbar) und leider bleibt der Adapter auf gelb.
Der Aufruf des TVs liefert folgende Infos (Api 6.1)
! {"notifyChange":"http","menulanguage":"German","name":"55POS9002/12","country":"Germany","serialnumber_encrypted":"u9fUvUq7i+VpA8InZyY9Z+iunRUC+dy4A+xpPBr8aC4=\n","model_encrypted":"wI6hSPXu5k+R/Rwf9OgLAzWtermaBGPPjoSExnuADtU=\n","deviceid_encrypted":"2he9GZhRX0c47vnshx6TnUAadeahpd4qrO02wTrc9w8=\n","nettvversion":"8.0.0","epgsource":"one","api_version":{"Major":6,"Minor":1,"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","pvr"],"tvsearch":"intent","pairing_type":"digest_auth_pairing","secured_transport":"true","companion_screen":"true"}}}
Das Log zeigt eigentlich gar nichts an:
! philips-tv.0 2018-12-31 12:20:45.989 info starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.philips-tv, node: v8.15.0
! philips-tv.0 2018-12-31 12:18:45.483 info starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.philips-tv, node: v8.15.0
! philips-tv.0 2018-12-31 12:18:38.211 info starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.philips-tv, node: v8.15.0
! philips-tv.0 2018-12-31 12:12:30.061 info starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.philips-tv, node: v8.15.0
! philips-tv.0 2018-12-31 12:11:31.730 info starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.philips-tv, node: v8.15.0Kann mir jemand weiterhelfen und sagen wie ich die Verbindung hergestellt bekomme?
Viele Grüße und Danke,
Bastian
-
Niemand da der mir helfen kann? :?
-
Hallo @AlCalzone ,
darf ich fragen ob die Entwicklung des Adapters noch mal weiter geht oder wird es an der Stelle keine Neuerungen mehr geben?
Ich würde ihn sehr gerne verwenden, aber bekomme ihn leider nicht zum laufen.Würde mich über eine Rückmeldung sehr freuen.
Viele Dank und Grüße
Bastian -
@Buddinski88 Ich habe derzeit nicht viel Zeit und andere Prioritäten. Habe ihn nicht vergessen, aber komme kurzfristig nicht zur Weiterentwicklung.
-
@AlCalzone
Ist ok, bin aber auch noch interessiert........... -
Falls es euch zwischenzeitlich weiterhilft bis der Adapter fertig ist... Mit dem HAM Adapter klappt die Ansteuerung inzwischen gut.
https://forum.iobroker.net/topic/20585/gelöst-installationsfehler-ham-adapter-philips-tv-plug-in/11
Viel ansteuern kann man nicht. Aber Ambilightstatus abfragen und an und ausschalten geht prima.
Auf Linuxebene könnte man nach dem pairing auch noch mit CURL Befehle arbeiten und die Kommandos von der API direkt ansprechen. Kenne mich damit leider selber nicht aus, habe nur ein paar von einem Arbeitskollegen bekommen. Tastendrucke und Ambi und Hue per CURL ansteuern bekomme ich aber leider noch immer nicht zum Laufen. Ist hier jemand der sich zufällig damit auskennt?
Dann könnte man die Wartezeit bis Al wieder mehr Zeit hat besser ûberbrücken Aber nochmal vielen Dank Al, dass du den Adapter noch auf dem Schirm hast und für die bereits geleistete Arbeit.
-
Hi zusammen,
eine Erfolgsmeldung:
Ich habe einen Philips 65PUS7303 (2018er Modell) - API-Version 6.1 lt Aufruf von http://x.x.x.x:1925/systemIch bin wie folgt vorgegangen:
- https://github.com/AlCalzone/ioBroker.philips-tv/tarball/api-v5+v6 über Katze installiert und dann manuell hochgeladen
- User/Passwort generiert lt. Vorgehensweise von https://github.com/nstrelow/ha_philips_2016
- User/Passwort per Script hinzugefügt: https://forum.iobroker.net/post/128997 (AlCalzone 4. Feb. 2018, 12:54)
Adapter grün und läuft!
Über Datenpunkt philips-tv.0.pressKey kann ich schon mal Fernseher in Standby versetzen und wieder aufwecken, weiteres werde ich testen.
Vielen Dank an @AlCalzone für die bisherige Arbeit!//////////////
Edit:
Hier noch ein wertvoller Link: https://community.openhab.org/t/philips-tv-2016-binding/64579/61
Mit den curl-Befehlen kann ich u.a. erfolgreich das Ambilight ausschalten und einschalten (= # setting Ambilight to FOLLOW_VIDEO). -
Top, das klingt gut. Ich hoffe ich komme demnächst mal dazu das fertig zu stellen. Habe mir deinen Beitrag als Lesezeichen gemerkt.
-
Selber habe ich weder den Adapter zum laufen gebracht (steht auf gelb) noch das Python Script
um User und Passwort vom meinem PUS7101 auszulesen.
Problem ist schon eingegrenzt (Visual Studio / C++)Aber in der Zwischenzeit habe ich etwas interessantes entdeckt...
Da stellt jemand eine Python Script zur Verfügung mit MQTT support
Da es aber auf meiner Windows-Kiste schon mit Python Probleme bei den Requirements gibt,
kann ich die Funktion nzw. das Script nicht testen.Quelle: https://github.com/eslavnov/pylips
Ein Auszug...
"Pylips is a Python tool to control Philips TVs (2015+) through their reverse-engineered API.Supports both Android and non-Android TVs
80 built-in commands + support for custom "GET" and "POST" requests to the API
All commands work on TVs with API version 6, most of them also work for API version 5
Full control of Ambilight including color, brightness, mode and 'Ambilight + Hue'
Allows sending TV status updates and receiving commands over MQTT
The current version of the API does not allow switching input sources anymore (?), use this tool instead (Android TVs only)." -
Danke @Ratze!
Interessant hierbei -- sicherlich auch für @AlCalzone -- ist auch die inoffizielle API-Referenz des Programmierers:
https://github.com/eslavnov/Pylips/wikiTeste ich gerade mit exec und curl und läuft sehr gut, hier ein JavaScript-Beispiel:
[ EDIT: überarbeitetes Script siehe unten ]
-
Hier noch ein Update meines Test-Scripts. Es legt einen Datenpunkt unter "javascript.0.PhilipsTV.MyScript" an, womit man den Philips-TV steuern kann. Eingebaut ist auch Einschalten von Netflix, Kodi und YouTube. Sicherlich einfach in den Adapter integrierbar
Achtung:
Update: aktuelles Script siehe auf Github.
-
@Mic
Mit dem Skript habe ich auch schon experimentiert. Nur leider waren meine Linux Kenntnisse zu schwach um es zum laufen zu bekommen. Ich löse das aus und einschalten vom Ambilight jetzt per CURL Befehl. Kennst du dich zufällig damit auch aus und weißt wie der richtige Befehl geht um Ambi und Hue aus und einzuschalten?Grundlage war die Seite
https://gist.github.com/marcelrv/ee9a7cf97c227d069e4ee88d26691019
-
@Stormbringer
Das macht mein Script (siehe oben), dort ist curl integriert, das per JavaScript über ioBroker ausgeführt wird. Wo hast Du da denn Fragen?
