When I activate a scene from an Insteon switch, it works perfectly. When I ask Alexa to execute only some of the actions in the scene ate executed

If you activate the scene from the admin console, does it behave the same as with Alexa?

Likely the answer is yes. Which means your scene links are corrupt. Try restoring all the devices in the scene. If that doesn't work, trying removing the device that isn't responding from the scene and then adding it back in. If that doesn't work, start deleting devices, factory resetting them, adding them back to ISY, then creating the scenes again.

Likely issues with the scene - if ISY gets the command from Alexa, Alexa did its part and triggered. Its up ISY and your switches to react to and execute the scene.

@PapaBear , when you execute a scene from your Insteon switch it will interrogate group members via a group cleanup command to verify that they received/acted on the scene command. If a device did not respond correctly, the switch MAY retry xx times.

When you request a scene to be turned on using Alexa, it communicates to the ISY via a Rest command. The ISY in turn executes the scene. The difference is that when the ISY executes a scene it does NOT interrogate the scene members to see if they received/acted on the command. It assumes the command was received properly.

You likely have poor communication to some of the scene members. The switch uses retries to try to improve communications. The ISY (and Alexa) do not.

You can try to improve communications, or use Individual device On/Off commands (Device on/off vs scene on/off). The ISY will use group cleanups and retries for Device Direct commands.

Thanks for the sound advice.

If I execute a program from my ISY will interrogate group members via a group cleanup command?

Also, is there a process I can run to find bad links or device communication issues?

Thanks

4 hours ago, PapaBear said:

If I execute a program from my ISY will interrogate group members via a group cleanup command?

If your program turns of/off a single device, it will request a response from the device.

If your program executes a scene, no cleanups are performed.

Example program with a Scene ON + a device On.

The event viewer output shows that the scene does not request a response from the device.

Turning the device itself on will request a response.

Test - [ID 0071][Parent 0003][Not Enabled]
If
   - No Conditions - (To add one, press 'Schedule' or 'Condition')
 Then
        Set 'SC Basement Bed' On
        Wait  2 seconds
        Set 'Basement / Basement Bed' On
Else
   - No Actions - (To add one, press 'Action')


EVENT VIEWER OUTPUT

######  following is the program turning on a ascene for my basement light - no verification is performed  ###
Thu 12/11/2025 08:43:42 PM : [        Time] 20:43:48 7(0)
Thu 12/11/2025 08:43:42 PM : [INST-TX-I1  ] 02 62 00 00 59 CF 11 00
Thu 12/11/2025 08:43:42 PM : [INST-ACK    ] 02 62 00.00.59 CF 11 00 06          LTONRR (00)


######  program turning on the individual light -  Light responds with 2 Hops left   #########
Thu 12/11/2025 08:43:44 PM : [INST-TX-I1  ] 02 62 13 0A 51 0F 11 FF
Thu 12/11/2025 08:43:44 PM : [INST-ACK    ] 02 62 13.0A.51 0F 11 FF 06          LTONRR (FF)
Thu 12/11/2025 08:43:44 PM : [INST-SRX    ] 02 50 13.0A.51 53.BC.3A 2B 11 FF    LTONRR (FF)
Thu 12/11/2025 08:43:44 PM : [Std-Direct Ack] 13.0A.51-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

4 hours ago, PapaBear said:

Also, is there a process I can run to find bad links or device communication issues?

Since your scene sounds like it is intermittent, I don't believe you have a link problem. If there were bad links, the devices would never respond. If you wish to look for bad or missing links,:

• Right click on a device in the admin console tree.

• Select "diagnostics/show device links table"

• Once the link table has finished populating, click the "compare" tab at the bottom of the table.

• A second table will open showing what the ISY believes the table should contain. Any errors will be noted in the original table.

###### Note - If you see an error flagged with a data value of ": EA" this is not an actual error. #####

Devices that show errors can be corrected by right clicking the device and using the "restore device"

For assessing communication issues -

You can query your devices with the Event Viewer open and set to level 3. Inspect the "Hops remaining" response from the device. Normally commands are sent with max Hops = 3. Responses received back with 3 hops remaining is excellent, 0 not so much.

You can also perform a scene test from the "Tools Menu". This will turn a scene on and then back off. It will request cleanups from the devices and indicate whether they responded properly. This is actually a rather rigorous test.

Edited yesterday at 02:02 AM1 day by IndyMike

Thanks IndyMike. Your wisdom helped me get thins working right.