Skybell Trim Plus not working with Smartthings

Hey guys,

I was looking for some help with the Skybell Trim Plus integration with Smartthings. The original Skybell HD API does not seem to work with the Trim Plus. When the doorbell button is pressed it produces a error:

074305d5-0d36-48db-b527-f37792110055 ( 12:49:09 PM: error groovy.lang.MissingPropertyException: No such property: id for class: java.lang.String

The indoor and outdoor chime option is always reading ‘Off’ even though they are on in the Skybell app. The doorbell button does not trigger anything in Smartthings or IFTTT. The motion sensor is also not working in the integrated environment.

Not really sure what to do next. I have contacted ST and SB support and gone through all the various troubleshooting but they both agree it might have something to do with the API connector in between. I ran Live Logs and received that error.

Does anyone here have any further info that they can share? After digging around for a bit I realized that it’s been almost a year that the Trim Plus version has been out. Others must have also faced similar issues.

Please help!


there are 2 or 3 threads in the past week about the integration being broken. no further info to share until skybell and smartthings get together to fix it.


So I got an email back from Skybell with regards to the issue we are all facing.

"Thank you for contacting SkyBell Technical Support.

I have received word that a request has been put in to review and fix this particular integration. Change logs and updated software has been sent to Samsung, we are awaiting verification to begin implementing these changes."

Hope this gets the ball rolling. If everyone here submits a ticket for this, maybe it will add some more priority to the issue.

I am experiencing the same issue. Trying to use skybell trim plus to turn on lights through ST. Never works and i get the chime off as well. I submitted a ticket and called and SB told me the issue is with samsung smartthings after they pushed out an update. They are aware of this issue and are working on a fix. Has anyone contacted ST recently regarding this issue?

1 Like