Need to hold/repeat RF signal for a few seconds

41

Also, I just saw the project @sriv74 put together: Bond Bridge RF/IR scanner & CQ Encoder It’s awesome! It can let you convert the HEX encoding into the CQ encoding. Then you can add additional delays to the end of the CQ encoding, and boost the reps, and you might get what you’re looking for.

Interesting about the 10 sec limit you are reporting. I thought the limit was 20 sec, but I could be wrong. Something we can review in the V3 effort (we will be doing some optimizations to the radio driver…)

1 Like
42

C:\Users\maxsp>curl -H “BOND-token: 86727107fe973d6e” -i http://192.168.0.183/v2/devices/61ef745f/commands/02bdb432/signal -X PATCH -d “{“reps”: 250}”
HTTP/1.1 200 OK
Content-Length: 6259
Content-Type: application/json; charset=utf-8

{“freq”:350040,“bps”:40000,“deviation”:0,“reps”:250,“modulation”:“OOK”,“encoding”:“hex”,“data”:“FFFFFFFFFF800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003FFFF800000000003FFFFC00000FFFFFFFFFFC00000FFFFFFFFFFC00000FFFFFFFFFFC00000FFFFFFFFFFC00000FFFFFFFFFFC00000FFFFFFFFFFC00000000003FFFFE00000000000FFFFE00000000000FFFFF00000000000FFFFF000003FFFFFFFFFF00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003FFFFC00000000003FFFFC00000FFFFFFFFFFC00000FFFFFFFFFFC00000FFFFFFFFFFC00000FFFFFFFFFFC00000FFFFFFFFFFC00000FFFFFFFFFFC00000000003FFFFC00000000003FFFFC00000000003FFFFE00000000003FFFFE000003FFFFFFFFFE00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003FFFFE00000000000FFFFF000003FFFFFFFFFF000003FFFFFFFFFF000003FFFFFFFFFF000003FFFFFFFFFF000003FFFFFFFFFF000003FFFFFFFFFF00000000000FFFFF00000000000FFFFF80000000000FFFFF800000000003FFFF800000FFFFFFFFFF80000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001FFFFE00000000003FFFFE000003FFFFFFFFFE000003FFFFFFFFFE000003FFFFFFFFFE000003FFFFFFFFFE000003FFFFFFFFFE000003FFFFFFFFFE00000000000FFFFF00000000000FFFFF00000000000FFFFF00000000000FFFFF800000FFFFFFFFFF800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000FFFFE00000000000FFFFE000003FFFFFFFFFE000003FFFFFFFFFE000003FFFFFFFFFE000003FFFFFFFFFF000003FFFFFFFFFF000003FFFFFFFFFF00000000000FFFFF00000000000FFFFF00000000000FFFFF00000000000FFFFF000003FFFFFFFFFF000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003FFFFE00000000003FFFFE000003FFFFFFFFFE000003FFFFFFFFFE000003FFFFFFFFFE000003FFFFFFFFFE000003FFFFFFFFFE000003FFFFFFFFFE00000000000FFFFE00000000000FFFFE00000000000FFFFE00000000003FFFFE000003FFFFFFFFFE00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000FFFFF00000000000FFFFF000003FFFFFFFFFF000003FFFFFFFFFF000003FFFFFFFFFF000003FFFFFFFFFF000003FFFFFFFFFF000003FFFFFFFFFF00000000000FFFFF00000000000FFFFF00000000000FFFFF80000000000FFFFF800000FFFFFFFFFF8000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000”,"_":“b9ad4caa”}

43

Nice to find this topic … looked like the perfect solution/access to default to more reps for my shades. All good for me until I dig down to look for “signal” param options. I successfully find three commands associated with device: “open”, “close” and “hold”. All return “signal” as params but when I dig down to signal, I get “HTTP/1.1 204 No Content” (same with all 3 commands)

Not sure what I’m missing … or something changed for V3? (Firmware v 3.8.4)

Thanks for any help

1 Like
44

I wonder if the “signal” endpoint can be non-existent on cloud-based devices.
It’s been a long time since I had occasion to ask the Bond team if there are any devices that are not fully stored locally (I think the goal at one point in time was to store all devices locally, but originally some had to be stored in the cloud).
@merck / someone else on the Bond team, do you have scenarios still that don’t fully store the signal locally?

To see if there is anything weird with the signal endpoint in the v3.8.4-beta firmware, I just verified a manually recorded device (guaranteed to be locally stored) returns the data as expected:

curl -H "BOND-Token: xxxxxxxxxxxxxxxx" -i http://nnn.nnn.nnn.nnn/v2/devices/aaaaaaaaaaaaaaaa/commands/bbbbbbbbbbbbbbbb/signal
HTTP/1.1 200 OK
BOND-Flags: 4
Content-Length: 6273
Content-Type: application/json; charset=utf-8

{"freq":433930,"bps":40000,"deviation":0,"reps":1,"modulation":"OOK","encoding":"hex","data":"...."}
45

Thanks very much for the response. Ah, didn’t think about the cloud vs. local storage… makes sense though would leave me wondering how to apply remote/cloud settings if not local. Hope to hear from the Bond team!

46

Wondering if there’s any status I could get from the Bond team on this issue … is there any remedy (an addition to the app?) for setting repeat for bridges without the corresponding local storage?

47

@merck - suggestions?
Are we barking up the right tree, thinking it might still be a cloud device somehow? Or are Shade type devices special and the Signal API endpoint is somehow different?

(@ajh - if we don’t hear from the team here soon, have you tried chatting with Support in the app or sending an email to customersupport?)

48

Thanks, yes I’ve emailed support, who pointed me here as a place Bond tech support would be checking. I will try them again … not ideal obviously, but I’m thinking a second bridge timed to schedule the same events as the first might accomplish the same goal of each device getting a repeat command…

49

Ah, curious. The Bond staff (such as Merck, tagged above, and @endy ) do come through here as time permits, but I was under the impression that more real-time support was better served in the app’s Chat or via the email ticketing system.
Fingers crossed someone has a chance to stop by here this week!

50

All devices have been local for some time, and we’ve never had “cloud” devices for shades.

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.

1 Like
51

Okay. Thanks for the details, so we don’t waste time trying to figure out “reps”.

52

@merck and @residualimages thank you. As far as scheduled opening/closing of shades, also thought redundant (e.g. “open at sunrise”) commands set in app might work. the app seemed to accept it, even though identical to previous set. Maybe that will work for me…

2 Likes