SmartThings Integration stopped working #24649
Assignees
Labels
Comments
ghost
assigned 
|
Hey there @andrewsayre, mind taking a look at this issue as its been labeled with a integration ( This is a automatic comment generated by codeowners-mention to help ensure issues and pull requests are seen by the right people. |
|
What the heck is a device type Can you share the output of this command? It will help identify what device is having that rogue type, perhaps you can then remove it or we can update the library to ignore it. curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" https://api.smartthings.com/v1/devices
The output is not sensitive, so you don't need to worry about redacting any of the IDs. |
|
Apologies for the giant block of text, it spit it out exactly as formatted below. |
|
Yeah looks like something changed in the API. You have a number of devices showing up as type {
"deviceId": "0473c5c0-fdae-4a62-9000-b57af9218a 65",
"name": "c2c-rgbw-color-bulb",
"label": "Desk Lamp",
"locationId": "c6358051-231c-49f3-90f0-d09f9cc 884d2",
"roomId": "902ca7f6-ff9a-42af-9432-55399b9582fc",
"components": [
{
"id": "main",
"capabilities": [
{
"id": "switch",
"version": 1
},
{
"id": "switchLevel",
"version": 1
},
{
"id": "colorControl",
"version": 1
},
{
"i d": "colorTemperature",
"version": 1
},
{
"id": "refresh",
"version": 1
},
{
"id": "healthCheck",
"version": 1
}
]
}
],
"profile": {
"id": "4d24a797-e0c0-45ad-8725-04aa6eb2eeb1"
},
"viper": {},
"type": "VIPER"
} |
|
I've reached out to ST, but meanwhile will start working on a fix to handle it. |
|
The Desk Lamp is a TP-Link RGB Bulb plugged into an ordinary socket. If it helps, that one is connected to Smart Things via the TP-Link SmartThings Manager Smart App. |
|
ST confirmed this is a valid type that now shows up in the API. I've updated the library and opened #24659 and it should get pulled into the next beta and released with 0.95.0. |
|
0.95 beta 1 is out and contains a fix for this. |
Working like a charm, now. Thanks so much! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Home Assistant release with the issue: 0.94.4
Last working Home Assistant release (if known): 0.94.4
Operating environment (Hass.io/Docker/Windows/etc.): Hass.io running on Raspberry Pi 3B+
Component/platform: SmartThings Integration ( https://www.home-assistant.io/components/smartthings/ )
Today, when I checked Lovelace, all of my devices connected through SmartThings were being reported as "Entity not Available". I tried restarting both Home Assistant and the Pi that it's running on. I decided to re-install the SmartThings integration to see if that worked. I utilized the Removal Tool ( https://pypi.org/project/hass-smartthings-remove/ ) to ensure everything was properly taken out. I created a new key and was able to add the Smart App to my SmartThings Classic App. However, when I click on the Smart App, it says "Something's Wrong. We can't load your screen right now." And Home Assistant still shows none of the previously controllable entries.
I made sure that my certificates and base URL are both accessible from the outside world (they always have been, and nothing has changed.) I have otherwise made no changes to the system prior to this issue, so I am very puzzled at this point. I enabled Debugging for the SmartThings integration, and the errors are shown below:
Problem-relevant
configuration.yamlentries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
As stated above, I didn't make any changes to the system before this occurred, so I'm not sure what caused. Any insight would be much appreciated!
The text was updated successfully, but these errors were encountered: