Coder Social home page Coder Social logo

o-lukas / homebridge-smartthings-tv Goto Github PK

View Code? Open in Web Editor NEW
23.0 4.0 1.0 1.83 MB

This is a plugin for Homebridge. It offers some basic functions to control Samsung TVs using the SmartThings API.

Home Page: https://www.npmjs.com/package/@o-lukas/homebridge-smartthings-tv

License: MIT License

TypeScript 98.63% Dockerfile 1.37%
homebridge homebridge-plugin samsung samsung-tv smartthings remote television tv tizen

homebridge-smartthings-tv's Introduction

Homebridge SmartThings TV

verified-by-homebridge semantic-release NPM Version NPM Node Version NPM Total Downloads GitHub issues Build and Lint

This is a plugin for Homebridge. It offers some basic functions to control Samsung TVs using the SmartThings API.

Configuration

The easiest way to configure the plugin is to use Homebridge Config UI X which should contain a description for every needed property. The only property needed to make the plugin work is the SmartThings API token. The other properties enable some additional functions but are not mandatory for the plugin to work.

Configuration example

The following snippet shows the most simple configuration you can use for the plugin:

{
    "bridge": {
    },
    "accessories": [],
    "platforms": [
        {
            "name": "SmartThings TV",
            "token": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
            "platform": "smartthings-tv"
        }
    ]
}

The following snippets shows all available properties you can use for the plugin:

{
    "bridge": {
    },
    "accessories": [],
    "platforms": [
        {
            "name": "SmartThings TV",
            "token": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
            "capabilityLogging": true,
            "cyclicCallsLogging": true,
            "registerApplications": true,
            "registerPictureModes": true,
            "registerSoundModes": true,
            "registerVolumeSlider": true,
            "pollInterval": 5000,
            "deviceBlacklist": [
                "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
                "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
            ],
            "deviceMappings": [
                {
                    "deviceId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
                    "wol": true,
                    "macAddress": "xx:xx:xx:xx:xx:xx",
                    "ping": true,
                    "ipAddress": "xx:xx:xx:xx:xx:xx",
                    "inputSources": [
                      {
                        "name": "xxxx",
                        "id": "xxxx"
                      }
                    ],
                    "applications": [
                        {
                            "name": "xxxx",
                            "ids": [
                                "xxxx",
                                "xxxx"
                            ]
                        }
                    ]
                },
                {
                    "deviceId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
                    "wol": true,
                    "macAddress": "xx:xx:xx:xx:xx:xx",
                    "ping": false
                },
                {
                    "deviceId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
                    "wol": false,
                    "ping": true,
                    "ipAddress": "xx:xx:xx:xx:xx:xx"
                }
            ],
            "platform": "smartthings-tv"
        }
    ]
}

Available configuration properties

token

The SmartThings API token is needed to authenticate the requests sent to the SmartThings API. To generate a token open SmartThings website and generate a new one (make sure at least devices is selected).

capabilityLogging

The SmartThings API returns the list of supported actions of a device as capabilities. For implementing new features it is neccessary to know the scheme the capability uses. Enable this property to log all capabilities of supported SmartThings devices.

cyclicCallsLogging

Enable debug logging for cyclic calls (e.g. polling).

registerApplications

To use installed application as input sources, a predefined list of applications will be used. This list will be checked for availability at the TV(s) and eventually be registered as input sources. Make sure to have the TV(s) turned on when starting your instance as this functionality requires your TV(s) be turned on to determine whether an application is installed or not. On startup the applications will be opened to determine if they are available. Do not use your TV until the input source is being changed back to the first one (usually Live TV).

registerPictureModes

Registers all available picture modes as separate switches that can be toggled to enable/disable a picture mode. Uses the names as exposed from the SmartThings API.

registerSoundModes

Registers all available sound modes as separate switches that can be toggled to enable/disable a sound mode. Uses the names as exposed from the SmartThings API.

registerVolumeSlider

Registers a separate volume slider accessorry that will be exposed as a light bulb accessory (because there is currently no option to change a speaker volume directly using Home).

pollInterval

Some characteristics are not updated automatically (e.g. power state). To enable polling these characteristics automatically set this value to the desired polling interval in milliseconds. Leave empty to disable this functionality.

deviceBlacklist

Devices not to be registered.

deviceMappings

Use the device mappings when e.g. turning on the accessory does not work as expected. When a device mapping is available the wake-on-lan functionality is used to turn on the device instead of the SmartThings API. To make use of the functionality you must enter the mapping using the SmartThings device ID and the mac address of the device. If status does not show up properly you can use the ping functionality to determine the device status. To make use of it you must enter the SmartThings device ID and the ip address of the device.

deviceId

The SmartThings device id. Check the log or go to https://account.smartthings.com/ and get the device id.

wol

Enables usage of wake-on-lan functionality to turn the device on. Use only if using the SmartThings API does not work for your device.

macAddress

The mac address of the device to turn device on using wake-on-lan functionality.

ping

Enables usage of ping functionality to determine if device is turned on. Use only if using the SmartThings API does not work for your device.

ipAddress

The IP address of the device (assign a static IP address to make sure it does not change) to determine the status using ping.

inputSources

Overrides the device's default input sources map to add custom input sources. Check the log for information about the default input sources.

name

The input source's name.

id

The input source's id.

applications

Overrides the default application mapping list to add custom applications. See registerApplications for more details about application registration.

name

The application's name.

ids

The application's possible ids. Since some applications have different ids for different versions of TVs you can provide a list here so the plugin will try every id and use the one that's working.

Common issues

TV does not show in HomeKit

After starting you have to add the TV manually to HomeKit because they are published as external accessory to get over the limit of only one TV per bridge.

TV does not turn on

The command to turn the TV on using the SmartThings API does not work for some TVs. To solve this problem you can use the built-in wake-on-lan functionality. To activate this functionality add a device mapping containing the device id and the mac address of your TV.

{
    "bridge": {
    },
    "accessories": [],
    "platforms": [
        {
            "name": "SmartThings TV",
            "token": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
            "deviceMappings": [
                {
                    "deviceId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
                    "macAddress": "xx:xx:xx:xx:xx:xx"
                }
            ],
            "platform": "smartthings-tv"
        }
    ]
}

TV state does not match actual state

Some TVs report a false active state using the SmartThings API. To get the actual state of the television you can use the build-in ping functionality. To activate this functionality add a device mapping containing the device id and the IP address of your TV.

{
    "bridge": {
    },
    "accessories": [],
    "platforms": [
        {
            "name": "SmartThings TV",
            "token": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
            "deviceMappings": [
                {
                    "deviceId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
                    "ipAddress": "xx:xx:xx:xx:xx:xx"
                }
            ],
            "platform": "smartthings-tv"
        }
    ]
}

Picture/sound mode switches do not match TV picture mode settings

Some TVs always report the same picture & sound mode. This will cause the exposed switches to not match the actual picture/sound mode state. I have not found a proper solution for this problem yet. But toggling the buttons will still work.

Error invalid device state

Sometimes the SmartThings API seems to loose the contact to the device and does not update it's state so every request will end up with an error message like invalid device state. To fix this try to remove the device from your SmartThings account and add it again. This seems to fix the problem.

DisplayPort input sources do not show up

For some TVs display port sources do not show up. When having the same problem you might try to use inputSources. Id might be something like Display Port but you will have to experiment a bit trying different ids until you find the the right one.


Since this is my first plugin it may contain some problems. Feel free to create an issue or pull request and I will try to help and fix the problems.

But since this plugin is developed in my spare time don't expect a quick fix.

homebridge-smartthings-tv's People

Contributors

dependabot[bot] avatar o-lukas avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

homebridge-smartthings-tv's Issues

Ignore Devices

Before opening the issue, have you...?

  • Searched for existing issues
  • Looked through common issues
  • Updated plugin to the latest version (if applicable)

Describe Your Problem

I have a few different homebridge servers setup with many devices. When I sync my devices, it pulls in all my TV's from the other locations since I am using the same ST login with different locations setup. Is there a way I can hide devices or ignore locations from each instance?

Logs

No response

If applicable, add screenshots to help explain your problem.

No response

Environment Information

- Plugin Version:
- Homebridge Version: <!-- homebridge -V -->
- Node.js version: <!-- node -v -->
- NPM version: <!-- npm -v -->
- Operating System: <!-- Raspbian / Ubuntu / Debian / Windows / macOS / Docker / hb-service -->

Detecting DisplayPort sources

Before opening the issue, have you...?

  • Searched for existing issues
  • Looked through common issues
  • Updated plugin to the latest version (if applicable)

Describe Your Problem

I have a Samsung Smart Monitor with two HDMIs and one DisplayPort input. Only the HDMI inputs are detected.

Logs

No response

If applicable, add screenshots to help explain your problem.

No response

Environment Information

- Plugin Version: v1.8.2
- Homebridge Version: v1.6.1
- Node.js version: v18.15.0
- Operating System: Docker

Multiple Locations in Smartthings does not show up

Before opening the issue, have you...?

  • Searched for existing issues
  • Looked through common issues
  • Updated plugin to the latest version (if applicable)

Describe the bug

I have an account in Smartthings that has two locations. I cannot control or see my TV in the second location. I see the logs are showing the device ID for the TV in my 1st location, but my Home Kit is for that second location. Is there any way to pull the API from a different location to pull those devices?

To Reproduce

  1. Create a second account and add devices to that account.
  2. Generate API token
  3. Paste token in Homebridge plugin
  4. Restart plugin
  5. View logs of device IDs pulled and registered
  6. Compare to device IDs in Samsung account
  7. Verified that the first location are the only devices pulled.

Expected behavior

Would be nice to pull ALL devices or allow device mappings to pull in the second location

Logs

[1/15/2024, 6:53:49 PM] [@o-lukas/homebridge-smartthings-tv] Launched child bridge with PID 2045
[1/15/2024, 6:53:49 PM] Registering platform '@o-lukas/homebridge-smartthings-tv.smartthings-tv'
[1/15/2024, 6:53:49 PM] [@o-lukas/homebridge-smartthings-tv] Loaded @o-lukas/homebridge-smartthings-tv v1.10.3 child bridge successfully
[1/15/2024, 6:53:49 PM] Homebridge v1.7.0 (HAP v0.11.1) (@o-lukas/homebridge-smartthings-tv) is running on port 54095.
[1/15/2024, 6:53:49 PM] [@o-lukas/homebridge-smartthings-tv] Adding new accessory: Samsung Q6DAA 65 TV (01a48093-2bb8-a613-e45c-75e8d84afe1c)
[1/15/2024, 6:53:49 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capabilities for component main
[1/15/2024, 6:53:49 PM] Samsung Q6DAA 65 TV E98D is running on port 34791.
[1/15/2024, 6:53:49 PM] Please add [Samsung Q6DAA 65 TV E98D] manually in Home app. Setup Code: 464-46-219
[1/15/2024, 6:53:50 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: Switch
[1/15/2024, 6:53:51 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: Audio Volume
[1/15/2024, 6:53:51 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: Audio Mute
[1/15/2024, 6:53:54 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: launchApp
[1/15/2024, 6:53:54 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Capability launchApp might not work as expected because it's status is: proposed
[1/15/2024, 6:53:55 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering applications will probably not work because TV is not turned on
[1/15/2024, 6:54:06 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: Media Input Source
[1/15/2024, 6:54:06 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Capability Media Input Source might not work as expected because it's status is: proposed
[1/15/2024, 6:54:07 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering input source: TV (dtv)
[1/15/2024, 6:54:07 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering input source: Receiver (HDMI2)
[1/15/2024, 6:54:09 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Resetting active identifier to TV because application registration needed to open all applications
[1/15/2024, 6:54:10 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Error when executing setInputSource of capability samsungvd.mediaInputSource: Request failed with status code 409: {"requestId":"8060089848482951124","error":{"code":"ConflictError","message":"invalid device state","details":[]}}
[1/15/2024, 6:54:10 PM] [@o-lukas/homebridge-smartthings-tv] Error when getting devices: HAP Status Error: -70402
[1/15/2024, 6:57:50 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Error when executing on of capability switch: Request failed with status code 409: {"requestId":"7653694303686337822","error":{"code":"ConflictError","message":"invalid device state","details":[]}}
[1/15/2024, 6:57:57 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Error when executing on of capability switch: Request failed with status code 409: {"requestId":"8536605341898282852","error":{"code":"ConflictError","message":"invalid device state","details":[]}}
[1/15/2024, 6:58:53 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Error when executing on of capability switch: Request failed with status code 409: {"requestId":"7870734013200644251","error":{"code":"ConflictError","message":"invalid device state","details":[]}}
[1/15/2024, 6:58:59 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Error when executing on of capability switch: Request failed with status code 409: {"requestId":"5339899254097692234","error":{"code":"ConflictError","message":"invalid device state","details":[]}}
[1/15/2024, 6:59:31 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Error when executing on of capability switch: Request failed with status code 409: {"requestId":"1069822059704923331","error":{"code":"ConflictError","message":"invalid device state","details":[]}}
[1/15/2024, 6:59:35 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Error when executing on of capability switch: Request failed with status code 409: {"requestId":"6697696948878896172","error":{"code":"ConflictError","message":"invalid device state","details":[]}}
[1/15/2024, 7:02:36 PM] [@o-lukas/homebridge-smartthings-tv] Restarting child bridge...
[1/15/2024, 7:02:36 PM] Got SIGTERM, shutting down child bridge process...
[1/15/2024, 7:02:41 PM] [@o-lukas/homebridge-smartthings-tv] Child bridge process ended
[1/15/2024, 7:02:41 PM] [@o-lukas/homebridge-smartthings-tv] Process Ended. Code: 143, Signal: null
[1/15/2024, 7:02:48 PM] [@o-lukas/homebridge-smartthings-tv] Restarting Process...
[1/15/2024, 7:02:49 PM] [@o-lukas/homebridge-smartthings-tv] Launched child bridge with PID 2295
[1/15/2024, 7:02:49 PM] Registering platform '@o-lukas/homebridge-smartthings-tv.smartthings-tv'
[1/15/2024, 7:02:49 PM] [@o-lukas/homebridge-smartthings-tv] Loaded @o-lukas/homebridge-smartthings-tv v1.10.3 child bridge successfully
[1/15/2024, 7:02:49 PM] Loaded 0 cached accessories from cachedAccessories.0ECFC154A937.
[1/15/2024, 7:02:49 PM] Homebridge v1.7.0 (HAP v0.11.1) (@o-lukas/homebridge-smartthings-tv) is running on port 54095.
[1/15/2024, 7:02:49 PM] [@o-lukas/homebridge-smartthings-tv] Adding new accessory: Samsung Q6DAA 65 TV (01a48093-2bb8-a613-e45c-75e8d84afe1c)
[1/15/2024, 7:02:49 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capabilities for component main
[1/15/2024, 7:02:49 PM] Samsung Q6DAA 65 TV E98D is running on port 40817.
[1/15/2024, 7:02:49 PM] Please add [Samsung Q6DAA 65 TV E98D] manually in Home app. Setup Code: 464-46-219
[1/15/2024, 7:02:50 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: Switch
[1/15/2024, 7:02:51 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: Audio Volume
[1/15/2024, 7:02:51 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: Audio Mute
[1/15/2024, 7:02:54 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: launchApp
[1/15/2024, 7:02:54 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Capability launchApp might not work as expected because it's status is: proposed
[1/15/2024, 7:02:55 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering applications will probably not work because TV is not turned on
[1/15/2024, 7:03:03 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Error when executing on of capability switch: Request failed with status code 409: {"requestId":"1610752041975862730","error":{"code":"ConflictError","message":"invalid device state","details":[]}}
[1/15/2024, 7:03:04 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering input source: EduPedia (3201608010385)
[1/15/2024, 7:03:04 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering input source: ARTE (3202011022316)
[1/15/2024, 7:03:05 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering input source: Twitch (3202203026841)
[1/15/2024, 7:03:07 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: Media Input Source
[1/15/2024, 7:03:07 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Capability Media Input Source might not work as expected because it's status is: proposed
[1/15/2024, 7:03:08 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering input source: TV (dtv)
[1/15/2024, 7:03:08 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering input source: Receiver (HDMI2)
[1/15/2024, 7:03:10 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Resetting active identifier to EduPedia because application registration needed to open all applications
[1/15/2024, 7:03:10 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Error when executing launchApp of capability custom.launchapp: Request failed with status code 409: {"requestId":"2090150110691450694","error":{"code":"ConflictError","message":"invalid device state","details":[]}}
[1/15/2024, 7:03:10 PM] [@o-lukas/homebridge-smartthings-tv] Error when getting devices: HAP Status Error: -70402
[1/15/2024, 7:03:11 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Error when executing on of capability switch: Request failed with status code 409: {"requestId":"3478759714951545386","error":{"code":"ConflictError","message":"invalid device state","details":[]}}
[1/15/2024, 7:03:13 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Error when executing on of capability switch: Request failed with status code 409: {"requestId":"2104526903555197618","error":{"code":"ConflictError","message":"invalid device state","details":[]}}
[1/15/2024, 7:07:00 PM] [@o-lukas/homebridge-smartthings-tv] Restarting child bridge...
[1/15/2024, 7:07:00 PM] Got SIGTERM, shutting down child bridge process...
[1/15/2024, 7:07:05 PM] [@o-lukas/homebridge-smartthings-tv] Child bridge process ended
[1/15/2024, 7:07:05 PM] [@o-lukas/homebridge-smartthings-tv] Process Ended. Code: 143, Signal: null
[1/15/2024, 7:07:12 PM] [@o-lukas/homebridge-smartthings-tv] Restarting Process...
[1/15/2024, 7:07:12 PM] [@o-lukas/homebridge-smartthings-tv] Launched child bridge with PID 2387
[1/15/2024, 7:07:12 PM] Registering platform '@o-lukas/homebridge-smartthings-tv.smartthings-tv'
[1/15/2024, 7:07:12 PM] [@o-lukas/homebridge-smartthings-tv] Loaded @o-lukas/homebridge-smartthings-tv v1.10.3 child bridge successfully
[1/15/2024, 7:07:12 PM] Loaded 0 cached accessories from cachedAccessories.0ECFC154A937.
[1/15/2024, 7:07:12 PM] Homebridge v1.7.0 (HAP v0.11.1) (@o-lukas/homebridge-smartthings-tv) is running on port 54095.
[1/15/2024, 7:07:13 PM] [@o-lukas/homebridge-smartthings-tv] Adding new accessory: Samsung Q6DAA 65 TV (01a48093-2bb8-a613-e45c-75e8d84afe1c)
[1/15/2024, 7:07:13 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capabilities for component main
[1/15/2024, 7:07:13 PM] Samsung Q6DAA 65 TV E98D is running on port 37373.
[1/15/2024, 7:07:13 PM] Please add [Samsung Q6DAA 65 TV E98D] manually in Home app. Setup Code: 464-46-219
[1/15/2024, 7:07:13 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: Switch
[1/15/2024, 7:07:14 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: Audio Volume
[1/15/2024, 7:07:14 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: Audio Mute
[1/15/2024, 7:07:18 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: launchApp
[1/15/2024, 7:07:18 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Capability launchApp might not work as expected because it's status is: proposed
[1/15/2024, 7:07:18 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering applications will probably not work because TV is not turned on
[1/15/2024, 7:07:30 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: Media Input Source
[1/15/2024, 7:07:30 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Capability Media Input Source might not work as expected because it's status is: proposed
[1/15/2024, 7:07:30 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering input source: TV (dtv)
[1/15/2024, 7:07:30 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering input source: Receiver (HDMI2)
[1/15/2024, 7:07:32 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Resetting active identifier to TV because application registration needed to open all applications
[1/15/2024, 7:07:33 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Error when executing setInputSource of capability samsungvd.mediaInputSource: Request failed with status code 409: {"requestId":"8256728498606309451","error":{"code":"ConflictError","message":"invalid device state","details":[]}}
[1/15/2024, 7:07:33 PM] [@o-lukas/homebridge-smartthings-tv] Error when getting devices: HAP Status Error: -70402
[1/15/2024, 7:11:39 PM] [@o-lukas/homebridge-smartthings-tv] Restarting child bridge...
[1/15/2024, 7:11:39 PM] Got SIGTERM, shutting down child bridge process...
[1/15/2024, 7:11:44 PM] [@o-lukas/homebridge-smartthings-tv] Child bridge process ended
[1/15/2024, 7:11:44 PM] [@o-lukas/homebridge-smartthings-tv] Process Ended. Code: 143, Signal: null
[1/15/2024, 7:11:51 PM] [@o-lukas/homebridge-smartthings-tv] Restarting Process...
[1/15/2024, 7:11:51 PM] [@o-lukas/homebridge-smartthings-tv] Launched child bridge with PID 2482
[1/15/2024, 7:11:51 PM] Registering platform '@o-lukas/homebridge-smartthings-tv.smartthings-tv'
[1/15/2024, 7:11:51 PM] [@o-lukas/homebridge-smartthings-tv] Loaded @o-lukas/homebridge-smartthings-tv v1.10.3 child bridge successfully
[1/15/2024, 7:11:51 PM] Loaded 0 cached accessories from cachedAccessories.0ECFC154A937.
[1/15/2024, 7:11:51 PM] Homebridge v1.7.0 (HAP v0.11.1) (@o-lukas/homebridge-smartthings-tv) is running on port 54095.
[1/15/2024, 7:11:52 PM] [@o-lukas/homebridge-smartthings-tv] Adding new accessory: Samsung Q6DAA 65 TV (01a48093-2bb8-a613-e45c-75e8d84afe1c)
[1/15/2024, 7:11:52 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capabilities for component main
[1/15/2024, 7:11:52 PM] Samsung Q6DAA 65 TV E98D is running on port 43583.
[1/15/2024, 7:11:52 PM] Please add [Samsung Q6DAA 65 TV E98D] manually in Home app. Setup Code: 464-46-219
[1/15/2024, 7:11:52 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: Switch
[1/15/2024, 7:11:53 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: Audio Volume
[1/15/2024, 7:11:53 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: Audio Mute
[1/15/2024, 7:11:56 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: launchApp
[1/15/2024, 7:11:56 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Capability launchApp might not work as expected because it's status is: proposed
[1/15/2024, 7:11:57 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering applications will probably not work because TV is not turned on
[1/15/2024, 7:12:09 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: Media Input Source
[1/15/2024, 7:12:09 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Capability Media Input Source might not work as expected because it's status is: proposed
[1/15/2024, 7:12:09 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering input source: TV (dtv)
[1/15/2024, 7:12:09 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering input source: Receiver (HDMI2)
[1/15/2024, 7:12:11 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Resetting active identifier to TV because application registration needed to open all applications
[1/15/2024, 7:12:12 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Error when executing setInputSource of capability samsungvd.mediaInputSource: Request failed with status code 409: {"requestId":"4665717268922989551","error":{"code":"ConflictError","message":"invalid device state","details":[]}}
[1/15/2024, 7:12:12 PM] [@o-lukas/homebridge-smartthings-tv] Error when getting devices: HAP Status Error: -70402
[1/15/2024, 7:16:50 PM] [@o-lukas/homebridge-smartthings-tv] Restarting child bridge...
[1/15/2024, 7:16:50 PM] Got SIGTERM, shutting down child bridge process...
[1/15/2024, 7:16:55 PM] [@o-lukas/homebridge-smartthings-tv] Child bridge process ended
[1/15/2024, 7:16:55 PM] [@o-lukas/homebridge-smartthings-tv] Process Ended. Code: 143, Signal: null
[1/15/2024, 7:17:02 PM] [@o-lukas/homebridge-smartthings-tv] Restarting Process...
[1/15/2024, 7:17:02 PM] [@o-lukas/homebridge-smartthings-tv] Launched child bridge with PID 2586
[1/15/2024, 7:17:02 PM] Registering platform '@o-lukas/homebridge-smartthings-tv.smartthings-tv'
[1/15/2024, 7:17:02 PM] [@o-lukas/homebridge-smartthings-tv] Loaded @o-lukas/homebridge-smartthings-tv v1.10.3 child bridge successfully
[1/15/2024, 7:17:02 PM] Loaded 0 cached accessories from cachedAccessories.0ECFC154A937.
[1/15/2024, 7:17:02 PM] Homebridge v1.7.0 (HAP v0.11.1) (@o-lukas/homebridge-smartthings-tv) is running on port 54095.
[1/15/2024, 7:17:03 PM] [@o-lukas/homebridge-smartthings-tv] Adding new accessory: Samsung Q6DAA 65 TV (01a48093-2bb8-a613-e45c-75e8d84afe1c)
[1/15/2024, 7:17:03 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capabilities for component main
[1/15/2024, 7:17:03 PM] Samsung Q6DAA 65 TV E98D is running on port 36313.
[1/15/2024, 7:17:03 PM] Please add [Samsung Q6DAA 65 TV E98D] manually in Home app. Setup Code: 464-46-219
[1/15/2024, 7:17:04 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: Switch
[1/15/2024, 7:17:04 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: Audio Volume
[1/15/2024, 7:17:05 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: Audio Mute
[1/15/2024, 7:17:08 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: launchApp
[1/15/2024, 7:17:08 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Capability launchApp might not work as expected because it's status is: proposed
[1/15/2024, 7:17:08 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering applications will probably not work because TV is not turned on
[1/15/2024, 7:17:20 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering capability: Media Input Source
[1/15/2024, 7:17:20 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Capability Media Input Source might not work as expected because it's status is: proposed
[1/15/2024, 7:17:20 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering input source: TV (dtv)
[1/15/2024, 7:17:20 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Registering input source: Receiver (HDMI2)
[1/15/2024, 7:17:22 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Resetting active identifier to TV because application registration needed to open all applications
[1/15/2024, 7:17:23 PM] [@o-lukas/homebridge-smartthings-tv] [Samsung Q6DAA 65 TV] Error when executing setInputSource of capability samsungvd.mediaInputSource: Request failed with status code 409: {"requestId":"2789193302944681401","error":{"code":"ConflictError","message":"invalid device state","details":[]}}
[1/15/2024, 7:17:23 PM] [@o-lukas/homebridge-smartthings-tv] Error when getting devices: HAP Status Error: -70402

Logs

{
"bridge": {
"name": "Homebridge 5514",
"username": "xxxxxxxxx",
"port": 51942,
"pin": "464-46-219",
"advertiser": "bonjour-hap",
"bind": [
"eth0"
]
},
"accessories": [],
"platforms": [
{
"name": "Config",
"port": 8581,
"platform": "config"
},
{
"token": "xxxxxxxx",
"capabilityLogging": true,
"registerApplications": true,
"registerPictureModes": true,
"registerVolumeSlider": true,
"deviceMappings": [
{
"deviceId": "6fce470c-63ec-c00f-85cd-d43a2b61562a",
"wol": false
}
],
"_bridge": {
"username": "xxxxxxxx",
"port": 54095
},
"platform": "smartthings-tv"
}
]
}

Environment Information

- Plugin Version: v1.10.3
- Homebridge Version: <!-- homebridge -V1.7.0 -->
- Node.js version: <!-- node -v18.19.0 --> 
- NPM version: <!-- npm -v -->
- Operating System: <!-- Ubuntu / Docker / hb-service -->

Trying to add a tv in HomeKit; not working so far ..or might just need a PIN?

Before opening the issue, have you...?

  • Searched for existing issues
  • Looked through common issues
  • Updated plugin to the latest version (if applicable)

Describe Your Problem

Using homebridge and HomeKit all latest releases/
Trying to add a tv to HomeKit to use it (it’s showing in the web based Homebridge which is promising though )

I click add accessories
It shows in Nearby devices
(Sammy 65 556C) name
Asks for a setup code ; not sure what is ideal but I’ve tried a few. 0000 seems to nearly work and 0000-0000 gives an instant
Accessory not Ready to Connect ; even when the tv is powered on and connected to the network

Logs

No response

If applicable, add screenshots to help explain your problem.

image
image
image
image
image

Environment Information

- Plugin Version:
- Homebridge Version: <!-- homebridge -V -->
- Node.js version: <!-- node -v -->
- NPM version: <!-- npm -v -->
- Operating System: <!-- Raspbian / Ubuntu / Debian / Windows / macOS / Docker / hb-service --> Raspian

TV turns off but not on.

Before opening the issue, have you...?

  • Searched for existing issues
  • Looked through common issues
  • Updated plugin to the latest version (if applicable)

Describe the bug

I'm running Smartthings TV plugin on Hoobs.

It works fine when turning off but not when turning on.

I read in a previous post that the solution was to remove the Device ID, which I did to no avail.

It's a Samsung Frame TV, only used in Art Mode. It's on Wifi, since ethernet wire doesn't work because the TV goes to TV mode when turning on wire and smarthings app fails all the time. Samsung stuff.

To Reproduce

Turn tv on then off

Expected behavior

Turn TV on and off with Homekit.

Logs

11/14/2023, 3:56:38 PMSmartThings Tv Bridge starting11/14/2023, 3:56:42 PMSmartThings Tv BridgeLoaded plugin '@o-lukas/homebridge-smartthings-tv'11/14/2023, 3:56:42 PMSmartThings Tv BridgeLoading 1 platforms...11/14/2023, 3:56:42 PMSmartThings Tv BridgeBridge is running on port 51946.11/14/2023, 3:56:43 PMSmartThings Tv Bridgesmartthings-tvAdding new accessory: Samsung The Frame 43 (c377ab8b-4955-5890-fb7c-4aa1edab75fb)11/14/2023, 3:56:43 PMSmartThings Tv Bridgesmartthings-tv[Samsung The Frame 43] Registering capabilities for component main11/14/2023, 3:56:43 PMSmartThings Tv BridgeSamsung The Frame 43 611D is running on port 44855.11/14/2023, 3:56:44 PMSmartThings Tv Bridgesmartthings-tv[Samsung The Frame 43] Registering capability: Switch11/14/2023, 3:56:44 PMSmartThings Tv Bridgesmartthings-tv[Samsung The Frame 43] Registering capability: Audio Volume11/14/2023, 3:56:45 PMSmartThings Tv Bridgesmartthings-tv[Samsung The Frame 43] Registering capability: Audio Mute11/14/2023, 3:56:49 PMSmartThings Tv Bridgesmartthings-tv[Samsung The Frame 43] Not registering capability because registering of applications has been disabled: launchApp11/14/2023, 3:56:51 PMSmartThings Tv Bridgesmartthings-tv[Samsung The Frame 43] Registering capability: Media Input Source11/14/2023, 3:56:51 PMSmartThings Tv Bridgesmartthings-tvWarning[Samsung The Frame 43] Capability Media Input Source might not work as expected because it's status is: proposed11/14/2023, 3:56:52 PMSmartThings Tv Bridgesmartthings-tv[Samsung The Frame 43] Registering input source: TV

Logs

{
"platform": "smartthings-tv",
"token": "b69e53b7-2538-4dce-a725-4b4173b3c9c9",
"deviceMappings": [
{
"macAddress": "d0:c2:4e:1c:8b:de",
"ipAddress": "192.168.1.18"
}
]
}

Environment Information

- Plugin Version:
- Hoobs Version: 4.3.0
- Node.js version: 16.20.2
- Operating System: Hoobs

Devices not show in homekit

Hello, so i install plugin on my homebridge v 1.6.0. Map devices correct with api and mapping and all my devices show and working on homebridge accesory tab but it didnt show on my homekit, the bridge shows no devices, try without bridge, try with register aplications and capability logging but nothing work, is this bug or i do something wrong

thats how my config looks like

        "token": "---",
        "capabilityLogging": false,
        "registerApplications": false,
        "deviceMappings": [
            {
                "deviceId": "Samsung 5 Series (32)",
                "macAddress": "----",
                "ipAddress": "192.168.31.102 "
            },
            {
                "deviceId": "Samsung Q80AA 65 TV",
                "macAddress": "----",
                "ipAddress": "192.168.31.109"
            }
        ],
        "platform": "smartthings-tv",
        "_bridge": {
            "username": "----",
            "port": 52522

[smartthings-tv] Error when getting devices: options must be an object

Before opening the issue, have you...?

  • Searched for existing issues
  • Looked through common issues
  • Updated plugin to the latest version (if applicable)

Describe the bug

Plugin was working beautifully until recent update. Now I get the error above when I restart homebridge and my device shows as 'No Response' in Home App and accessory has disappeared from homebridge.

To Reproduce

Any restart of homebridge. Tried enabling/disabling plugin; uninstall/re-install; new API Token. Also tried device mapping with Id and Mac address - no success.

Expected behavior

Device (TV) would register and work.

Logs

[smartthings-tv] Error when getting devices: options must be an object

Logs

{
"token": "XYXYXY-removed-XYXYXYX",
"platform": "smartthings-tv"
}

Environment Information

- Plugin Version: v2.0.0
- Homebridge Version: v1.7.0
- Node.js version: v20.12.0
- NPM version: 10.5.0
- Operating System: macOS Catalina

Detecting DisplayPort sources on G9 monitor

Before opening the issue, have you...?

  • Searched for existing issues
  • Looked through common issues
  • Updated plugin to the latest version (if applicable)

Describe the bug

I am openning a new issue on this mater because the old one has been closed automatically, the previous owner did not respond.
I have and odyssey G9 monitor with 2 HDMI inputs and a DisplayPort Input.
So when using the plugin only the two HDMI sources of the monitor are recognized. The Display port input is not proposed.
I am able to switch to the DisplayPort input with the SmartThings app on my phone. (see below)
IMG_3856

To Reproduce

Try to pair a G9 monitor with the plug-in

Expected behavior

All the inputs of the monitor should show in HomeKit.

Logs

[11/22/2023, 3:12:22 PM] [@o-lukas/homebridge-smartthings-tv] [49" Odyssey OLED G9 1] Registering capability: Media Input Source
[11/22/2023, 3:12:22 PM] [@o-lukas/homebridge-smartthings-tv] [49" Odyssey OLED G9 1] Capability Media Input Source might not work as expected because it's status is: proposed
[11/22/2023, 3:12:22 PM] [@o-lukas/homebridge-smartthings-tv] [49" Odyssey OLED G9 1] Registering input source: PC_abby
[11/22/2023, 3:12:22 PM] [@o-lukas/homebridge-smartthings-tv] [49" Odyssey OLED G9 1] Registering input source: PC_portable

Logs

        "token": "******",
        "capabilityLogging": true,
        "registerApplications": false,
        "_bridge": {
            "username": "******",
            "port": ****
        },
        "platform": "smartthings-tv"
    }

Environment Information

- Plugin Version: 1.9.1
- Homebridge Version: 1.7.0
- Node.js version: 18.17.1
- NPM version: <!-- npm -v -->
- Operating System: Raspbian

TV Not Adding in Home App.

Before opening the issue, have you...?

  • Searched for existing issues
  • Looked through common issues
  • Updated plugin to the latest version (if applicable)

Describe Your Problem

Hello!

I just attempted to add my tv to homebridge via your plugin, however, when i go to manually add the tv in the home app, it shows, and then i tap it, type in the code and then it just spins. i've restarted, i've reinstalled the app, on the newest version of homebridge, still the same issue

Please assist
IMG_6850
IMG_6849
IMG_6848

Logs

No response

If applicable, add screenshots to help explain your problem.

No response

Environment Information

- Plugin Version: 1.10.3
- Homebridge Version: 1.7.0
- Node.js version: 18.19.1
- NPM version: <!-- npm -v -->
- Operating System: RHEL 9.3

TV status not updating when turning on and off with remote

Before opening the issue, have you...?

  • Searched for existing issues
  • Looked through common issues
  • Updated plugin to the latest version (if applicable)

Describe Your Problem

My TV's power status is not reliably updating if I turn the TV on or off with the remote. If I power the TV on with the remote it will show as on in the app. However, If I then turn the TV off with the remote its status never updates unless I force close the Home app and reopen. The issue is that when I close and open the app to refresh the status this breaks any automation that is triggered by the status of the TV. I also noticed that another plugin that works fine if I uninstall this plugin starts throwing errors when I have turned the TV off with the remote. I disabled my other plugins to make the logs cleaner. Any help would be appreciated I am new to all this home kit stuff and I am just a little lost with this issue Thanks in advance.

Logs

[23/10/2023, 03:02:43] [Homebridge UI] Homebridge restart request received
[23/10/2023, 03:02:43] [Homebridge UI] UI / Bridge settings have not changed; only restarting Homebridge process
[23/10/2023, 03:02:43] [Homebridge UI] Sending SIGTERM to Homebridge
[23/10/2023, 03:02:43] Got SIGTERM, shutting down Homebridge...
[23/10/2023, 03:02:48] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[23/10/2023, 03:02:53] [HB Supervisor] Restarting Homebridge...
[23/10/2023, 03:02:53] [HB Supervisor] Starting Homebridge with extra flags: -I -P /var/lib/homebridge/node_modules --strict-plugin-resolution
[23/10/2023, 03:02:53] [HB Supervisor] Started Homebridge v1.6.1 with PID: 20028
[23/10/2023, 03:02:54] Loaded config.json with 2 accessories and 8 platforms.
[23/10/2023, 03:02:54] Loaded 15 cached accessories from cachedAccessories.
[23/10/2023, 03:02:54] ---
[23/10/2023, 03:02:54] Disabled plugin: [email protected]
[23/10/2023, 03:02:54] ---
[23/10/2023, 03:02:57] Disabled plugin: [email protected]
[23/10/2023, 03:02:57] ---
[23/10/2023, 03:02:58] Disabled plugin: [email protected]
[23/10/2023, 03:02:58] ---
[23/10/2023, 03:03:00] Disabled plugin: [email protected]
[23/10/2023, 03:03:00] ---
[23/10/2023, 03:03:00] Disabled plugin: [email protected]
[23/10/2023, 03:03:00] ---
[23/10/2023, 03:03:00] Disabled plugin: [email protected]
[23/10/2023, 03:03:00] ---
[23/10/2023, 03:03:01] Disabled plugin: [email protected]
[23/10/2023, 03:03:01] ---
[23/10/2023, 03:03:01] Loaded plugin: @o-lukas/[email protected]
[23/10/2023, 03:03:01] Registering platform '@o-lukas/homebridge-smartthings-tv.smartthings-tv'
[23/10/2023, 03:03:01] ---
[23/10/2023, 03:03:03] Loaded plugin: @seiry/[email protected]
[23/10/2023, 03:03:03] Registering platform '@seiry/homebridge-esphome-ts.esphome'
[23/10/2023, 03:03:03] ---
[23/10/2023, 03:03:03] Loading 8 platforms...
[23/10/2023, 03:03:03] Ignoring config for the platform "Nest" in your config.json as the plugin "homebridge-nest" has been disabled.
[23/10/2023, 03:03:03] Ignoring config for the platform "Kumo" in your config.json as the plugin "homebridge-kumo" has been disabled.
[23/10/2023, 03:03:03] Ignoring config for the platform "TplinkSmarthome" in your config.json as the plugin "homebridge-tplink-smarthome" has been disabled.
[23/10/2023, 03:03:03] Ignoring config for the platform "myQ" in your config.json as the plugin "homebridge-myq" has been disabled.
[23/10/2023, 03:03:03] Ignoring config for the platform "homebridge-intex" in your config.json as the plugin "homebridge-intex" has been disabled.
[23/10/2023, 03:03:03] [esphome] Initializing esphome platform...
[23/10/2023, 03:03:03] [esphome] starting esphome
[23/10/2023, 03:03:03] [smartthings-tv] Initializing smartthings-tv platform...
[23/10/2023, 03:03:03] Loading 2 accessories...
[23/10/2023, 03:03:03] Ignoring config for the accessory "DummySwitch" in your config.json as the plugin "homebridge-dummy" has been disabled.
[23/10/2023, 03:03:03] Ignoring config for the accessory "DummySwitch" in your config.json as the plugin "homebridge-dummy" has been disabled.
Setup Payload:
X-HM://XXXXXXXXXXXXX
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:

┌────────────┐     
│ XXX-XX-XXX │     
└────────────┘     

[23/10/2023, 03:03:03] Homebridge v1.6.1 (HAP v0.11.1) (Homebridge D47F) is running on port 51286.
[23/10/2023, 03:03:03] [esphome] HAP Device discovered jordans-bed-sensor
[23/10/2023, 03:03:03] [esphome] Writing the raw data from your ESP Device to /tmp
[23/10/2023, 03:03:03] [esphome] HAP Device discovered lukes-bed-sensor
[23/10/2023, 03:03:03] [esphome] Writing the raw data from your ESP Device to /tmp
[23/10/2023, 03:03:03] [esphome] Lukes Side Bed Sensor discovered and setup.
[23/10/2023, 03:03:03] [esphome] {
lukes_side_bed_sensor: BinarySensorComponent {
listEntity: {
objectId: 'lukes_side_bed_sensor',
key: 1611208404,
name: 'Lukes Side Bed Sensor',
uniqueId: 'lukes-bed-sensorbinary_sensorlukes_side_bed_sensor',
deviceClass: 'motion',
isStatusBinarySensor: false
},
commandInterface: { sendEspMessage: [Function: sendEspMessage] },
state: BehaviorSubject {
closed: false,
currentObservers: null,
observers: [Array],
isStopped: false,
hasError: false,
thrownError: null,
_value: [Object]
},
terminatePreviousStateSubscription: Subject {
closed: false,
currentObservers: null,
observers: [Array],
isStopped: false,
hasError: false,
thrownError: null
},
teardown: Subject {
closed: false,
currentObservers: null,
observers: [Array],
isStopped: false,
hasError: false,
thrownError: null
},
commandInPipeline: BehaviorSubject {
closed: false,
currentObservers: [Array],
observers: [Array],
isStopped: false,
hasError: false,
thrownError: null,
_value: false
},
'state$': AnonymousSubject {
closed: false,
currentObservers: null,
observers: [],
isStopped: false,
hasError: false,
thrownError: null,
destination: [BehaviorSubject],
source: [BehaviorSubject],
operator: [Function (anonymous)]
}
}
} []
[23/10/2023, 03:03:03] [esphome] Jordans Side Bed Sensor discovered and setup.
[23/10/2023, 03:03:03] [esphome] {
jordans_side_bed_sensor: BinarySensorComponent {
listEntity: {
objectId: 'jordans_side_bed_sensor',
key: 2285865909,
name: 'Jordans Side Bed Sensor',
uniqueId: 'jordans-bed-sensorbinary_sensorjordans_side_bed_sensor',
deviceClass: 'motion',
isStatusBinarySensor: false
},
commandInterface: { sendEspMessage: [Function: sendEspMessage] },
state: BehaviorSubject {
closed: false,
currentObservers: null,
observers: [Array],
isStopped: false,
hasError: false,
thrownError: null,
_value: [Object]
},
terminatePreviousStateSubscription: Subject {
closed: false,
currentObservers: null,
observers: [Array],
isStopped: false,
hasError: false,
thrownError: null
},
teardown: Subject {
closed: false,
currentObservers: null,
observers: [Array],
isStopped: false,
hasError: false,
thrownError: null
},
commandInPipeline: BehaviorSubject {
closed: false,
currentObservers: [Array],
observers: [Array],
isStopped: false,
hasError: false,
thrownError: null,
_value: false
},
'state$': AnonymousSubject {
closed: false,
currentObservers: null,
observers: [],
isStopped: false,
hasError: false,
thrownError: null,
destination: [BehaviorSubject],
source: [BehaviorSubject],
operator: [Function (anonymous)]
}
}
} []
[23/10/2023, 03:03:04] [smartthings-tv] Adding new accessory: Samsung 7 Series (65) (XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX)
[23/10/2023, 03:03:04] [smartthings-tv] [Samsung 7 Series (65)] Registering capabilities for component main
[23/10/2023, 03:03:04] Samsung 7 Series (65) 02DE is running on port 44747.
[23/10/2023, 03:03:04] Please add [Samsung 7 Series (65) 02DE] manually in Home app. Setup Code: XXX-XX-XXX
[23/10/2023, 03:03:04] [smartthings-tv] [Samsung 7 Series (65)] Registering capability: Switch
[23/10/2023, 03:03:05] [smartthings-tv] [Samsung 7 Series (65)] Registering capability: Audio Volume
[23/10/2023, 03:03:05] [smartthings-tv] [Samsung 7 Series (65)] Registering capability: Audio Mute
[23/10/2023, 03:03:07] [smartthings-tv] [Samsung 7 Series (65)] Not registering capability because registering of applications has been disabled: launchApp
[23/10/2023, 03:03:08] [esphome] Writing the raw data from your ESP Device to /tmp
[23/10/2023, 03:03:08] [esphome] Writing the raw data from your ESP Device to /tmp
[23/10/2023, 03:03:08] [esphome] Lukes Side Bed Sensor discovered and setup.
[23/10/2023, 03:03:08] [esphome] {
lukes_side_bed_sensor: BinarySensorComponent {
listEntity: {
objectId: 'lukes_side_bed_sensor',
key: 1611208404,
name: 'Lukes Side Bed Sensor',
uniqueId: 'lukes-bed-sensorbinary_sensorlukes_side_bed_sensor',
deviceClass: 'motion',
isStatusBinarySensor: false
},
commandInterface: { sendEspMessage: [Function: sendEspMessage] },
state: BehaviorSubject {
closed: false,
currentObservers: null,
observers: [Array],
isStopped: false,
hasError: false,
thrownError: null,
_value: [Object]
},
terminatePreviousStateSubscription: Subject {
closed: false,
currentObservers: null,
observers: [Array],
isStopped: false,
hasError: false,
thrownError: null
},
teardown: Subject {
closed: false,
currentObservers: null,
observers: [Array],
isStopped: false,
hasError: false,
thrownError: null
},
commandInPipeline: BehaviorSubject {
closed: false,
currentObservers: [Array],
observers: [Array],
isStopped: false,
hasError: false,
thrownError: null,
_value: false
},
'state$': AnonymousSubject {
closed: false,
currentObservers: null,
observers: [],
isStopped: false,
hasError: false,
thrownError: null,
destination: [BehaviorSubject],
source: [BehaviorSubject],
operator: [Function (anonymous)]
}
}
} []
[23/10/2023, 03:03:08] [esphome] Jordans Side Bed Sensor discovered and setup.
[23/10/2023, 03:03:08] [esphome] {
jordans_side_bed_sensor: BinarySensorComponent {
listEntity: {
objectId: 'jordans_side_bed_sensor',
key: 2285865909,
name: 'Jordans Side Bed Sensor',
uniqueId: 'jordans-bed-sensorbinary_sensorjordans_side_bed_sensor',
deviceClass: 'motion',
isStatusBinarySensor: false
},
commandInterface: { sendEspMessage: [Function: sendEspMessage] },
state: BehaviorSubject {
closed: false,
currentObservers: null,
observers: [Array],
isStopped: false,
hasError: false,
thrownError: null,
_value: [Object]
},
terminatePreviousStateSubscription: Subject {
closed: false,
currentObservers: null,
observers: [Array],
isStopped: false,
hasError: false,
thrownError: null
},
teardown: Subject {
closed: false,
currentObservers: null,
observers: [Array],
isStopped: false,
hasError: false,
thrownError: null
},
commandInPipeline: BehaviorSubject {
closed: false,
currentObservers: [Array],
observers: [Array],
isStopped: false,
hasError: false,
thrownError: null,
_value: false
},
'state$': AnonymousSubject {
closed: false,
currentObservers: null,
observers: [],
isStopped: false,
hasError: false,
thrownError: null,
destination: [BehaviorSubject],
source: [BehaviorSubject],
operator: [Function (anonymous)]
}
}
} []
[23/10/2023, 03:03:08] [smartthings-tv] [Samsung 7 Series (65)] Registering capability: Media Input Source
[23/10/2023, 03:03:08] [smartthings-tv] [Samsung 7 Series (65)] Capability Media Input Source might not work as expected because it's status is: proposed
[23/10/2023, 03:03:08] [smartthings-tv] [Samsung 7 Series (65)] Registering input source: TV
[23/10/2023, 03:03:28] [@seiry/homebridge-esphome-ts] This plugin threw an error from the characteristic 'Motion Detected': Unhandled error thrown inside read handler for characteristic: This callback function has already been called by someone else; it can only be called one time.. See https://homebridge.io/w/JtMGR for more info.
[23/10/2023, 03:03:28] [@seiry/homebridge-esphome-ts] This plugin threw an error from the characteristic 'Motion Detected': Unhandled error thrown inside read handler for characteristic: This callback function has already been called by someone else; it can only be called one time.. See https://homebridge.io/w/JtMGR for more info.

If applicable, add screenshots to help explain your problem.

No response

Environment Information

- Plugin Version: 1.8.2
- Homebridge Version: <!-- homebridge -V1.6.1 -->
- Node.js version: <!-- node -v18.18.2 -->
- NPM version: <!-- npm -v -->
- Operating System: <!-- Raspbian GNU/Linux Bullseye (11) -->

How to change volume from Home app?

Before opening the issue, have you...?

  • Searched for existing issues
  • Looked through common issues
  • Updated plugin to the latest version (if applicable)

Describe Your Problem

I want to volume up/down TV from Home app on iOS, how to do that? I can do it from Homebridge UI but speaker accessory isn’t appearing in the app.

Logs

No response

If applicable, add screenshots to help explain your problem.

No response

Environment Information

No response

The automated release is failing 🚨

🚨 The automated release from the alpha branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the alpha branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


Good luck with your project ✨

Your semantic-release bot 📦🚀

Samsung Smart Monitor M8 (switching or volume does not work)

Before opening the issue, have you...?

  • Searched for existing issues
  • Looked through common issues
  • Updated plugin to the latest version (if applicable)

Describe Your Problem

Thanks for all the work in this plugin - it's quite useful!

I started with issue #121 and was able to configure the plugin, which then found my monitor. Two icons popped up in my accessories list:

Screenshot 2024-02-12 at 20 25 36

However, when I click on the screen, it does not toggle the screen state (ON/OFF). Moreover, when I click the volume button, it does not set the volume on the screen. The following errors appear in the plugin logs.

Am I doing something wrong? Thanks in advance!

Logs

[2/12/2024, 8:16:53 PM] [@o-lukas/homebridge-smartthings-tv] Restarting child bridge...
[2/12/2024, 8:16:53 PM] Got SIGTERM, shutting down child bridge process...
[2/12/2024, 8:16:58 PM] [@o-lukas/homebridge-smartthings-tv] Child bridge process ended
[2/12/2024, 8:16:58 PM] [@o-lukas/homebridge-smartthings-tv] Process Ended. Code: 143, Signal: null
[2/12/2024, 8:17:05 PM] [@o-lukas/homebridge-smartthings-tv] Restarting Process...
[2/12/2024, 8:17:05 PM] [@o-lukas/homebridge-smartthings-tv] Launched child bridge with PID 8458
[2/12/2024, 8:17:05 PM] Registering platform '@o-lukas/homebridge-smartthings-tv.smartthings-tv'
[2/12/2024, 8:17:05 PM] [@o-lukas/homebridge-smartthings-tv] Loaded @o-lukas/homebridge-smartthings-tv v1.10.3 child bridge successfully
[2/12/2024, 8:17:05 PM] Loaded 0 cached accessories from cachedAccessories.0EE26258DD5E.
[2/12/2024, 8:17:05 PM] Homebridge v1.7.0 (HAP v0.11.1) (@o-lukas/homebridge-smartthings-tv) is running on port 45777.
[2/12/2024, 8:17:05 PM] [@o-lukas/homebridge-smartthings-tv] Adding new accessory: Office Screen (998e3aa9-e5cf-c3f3-db17-90ec1a0b2d22)
[2/12/2024, 8:17:05 PM] [@o-lukas/homebridge-smartthings-tv] [Office Screen] Registering capabilities for component main
[2/12/2024, 8:17:05 PM] Office Screen 5773 is running on port 37011.
[2/12/2024, 8:17:05 PM] Please add [Office Screen 5773] manually in Home app. Setup Code: 292-74-856
[2/12/2024, 8:17:06 PM] [@o-lukas/homebridge-smartthings-tv] [Office Screen] Registering capability: Switch
[2/12/2024, 8:17:06 PM] [@o-lukas/homebridge-smartthings-tv] [Office Screen] Registering capability: Audio Volume
[2/12/2024, 8:17:06 PM] [@o-lukas/homebridge-smartthings-tv] [Office Screen] Registering capability: Audio Mute
[2/12/2024, 8:17:08 PM] [@o-lukas/homebridge-smartthings-tv] [Office Screen] Not registering capability because registering of applications has been disabled: launchApp
[2/12/2024, 8:17:09 PM] [@o-lukas/homebridge-smartthings-tv] [Office Screen] Registering capability: Media Input Source
[2/12/2024, 8:17:09 PM] [@o-lukas/homebridge-smartthings-tv] [Office Screen] Capability Media Input Source might not work as expected because it's status is: proposed
[2/12/2024, 8:17:14 PM] [@o-lukas/homebridge-smartthings-tv] [Office Screen] Error when executing on of capability switch: Request failed with status code 409: {"requestId":"7880972982617937632","error":{"code":"ConflictError","message":"invalid device state","details":[]}}
[2/12/2024, 8:17:27 PM] [@o-lukas/homebridge-smartthings-tv] [Office Screen] Error when executing on of capability switch: Request failed with status code 409: {"requestId":"5034803601971331290","error":{"code":"ConflictError","message":"invalid device state","details":[]}}
[2/12/2024, 8:17:50 PM] [@o-lukas/homebridge-smartthings-tv] [Office Screen] Error when executing on of capability switch: Request failed with status code 409: {"requestId":"717287382113043070","error":{"code":"ConflictError","message":"invalid device state","details":[]}}

If applicable, add screenshots to help explain your problem.

No response

Environment Information

- Plugin Version: v1.10.3
- Homebridge Version: 1.7.0
- Node.js version: v18.19.0
- NPM version: 10.2.3
- Operating System: Docker, homebridge image: homebridge/homebridge:latest

node 18 support?

Before opening the issue, have you...?

  • Searched for existing issues
  • Looked through common issues
  • Updated plugin to the latest version (if applicable)

Describe Your Problem

How come the decision to drop support for node 18?

Logs

No response

If applicable, add screenshots to help explain your problem.

No response

Environment Information

No response

Apple home forgets switch and input names after restarting Homebridge

Before opening the issue, have you...?

  • Searched for existing issues
  • Looked through common issues
  • Updated plugin to the latest version (if applicable)

Describe Your Problem

First, let me say thank you for this amazing plugin, I love the functionality this adds to my smart home!

However, I am encountering a small issue: every time I restart the Homebridge, Apple Home forgets the names I set for the sound/picture mode switches, and they are moved from any scenes/automations. Is there any way I can avoid this?
One suspicion I have is that the plugin tries to name the switch something like "Picture: standard". However, Apple Home does not allow colons in the device names.

Thanks!

Logs

No response

If applicable, add screenshots to help explain your problem.

No response

Environment Information

- Plugin Version:
- Homebridge Version: <!-- homebridge -V -->
- Node.js version: <!-- node -v -->
- NPM version: <!-- npm -v -->
- Operating System: <!-- Raspbian / Ubuntu / Debian / Windows / macOS / Docker / hb-service -->

Getting Request failed with status code 409

Describe The Bug:
It was working ok with a week or two with the latest version. For no reason that I aware of, it stopped working with this error:
[5/5/2023, 8:37:00 PM] [smartthings-tv] [Big Li TV] Registering input source: TV
[5/5/2023, 8:37:00 PM] [smartthings-tv] [Big Li TV] Registering input source: HDMI 2
[5/5/2023, 8:37:04 PM] [smartthings-tv] [Big Li TV] Resetting active identifier to TV because application registration needed to open all applications
[5/5/2023, 8:37:05 PM] [smartthings-tv] [Big Li TV] Error when executing setInputSource of capability samsungvd.mediaInputSource: Request failed with status code 409: {"requestId":"EAB05282-B35E-46DF-81AA-4B9C5BD59EF3","error":{"code":"ConflictError","message":"invalid device state","details":[]}}

If I try to power off the tv with Homekit, I got this error:
[5/5/2023, 8:42:04 PM] [smartthings-tv] [Big Li TV] Error when executing on of capability switch: Request failed with status code 409: {"requestId":"F038B173-2AF5-4E1A-8B74-A9428F25A6AA","error":{"code":"ConflictError","message":"invalid device state","details":[]}}

To Reproduce:
I restarted the hb service, rebooted the server, no difference. I used the tv remote to "power off" the tv but no difference. The only thing I plan to try next is to physically power down the TV which is a bit harder since the power plug is behind the tv.

One of two TV not turning on

Please excuse my errors in this request, I'm new at this, well and old new, it been quite a few years since I did and network configuring...

I have installed the home bridge-smartthing-tv plugin and it installed ok. I added two Samsung TV's of different age. The IOS Smartthings app on my phone works flawlessly. I added them to HomeKit, the older of the two works well turns off/on/change input etc. The second a QA65Q800TAWXXY model, can turn off and changes inputs but will NOT turn ON, but will turn off.

Is there something I've missed, like a WOL or some other permission ? I've deleted and re-added without any change. The Samsung access key seems correct, no errors I can see.

Is there a configurable delay between commands anywhere?

I have not seen any popup on the TV to authorise, apart from bluetooth direct from my phone.

There didn't deem to be anything in the log file except for an unsupported Air Purifier, also in SmartThings. There we a few input errors, because I didn't change the config file much from the example, but I didn't change anything as one worked and the other didn't.

Logs: Attached.

config-.json attached.

config-json.txt

LogFile-RW .txt

Getting an error in the log

Describe Your Problem:
Just load this plug-in. After manually adding the TV, I am able to see it on the Home App and actually turn it on/off.
However I saw this error message

Logs:

 [smartthings-tv] [Big Li TV] Error when executing setInputSource of capability samsungvd.mediaInputSource: Conflict

Plugin Config:

{
            "token": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
            "capabilityLogging": true,
            "registerApplications": true,
            "registerPictureModes": true,
            "registerSoundModes": true,
            "deviceMappings": [
                {
                    "ipAddress": "1"
                }
            ],
            "platform": "smartthings-tv"
        }

Screenshots:

Environment:

  • Plugin Version: v1.4.2
  • Homebridge Version: 1.6
  • Node.js Version: 16.16.0
  • NPM Version: 8.11.0
  • Operating System: Raspbian

tv switch not displaying in homekit

Before opening the issue, have you...?

  • Searched for existing issues
  • Looked through common issues
  • Updated plugin to the latest version (if applicable)

Describe Your Problem

Hi,

Thanks for this great plugin. Homebridge web interface shows multiple working commands :

homebridge commands available

Theses commands can actually control the TV directly from the web interface 👍 and most of them are working fine in HomeKit too 👍 , except one ! 😞 which is one of the most important : toggle ON/OFF.

Toggle ON/OFF in homebrige web interface is working too, but no way to see the same switch in HomeKit 👀 .

What am I missing ?

Here is the very simple config file (cleaned) :

{ "token": "XXXXXX-XXXX-XXXX-XXXX-XXXXXXX", "capabilityLogging": true, "cyclicCallsLogging": true, "registerApplications": true, "registerPictureModes": true, "registerSoundModes": true, "registerVolumeSlider": true, "pollInterval": 5000, "deviceMappings": [ { "deviceId": "XXXXXX-XXXX-XXXX-XXXX-XXXXXXX", "wol": true, "macAddress": "MAC_ADDRESS", "ping": true, "ipAddress": "XXX.XXX.X.XX" } ], "_bridge": { "username": "KIND_OF_MAC_ADDRESS", "port": XXXXX }, "platform": "smartthings-tv" }

Logs

[10/11/2023, 19:05:49] [@o-lukas/homebridge-smartthings-tv] Restarting Process...
[10/11/2023, 19:05:51] [@o-lukas/homebridge-smartthings-tv] Launched child bridge with PID 31060
[10/11/2023, 19:05:51] Registering platform '@o-lukas/homebridge-smartthings-tv.smartthings-tv'
[10/11/2023, 19:05:51] [@o-lukas/homebridge-smartthings-tv] Loaded @o-lukas/homebridge-smartthings-tv v1.9.1 child bridge successfully
[10/11/2023, 19:05:51] Loaded 5 cached accessories from cachedAccessories.0ED29E28BE39.
[10/11/2023, 19:05:51] [@o-lukas/homebridge-smartthings-tv] Loading accessory from cache: Picture Confort visuel
[10/11/2023, 19:05:51] [@o-lukas/homebridge-smartthings-tv] Loading accessory from cache: Picture Optimisé
[10/11/2023, 19:05:51] [@o-lukas/homebridge-smartthings-tv] Loading accessory from cache: Sound Amplifier
[10/11/2023, 19:05:51] [@o-lukas/homebridge-smartthings-tv] Loading accessory from cache: Sound Standard
[10/11/2023, 19:05:51] [@o-lukas/homebridge-smartthings-tv] Loading accessory from cache: Volume
[10/11/2023, 19:05:51] Homebridge v1.7.0 (HAP v0.11.1) (@o-lukas/homebridge-smartthings-tv) is running on port 52733.
[10/11/2023, 19:05:52] [@o-lukas/homebridge-smartthings-tv] Adding new accessory: TV Samsung (DEVICE_ID)
[10/11/2023, 19:05:52] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering capabilities for component main
[10/11/2023, 19:05:52] TV Samsung A2ED is running on port XXXXX.
[10/11/2023, 19:05:52] Please add [TV Samsung A2ED] manually in Home app. Setup Code: XXX-XX-XXX
[10/11/2023, 19:05:52] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering capability: Switch
[10/11/2023, 19:05:52] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Start status polling for Switch with interval of 5000ms
[10/11/2023, 19:05:52] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering capability: Audio Volume
[10/11/2023, 19:05:52] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Start status polling for Audio Volume with interval of 5000ms
[10/11/2023, 19:05:52] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering capability: Audio Mute
[10/11/2023, 19:05:52] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Start status polling for Audio Mute with interval of 5000ms
[10/11/2023, 19:05:54] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering capability: launchApp
[10/11/2023, 19:05:54] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Capability launchApp might not work as expected because it's status is: proposed
[10/11/2023, 19:05:54] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering input source: Netflix
[10/11/2023, 19:05:55] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering input source: YouTube
[10/11/2023, 19:05:55] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering input source: YouTubeTV
[10/11/2023, 19:05:56] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering input source: Prime Video
[10/11/2023, 19:05:56] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering input source: Disney+
[10/11/2023, 19:05:56] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering input source: Apple TV
[10/11/2023, 19:05:57] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering input source: Apple Music
[10/11/2023, 19:05:57] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering input source: Amazon Music
[10/11/2023, 19:05:58] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering input source: Spotify
[10/11/2023, 19:05:59] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering input source: Deezer
[10/11/2023, 19:05:59] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering input source: Steam Link
[10/11/2023, 19:06:00] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering input source: Eurosport Player
[10/11/2023, 19:06:00] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering input source: EduPedia
[10/11/2023, 19:06:01] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering input source: ARTE
[10/11/2023, 19:06:01] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering input source: Twitch
[10/11/2023, 19:06:01] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Start status polling for activeIdentifier with interval of 5000ms
[10/11/2023, 19:06:02] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering capability: Media Input Source
[10/11/2023, 19:06:02] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Capability Media Input Source might not work as expected because it's status is: proposed
[10/11/2023, 19:06:02] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Registering input source: TV
[10/11/2023, 19:06:02] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Start status polling for activeIdentifier with interval of 5000ms
[10/11/2023, 19:06:04] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Resetting active identifier to Netflix because application registration needed to open all applications
[10/11/2023, 19:06:05] [@o-lukas/homebridge-smartthings-tv] Restoring existing accessory from cache: Picture Confort visuel
[10/11/2023, 19:06:05] [@o-lukas/homebridge-smartthings-tv] Restoring existing accessory from cache: Picture Optimisé
[10/11/2023, 19:06:05] [@o-lukas/homebridge-smartthings-tv] Restoring existing accessory from cache: Sound Amplifier
[10/11/2023, 19:06:05] [@o-lukas/homebridge-smartthings-tv] Restoring existing accessory from cache: Sound Standard
[10/11/2023, 19:06:05] [@o-lukas/homebridge-smartthings-tv] Restoring existing accessory from cache: Volume
[10/11/2023, 19:06:05] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Start status polling for audioVolume_on with interval of 5000ms
[10/11/2023, 19:06:05] [@o-lukas/homebridge-smartthings-tv] [TV Samsung] Start status polling for audioVolume_brightness with interval of 5000ms

If applicable, add screenshots to help explain your problem.

No response

Environment Information

- Plugin Version: v1.9.1
- Homebridge Version: 1.7.0
- Node.js version: v18.16.0
- NPM version: 9.5.1
- Operating System: Raspbian

Bug: Not able to get device components for Samsung 7 Series TV

Before opening the issue, have you...?

  • Searched for existing issues
  • Looked through common issues
  • Updated plugin to the latest version (if applicable)

Describe the bug

When the plugin tries to discover my devices it logs:

[8/18/2023, 3:44:47 PM] [@o-lukas/homebridge-smartthings-tv] Adding new accessory: Samsung 7 Series (XXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX)
[8/18/2023, 3:44:47 PM] [@o-lukas/homebridge-smartthings-tv] Error when getting devices: _a.at is not a function

To Reproduce

Try to discover a Samsung 7 Series TV.

Expected behavior

To discover TV correctly and load its components.

Logs

[8/18/2023, 3:44:47 PM] [@o-lukas/homebridge-smartthings-tv] Adding new accessory: Samsung 7 Series (XXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX)
[8/18/2023, 3:44:47 PM] [@o-lukas/homebridge-smartthings-tv] Error when getting devices: _a.at is not a function

Logs

{
    "token": "XXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
    "capabilityLogging": true,
    "registerApplications": true,
    "registerPictureModes": true,
    "registerSoundModes": true,
    "platform": "smartthings-tv",
    "_bridge": {
        "username": "XX: XX: XX: XX: XX: XX",
        "port": 58259
    }
}

Environment Information

- Plugin Version:
- Homebridge Version: v1.6.1
- Node.js version: v14.17.6
- NPM version: 6.14.15
- Operating System: macOS

Follow up - TV not adding

Before opening the issue, have you...?

  • Searched for existing issues
  • Looked through common issues
  • Updated plugin to the latest version (if applicable)

Describe Your Problem

Sorry, delete if necessary, i am new to github and do not know how to reopen an issue. But i get the following even after unpairing the tv from my homebridge:

[Living Room TV] Capability Media Input Source might not work as expected because it's status is: proposed

The tv is literally just on one of the hdmi inputs

Logs

No response

If applicable, add screenshots to help explain your problem.

No response

Environment Information

- Plugin Version:
- Homebridge Version: <!-- homebridge -V -->
- Node.js version: <!-- node -v -->
- NPM version: <!-- npm -v -->
- Operating System: <!-- Raspbian / Ubuntu / Debian / Windows / macOS / Docker / hb-service -->

Volume not showing correctly

Describe The Bug:
The volume showing in the Homebridge Config UI does not match the value of the TV.

To Reproduce:

  1. open accessories page
  2. set a volume using the volume slider
  3. change volume using normal TV remote

Expected behavior:
Volume showing in Homebridge Config UI accessories page should match the volume of the TV.

Application list

Before opening the issue, have you...?

  • Searched for existing issues

Is your feature request related to a problem? Please describe

Found an application list with even more IDs. Maybe you can integrate those IDs?

https://tavicu.github.io/homebridge-samsung-tizen/extra/applications.html#list-with-ids

Also: the application registering after a homebridge reboot does not work reliable for me. sometimes only the ids instead of the name is shown. (didn't report this, since it seems to be "work in progress".)

Describe the solution you'd like

Integrate the IDs from above.

Describe alternatives you've considered

none

Additional context

none

Is it possible to use a combined accessory in Homekit?

Before opening the issue, have you...?

  • Searched for existing issues
  • Looked through common issues
  • Updated plugin to the latest version (if applicable)

Describe Your Problem

I have a Sony Bravia TV and am using the Bravia TVOS pluigin for Homebridge (https://github.com/seydx/homebridge-bravia-tvos). That plugin is able to create a single accessory in Homekit which combines a power button, brightness/volume slider and input selector into one. I believe the power and input are one accessory and the volume is a second.

It is possible to do this with the smartthings-tv plugin?

Logs

No response

If applicable, add screenshots to help explain your problem.

No response

Environment Information

- Plugin Version:
- Homebridge Version: 1.7.0
- Node.js version: 20.10.0
- NPM version: 10.2.5
- Operating System: Raspbian / Debian 12 (via Homebridge Raspi image)

Which ports to open in Firewall

Before opening the issue, have you...?

  • Searched for existing issues
  • Looked through common issues
  • Updated plugin to the latest version (if applicable)

Describe Your Problem

Which Ports are used by the Plugin?
I'm running homebridge via docker on a Synology DiskStation.
When I have the Firewall of the Diskstation activated the HomeApp doesn't get response by the TV.
When I deactivate the Firewall the TV is shown in the correct state and reacts.

Which Ports do I need to open in the Firewall to allow the communication between the HomeApp and the Plugin?

Logs

No response

If applicable, add screenshots to help explain your problem.

No response

Environment Information

- Plugin Version: v1.9.1
- Homebridge Version: 1.6.1
- Node.js version: v18.13.0
- NPM version: <!-- npm -v -->
- Operating System: Docker

Implement Samsung Smart Monitor 4K M7

Before opening the issue, have you...?

  • Searched for existing issues
  • Looked through common issues
  • Updated plugin to the latest version (if applicable)

Describe Your Problem

Samsung Smart monitor M7 is not showing up on Homebridge. I believe it is identical to Samsung TV in terms of features.

It would be great if you can add this device.

Thanks for your work

Logs

[6/17/2023, 6:35:58 PM] [smartthings-tv] Ignoring SmartThingsDevice 4K Monitor (device---id) because device type x.com.st.d.monitor is not implemented

If applicable, add screenshots to help explain your problem.

No response

Environment Information

- Plugin Version: 1.5.0
- Homebridge Version: v1.6.1
- Node.js version: v18.16.0
- NPM version: 9.5.1
- Operating System: hb-service on Raspbian

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.