Fireplace RFP8 patch SIGNAL command

[alexbk66]

I have a request from HomeSeer user to patch SIGNAL for TurnOn command to set ‘reps’ to 5 (following https://global.discourse-cdn.com/standard14/uploads/bond1/original/1X/557412d4d7c2194df21e2025cc488081fe8ac5d2.jpeg)

Problem I’m facing - the SIGNAL command doesn’t seem to be available via API.
Any request like “http://192.168.1.26/v2/devices/47cc0984/commands/6ad2563a”
returns “signal”:{“_”:“00000000”}, and requests like “http://192.168.1.26/v2/devices/47cc0984/commands/3276e6ea/signal”
returns empty string.

FYI, I don’t own the fireplace, I’m testing using my own Bridge with my devices.

[residualimages]

I see the device you’re testing with looks like a Shade type device from.your screenshot.

I noticed someone else before not having a Signal endpoint on Shade devices, but the Bond staff explained that not all devices will have a meaningful Signal endpoint:

@merck

The “signal” endpoint is present for all raw-recorded devices (where you have to record each signal), and also present for some of the one-click devices. However, many shade protocols involve complex or rolling-code packets where we don’t have a signal endpoint: the packets need to be programmatically generated for each transmission, so there’s no way to modify the reps. Depends on the template.

The first long form document screenshot you referenced does look accurate as to how the reps would be changed on a device that has a meaningful Signal endpoint (such as a Fireplace).