Hello
I've programmed power off sequence for PS5 and in the device test it runs perfectly every time.
I've identified three issues related to the remote, device and activity issues respectively.
In summary, even when setup and tested working in device settings, the remote, device, activity and inter-activity settings all behave differently.
The first is very disappointing. The latter two are severe bugs.
Thanks
Chris
1) power command sequences don't work in device (or activity ) buttons
When I goto customise remote buttons, the power option that I configured isn't present.
If I goto add command, it only lets me remove the previously incomplete power button, not add the commands that I've programmed.
I'll report that as medium issue
2) the setting for device power off when not in use is disregarded during activity switching.
The power off doesn't even run one step even selecting activity where that device not used...even when tested in Device menu it's fine.
I created and used playstation and Nvidia activities. Being on Playstation activity and then select Nvidia I would expect it to run the power off sequence to shut down the playstation, and then start the Nvidia.
But all that happens is that it starts the Nvidia activity but doesn't attempt a single one of the playstation power down sequence commands.
Logitech was clever enough to know that the playstation isn't needed for the Nvidia activity, and so would run the playstation shutdown script before running the Nvidia startup script.
I'll report this as a high impact bug as the setting exists in the app but isn't working.
3) Power sequence delays ignored in activity power off (and on?). Noted especially when successive event change between hold and click events.
Sequence works when testing from the device power off test page, but not in practice and also not in the activity test sequence.
This is testable by putting in a ridiculous delay of 3 seconds or even longer into each for the end of the first and second steps....
With such a big delay it should be easy to see the pause between the steps. But the delay isn't used at all in the activity test and the sequence races through in just a couple of seconds without observing the delays at all timing.
But for the identical sequence in the device test the delays are observed correctly.
Update: delays seem to be ignored if the command action type is different between the steps or when action is "click"
Redundant steps needed as workaround.
I'll report this as high impact bug.
Power Off Sequences below
Thanks
Chris
Works when tested in Device settings
Order__Command___Action________Hold__Delay
----------------------------------------------------------------------
1______Pause/Break_Press & Hold__0.5 ____1 s
2______Pause/Break_Click__________n/a____0.5 s
3______Down arrow__Press & Hold__0.5____0.5 s
4______Right arrow___Press & Hold__1 _____0.5 s
5______OK___________Click__________n/a____0.5 s
6______OK___________Click__________n/a____0.5 s
^^^^^^^^^^^^^^^^^^^
Edit: following edits needed due to bugs in activity shutdown which ignores delays when compared to testing in device - see comment below
Order__Command___Action________Hold__Delay
----------------------------------------------------------------------
1______Pause/Break_Press & Hold__0.5 ____1 s
2______Pause/Break_Click__________n/a____0.5 s
X______Down arrow__Click__________n/a____0.5 s
3______Down arrow__Press & Hold__0.5____0.5 s
4______Right arrow___Press & Hold__1 _____0.5 s
5______OK___________Click__________n/a____0.5 s
X______Up arrow_____Press & Hold__0.5____0.5 s
6______OK___________Click__________n/a____0.5 s
The extra X aren't actually needed except for the bug because delays seem to be ignored if the command action type is different between the steps when action is "click"
They're inserted in sensitive area where additional delay needed and can actually be any command
provided doesn't change the selection.
Once bug fixed the redundant steps can be removed
