Yeah I got as far as resetting all the stolen bulbs and the remote and re-pairing the bulbs to ST, and even pairing the Lutron remote to the ST hub by holding it nearby with the power button held, as you suggested. ST found it as a ‘thing’, but of course I didn’t have the Alpha device type installed so when I repaired the remote to a bulb, it stole it again.
I’ll give the custom code FAQ a read and try and get the device type installed. Thanks!
One more question: after installing the Alpha device type, I’m assuming ST will now see the Lutron remote as something more than just a ‘thing’. But how will that itself stop the Lutron from stealing bulbs when I then pair the remote to the bulb? In other words, how does ST’s understanding of what the Lutron remote is help here, when the Lutron remote just steals the bulb?
Is it because after ST understands what the Lutron remote is, it’s OK for the Lutron remote to steal the bulb, because ST will ‘listen’ to its command and therefore not fall out of sync with the bulb(s) the Lutron remote operates?
Also, I need to clarify something regarding Hue Taps vs Lutron connected remote. They interact very differently with ST. While the Hue Tap, like the Lutron remote, does cause ST to fall out of sync with bulbs, at least it doesn’t ‘steal’ the bulb. And ST can continue to send commands to Hue bulbs after they’ve been operated by Hue Tap. In other words, if Hue Tap turns my Hue bulbs off, sure ST doesn’t register them as off and still registers them as ‘on’, but this isn’t a big deal: in ST for that Hue bulb I just hit ‘off’ (which does nothing) and then hit ‘on’ and then ST turns them back on. So at least ST can continue working with the bulbs, which isn’t the case when I operate the bulbs with the Lutron remote.
In other words, Hue Tap is friendly with ST, while the Lutron remote isn’t. Of course, although I can hit ‘off’ and then ‘on’ to turn the Hue bulb(s) on again after the Hue tap turns them off, I don’t know if ST actions/apps would continue to work – in other words, if the last known Hue bulb state to ST was ‘on’, but then I turned that bulb off using Hue Tap, but then ST got a motion trigger to turn the Hue bulb on, would it? Since it still thinks the bulb is ‘on’, can it still send an ‘on’ command? In other words, does it not really matter that ST falls out of sync, as long as it sends the necessary commands? I don’t know, will have to try, but let me know if you know.
But does anyone know why the Hue Tap can be far more ‘friendly’ with ST than the Lutron remote? Is it because the Hue Tap isn’t binding directly to the bulb, but instead sending commands to the Hue bridge? Even then, ST does fall out of sync despite being connected to the Hue bridge - which is odd. When Hue Tap sends an off command for a Hue bulb to the Hue bridge, since the Hue bridge is connected to ST, shouldn’t ST understand that the Hue Tap told the Hue bridge to turn that bulb off?
I feel that the Lutron remote should almost come with a warning that says that it can really make things difficult by stealing bulbs - it stole my Hue bulb from the Hue Bridge/ST/Echo and I don’t even know how to get this particular Hue bulb ‘back’. I even tried TouchLink to no avail. So now I have a dead Hue bulb… which I guess I’ll have to try resetting using a Hue Dimmer remote, but I digress.
Many thanks again,