Not sure why the "Basic Rule" would turn on a group of Hue lights twice when I use a Lutron Pico?
dev:6712021-04-03 08:53:00.082 pm infoSpot 6 was turned on
dev:6702021-04-03 08:53:00.060 pm infoSpot 5 was turned on
dev:6712021-04-03 08:53:00.058 pm infoSpot 6 was turned on
dev:6702021-04-03 08:53:00.030 pm infoSpot 5 was turned on
dev:6692021-04-03 08:53:00.019 pm infoSpot 4 was turned on
dev:6692021-04-03 08:53:00.010 pm infoSpot 4 was turned on
dev:6682021-04-03 08:52:59.997 pm infoSpot 3 was turned on
dev:6682021-04-03 08:52:59.985 pm infoSpot 3 was turned on
dev:6672021-04-03 08:52:59.976 pm infoSpot 2 was turned on
dev:6672021-04-03 08:52:59.963 pm infoSpot 2 was turned on
dev:6662021-04-03 08:52:59.955 pm infoSpot 1 was turned on
dev:6662021-04-03 08:52:59.937 pm infoSpot 1 was turned on
dev:6892021-04-03 08:52:59.928 pm infoGroup Office Track was turned on
dev:6892021-04-03 08:52:59.903 pm infoGroup Office Track was turned on
app:6592021-04-03 08:52:59.773 pm infoapp: finished
app:6592021-04-03 08:52:59.715 pm infoact: Turn on Office Track
app:6592021-04-03 08:52:59.711 pm infoevt: Office Pico pushed 1
dev:5962021-04-03 08:52:59.674 pm infoOffice Pico button 1 was pushed
Can you rule out (no pun intended...) a Basic Rules issue here? Try just going to "Group Office Track" (the device) directly, run the "On" command from the device page, and see what happens. My guess is that multiple bulbs that are members of that group report their "on" status in quick succession, which the group pays attention to and might log duplicate "was turned on" event descriptions if a second bulb reports an "on" status before the "on" from the first bulb had quite finished processing. You you may or may not also get duplicate events (check the group device "Events" tab), depending on how quick they come in and whether even the platform had time to commit the first before realizing that the second would be a duplicate.
The alternative, of course, is that Basic Rules actually is sending duplicate "on" commands to the group. It's not clear from the logs that this is what is happening (nothing on the app side either suggests this or rules it out for sure, though it only says it's doing it once). The device logs aren't a lot of help since they only show the events (generally the result of a real-world state change reported back from the device[s]), not what commands are really being sent (from the hub, generally with the intent of causing a change).
