Northern Man

Receiver sample in 2-FSK Mode When running in this mode ( I just changed the modulation default in ELECHOUSE_CC1101_SRC_DRV.cpp from 2 to 0 ) I can see the FSK Transmitter...

Hit a minor setback last night, and need to get the soldering iron back out again. I was looking at using carrier sense to determine start and end of signal...

Well I have had some initial success with receiving FSK signals from the sample transmitter your created @AusGunno. This is the FSK branch and the example/FSK_Sample complied under platformio and...

I have updated the first comment into a tracker of release status of this feature.

I think I found the issue with the FSK Reception and why I was only successfully receiving and decoding 1 signal in 10, the sample transmitter was shutting down too...

It’s sitting as a future todo, and the major blocker is access to a device to test with. My current farm of sensors are all OOK based.

No change in status of FSK support Also with the cc1101 receiver, it would only be able to support a single modulation scheme at a time, either OOK or FSK...

The common pattern for indicating that a device is not returning any data is to use the updatecharacteristic method, and return an error value. See this https://developers.homebridge.io/#/api/service#serviceupdatecharacteristic

updateValue also works the same way. In your code, the setValue is not needed. updateValue updates the value within homebridge/homekit

Something odd must be occurring in your code as this pattern works very well as I use it with my homebridge-tasmota plugin https://github.com/NorthernMan54/homebridge-tasmota/blob/master/src/TasmotaService.ts#L184 The reference to `this.characteristic` is the primary...