iOS BETA v1.109 (4) on TestFlight

BETA BETA iOS
1

This iOS build adds support for so-called “state remotes”, which send a control signal containing the entire state of the device (speed, light value) rather than a simple command. These remotes typically have LCD screens.

In particular, the new ceiling fan remote FCC IDs which are fully-supported in this release are:

CHQ7096T
kujce10305
chq7096t
l3hfan9t
kujce10203

The app is currently under Apple review and will be available via Testflight in about 24 hours. Everyone with access to this post (and an iOS device that you have used with the BOND) should be on the Testflight list, and you will receive an email only once the Testflight build is approved by Apple and available to test.

EDIT: Contains BOND firmware v1.108.3.

2

Apple approved the beta. v1.109 (4) is live on TestFlight! :flight_departure:

1 Like
3

Is it ok to move to this version if my Bond is currently on firmware 1.108.4?

4

Good question! The iOS app v1.109 (4) contains firmware v1.108.3, which does not have the experimental DHCP fix. So I’d recommend holding off until we roll the DHCP fix into the firmware in the apps. We haven’t gotten any negative feedback on the firmware v1.108.4 so it’s looking good for mid next week (plus/minus Apple approval).

5

Actually, you can certainly update the iOS app to the beta version! Just say “NO” if you are offered a “firmware update”.

6

OK I updated to both the Test Flight app and the firmware. I am unable to program BOND for my State Remote.
FAN-9T. FCC ID L3HFAN9T I could use some hints on getting this to work. The traditional hold down the button to program not helping.

7

Indeed, we broke L3HFAN3T support this morning. We just about have it fixed… maybe 2hrs needed.

8

OK Thank you. Please let me know when ready. Thanks.

9

Should be OK now. Try rapidly pressing the Light or Fan button while recording. (This remote only transmits once per button press, unlike most others that continue to transmit as long as you are holding the button down.)

10

OK no real luck. I started by testing with light. It took the command. I turned on the light using remote control. Pressed the test button on my phone it went off for a split second then back on. Same for all other options.

11

Did you get a screen like this? This is what you see when a state remote is found in the database.

Image-1
Image-1.jpg1536×2048 226 KB

12

Ah, I checked the packet you recorded on the backend. It doesn’t look like the one we expected. Investigating with our remotes expert…

13

OK never did get a screen like that. I will stand by.

14

This is the L3HFAN-9T that we have here:

IMG_20180122_172156
IMG_20180122_172156.jpg4032×3024 2.18 MB
15166602645065471411769231875139
15166602645065471411769231875139.jpg2851×2138 1.46 MB

Look like yours?

15

Yes even down to the model on back.

IMG_0867
IMG_0867.JPG1512×2016 845 KB
IMG_0868
IMG_0868.JPG1512×2016 587 KB

16

Ok, we narrowed down the issue to your remote transmitting a slightly shorter gap between packets, which is just under a threshold we use for separating the packets apart. Thus the lack of recognition.

Here’s what it looks like in our system:

LUA:DEBUG: Detect packet. freq 302725 bps 3309
LUA:TRACE: data = 110110110110110110110110110110110110110010110010010110010010110000000000000000000000001011011011011011011011011011011011011011001011001001011001001011000000000000000000000000101101101101101101101101101101101101101100101100100101100100101100000000000000000000000010110110110110110110110110110110110
11011001011001001011001001011

Those runs of ~24 zeros should be used as delimiters for the several packets.

We will make some more adjustments and get back to you tomorrow.

17

OK thank you, I will be standing by.

18

Any update on this problem?

19

Just pushed a fix to the backend. Checking now if it’s deployed…

20

Great, I will try to test later if you give me the go ahead.