Hello all, I’m trying to connect my Innr smart bulbs to the ST hub, but no success. On Zigbee level they seem to connect, but they won’t show up in the App. Tried to create a Device Handler for them (I have the Zigbee details required for this) but then get back the following message:
Org.springframework.security.access.AccessDeniedException: Run Locally Permission not allowed for DeviceType: 7a85c6a2-c1ad-4aff-87a2-f3612b3e4593
Who know what this is, and why I get this error message ?
Alternatively, does anyone already have DH for Innr bulbs ?
I used a ST published DH and then adapted it for Innr Bulbs, but that didn’t work. Meanwhile I understood that ST is working on adding Innr bulbs to their generic DH’s for white, tunable white and color bulbs, so this should already work or work very soon .
Hi Nick. Thank you for your helpful post. This worked perfectly for my Innr B22 RGBW. I thought I was going to have to send it back but I’m now ‘enjoying’ bridgeless Smart Bulb functionality. Paul
Has anyone managed to add the INNR lightstrip in SmartThings? ( Innr Flex Light RGBW FL 130C). Works great with hue hub, but can’t seem to see it in ST.
tried adding device handler found HERE
which it says adds the FL 130C but cant save the handler as it errors with
org.springframework.security.access.AccessDeniedException: Run Locally Permission not allowed for DeviceType: bcca9699-02b5-4f20-ae35-02c072f1bcaa
That’s the default handler SmartThings uses. If the hub isn’t even finding the device, it’s not a handler problem. It should show up as a “thing” at the minimum.
Very strange…the INNR strip is connected to the Hue Hub and works perfectly , and all other bulbs on that hub did not NEED to be added to smartthings…they just appeared…in addition Samsung says that particular INNR strip IS supported
No idea how to progress it now …anyone got any ideas?
SUCCESS…
weird solution… I used the hue b smart app I had already and the new bulb showed up as not added there…so I added it under “choose bulbs”
it then immediately showed up in ST as expected… very odd, but all working now