Differences in command parameters (protocol and code)

[JiRo]

Thank you for the good work. If the function of the A, B and C buttons can be expanded to include commands related to switching activities, I will definitely order more Skip 1s. I would like to use them for all TV and media complexes that I manage in a wide area for my relatives, neighbors and friends. But now I ran into a rather fundamental problem.

So far I have only had two activities in Skip 1. I created them using Skip App version 0.9.965 and both work fine. I have a Samsung TV and a Media Center PC in them.
Now we have updated Skip App to version 0.9.066 and added a third activity and added Samsung TV in it again. And immediately during the test after adding the device, I found out that the POWER ON and OFF commands do not work.

So now I have two activities in Skip where controlling the Samsung TV works and one where controlling the same Samsung TV doesn't work.
I exported the Skip configuration and found that the Samsung TV parameters for the first two activities are different from the parameters for the third activity.

Here is an example for the POWER ON command for the first two activities:

{
    "label": "POWER ON",
    "key": "0",
    "code": "0000,006D,0000,0022,00ac,00ac,0016,0040,0016,0040,0016,0040,0016,0015,0016,0015,0016,0015,0016,0015,0016,0015,0016,0040,0016,0040,0016,0040,0016,0015,0016,0015,0016,0015,0016,0015,0016,0015,0016,0040,0016,0015,0016,0015,0016,0040,0016,0040,0016,0015,0016,0015,0016,0040,0016,0015,0016,0040,0016,0040,0016,0015,0016,0015,0016,0040,0016,0040,0016,0015,0016,071c",
    "protocol": "PRONTO"
},

and for POWER ON for the third activity:

{
    "label": "POWER ON",
    "key": "0",
    "code": "eeecheeeggeÉeoieseaeeseaeeseaeesed`esed`esed`esed`esed`eseaeeseaeeseaeesed`esed`esed`esed`esed`eseaeesed`esed`eseaeeseaeesed`esed`eseaeesed`eseaeeseaeesed`esed`eseaeeseaeesed`ese\u0014i",
    "protocol": "eee"
},

Configuration files is attched.

It can be seen that the parameters (protocols and code) are fundamentally different.
I think that the parameterization is done correctly. After all, the first two activities work very well for me. So I wonder where the problem is.

Thanks for explaining.

JiRo

2024-05-15_MEDIA.skip

[jason]

Holy shit, where did the one for the third activity come from? Was that from the wizard? If you delete it and add the same device again, do you get the same thing? Which OS was this in?

It's completely corrupt.

[JiRo]

Thanks for the response.

I use Skip App on Windows 11.

I've tried that several times. Deleted and recreated the third activity, deleted and added the Samsung TV device and always with the same result.

I even tried adding another device (Flirc) to the third activity (Media Centre PC 2) and the commands for it work fine. Here, for example, you can see both commands (for TV and Flirc) for turning on the third activity, and you can see that while TV has the "eee" protocol, Flirc has "PRONTO".

{
    "id": "a8e5198ec0b",
    "deviceModelId": 7523,
    "position": 3,
    "device": "77fac048c98",
    "icon": "/",
    "iconColor": {
        "value": "#FF9DE9"
    },
    "actionId": "8e5198ec0bd",
    "label": "CONTEXT MENU",
    "protocol": "PRONTO",
    "code": "0000,006D,0013,0000,00BC,00BC,0020,0040,0020,0040,0020,0040,0020,0020,0020,0040,0020,0040,0020,0040,0020,00A7,0020,0020,0020,0020,0020,0020,0020,0020,0020,0040,0040,0040,0020,0020,0020,0020,0020,0020,0040,03CD",
    "repeat": 1,
    "up": true,
    "isDragging": false,
    "action": "56"
},
{
    "id": "76dfe7988e9",
    "deviceModelId": 595,
    "position": 4,
    "device": "6d319824c90",
    "icon": "1",
    "iconColor": {
        "value": "#FF9800",
        "isSelected": false,
        "isDisabled": false
    },
    "actionId": "6dfe7988e9e",
    "label": "POWER ON",
    "protocol": "eee",
    "code": "eeecheeeggeÉeoieseaeeseaeeseaeesed`esed`esed`esed`esed`eseaeeseaeeseaeesed`esed`esed`esed`esed`eseaeesed`esed`eseaeeseaeesed`esed`eseaeesed`eseaeeseaeesed`esed`eseaeeseaeesed`ese\u0014i",
    "repeat": 1,
    "up": true,
    "isDragging": false,
    "action": "0"
}

MEDIA Test 3.skip

[jason]

we spotted the issue and pushed a fix. Try removing the device and re-adding. Let me know if that works.

[JiRo]

Unfortunately, still the same status, nothing has changed.

Maybe some sort of cache on the server side?

[jason]

8 hours ago, JiRo said:

Unfortunately, still the same status, nothing has changed.

Maybe some sort of cache on the server side?

Sorry, makes sure you are on the latest: 

Windows v0.9.967
Linux v0.9.967
Mac v0.9.967

[JiRo]

Latest version v0.9.967-Beta works fine. Tested on Windows 11.

Thank you very much.

JiRo

[jason]

8 hours ago, JiRo said:

Latest version v0.9.967-Beta works fine. Tested on Windows 11.

Thank you very much.

JiRo

We posted another update today that should autodetect and correct this.

Mac v0.9.968
Linux v0.9.968
Windows v0.9.968

These are also on the front page of the website. So very sorry for those seeing this issue.