Device without thermometer/humidity sensor

[apppie123]

Sorry to bother you again.

I have a bluetooth sensor which does not have an i2c thermometer but instead only I/O for switch input.

The configuration has been set like this:
#define DEV_SERVICES ( SERVICE_OTA\ | SERVICE_OTA_EXT \ | SERVICE_PINCODE \ | SERVICE_BINDKEY \ | SERVICE_LE_LR \ | SERVICE_RDS \ | SERVICE_KEY \ | SERVICE_TH_TRG \ | SERVICE_THS \ | SERVICE_LED \ )

(Note: I cannot remove SERVICE_TH_TRG and SERVICE_THS because then it will not compile the code)

I got it as far that it is beaconing in adv type 0x09. I also see beacons when one of the key/reed switches is pressed.
However, I never see environmental sensor service data 0x1A18.

I also loaded a pre-compiled firmware just to check it's not me, but with that firmware it also does not broadcast 0x1A18 data.
It appears this data is not being sent when it cannot retrieve TH data. So then I also don't get the battery state and trigger states at regular intervals.

Still trying to wrap my head around why this is. In the code it is not obvious to me when trying to see what is happening.

Any idea why it is not broadcasting 0x1A18?

[apppie123]

It looks to be in the app_advertise_prepare_handler()

"if(wrk.msc.b.th_sensor_read) { // th sensor work"

If this is false then no environmental sensing beacon it sent.

When adding "set_adv_data()", it starts to beacon 0x181A again:
else { // th sensor bad adv_buf.data_size = 0; load_adv_data(); set_adv_data(); }

However, even when the TH sensor is bad, it should still broadcast data since trigger flags and battery status are also in that beacon.

[pvvx]

If the sensor is faulty, an empty beacon is transmitted, indicating a problem with the sensor.
There are no specific codes for transmitting sensor faults in the existing formats.

[apppie123]

I understand. That also means that the trigger and battery data is not being transmitted.

I found some nice window/door sensors that work really well with your project, except this part is missing.
I've hacked together some code and it is working for me now, but that would break as soon as there would be an update for this project. :) I can understand if you want to keep this repo purely thermometer related.

[apppie123]

If it is not too troublesome I could imagine here in the code that it checks if any i2c sensor has been selected to be supported and if none has been selected it would send out a beacon anyway, so you would still get the data(and people could hack their existing devices and remove the TH sensor if they want to save some power and just need the reed functionality).

In the app_config I disabled all USE_SENSOR_XXXX

But I can understand if you don't want to go this route.

[pvvx]

There's no one-size-fits-all solution.
The current program supports devices with various sensors, but it's not designed for a single button. A single button requires completely different algorithms. Otherwise, power consumption will be too high.

And you are setting the options for the build variants incorrectly.

[pvvx]

I understand. That also means that the trigger and battery data is not being transmitted.

Events are transmitted by a separate program branch. This requires an SDK hack. Otherwise, there will be a delay equal to the beacon interval.
Reed switch triggering events are received on the receiving end 3-7 ms after the contact change.

[apppie123]

That's right. I see those transmissions. But that also means that the switch state is unknown if the sensor has not changed state at least once and is received at least once. If the receiving end rebooted, it will not know what the state of the switch is until something changes. So receiving the current switch state at a regular interval with the rest of the data can be useful.

I made the modification as per below. Ideally SERVICE_THS should be able to be disabled, but this is fine for now for this device.
I now have a nice BLE window/door sensor sending updates as soon as a window opens and also every 10 seconds together with the battery information.

This 10 seconds can probably be set much longer as when I press the button on the door sensor it starts to send many beacons and that way my phone has no trouble into connecting to it to change settings, saving a lot of battery power when not in use.

Your repo made it possible to get it to work in a very short time which I am very thankful for.

_attribute_ram_code_
int app_advertise_prepare_handler(rf_packet_adv_t * p)	{
	(void) p;
#if (DEV_SERVICES & SERVICE_RDS)
	if (!blta.adv_duraton_en)
#endif
	{
#if USE_SYNC_SCAN
		scan.enabled = 0; // stop scan
#endif
#if USE_SENSOR_SCD41
		wrk.start_measure = 1;
#else
		// counter of advertising broadcasts until the start of the next measurement
		if(++adv_buf.meas_count >= cfg.measure_interval) {
			adv_buf.meas_count = 0;
			wrk.start_measure = 1;
		}
#endif

#if (USE_SENSOR_CHT8305 || USE_SENSOR_CHT8215 || USE_SENSOR_AHT20_30 || USE_SENSOR_SHT4X || USE_SENSOR_SHTC3 || USE_SENSOR_SHT30)
		if(wrk.msc.b.th_sensor_read) { // th sensor work
			if (wrk.msc.b.update_adv) {
				// new measured_data
				wrk.msc.b.update_adv = 0;
#if USE_SENSOR_INA3221 || USE_SENSOR_SCD41 || USE_SENSOR_INA226
				adv_buf.send_count++; // count & id advertise, = beacon_nonce.cnt32
			}
			set_adv_data();
#else
				adv_buf.call_count = 1; // count 1..cfg.measure_interval
				adv_buf.send_count++; // count & id advertise, = beacon_nonce.cnt32
				adv_buf.update_count = 0; // refresh adv_buf.data in next set_adv_data()
				set_adv_data();
			} else {
#if (DEV_SERVICES & SERVICE_RDS)
				if (!adv_buf.data_size) // flag adv_buf.send_count++ over adv.event
					adv_buf.send_count++; // count & id advertise, = beacon_nonce.cnt32
#endif
				// ++adv_buf.call_count increase the counter of data iteration in advertising
				// adv_buf.update_count == 0xff -> next call only at next measurement
				// adv_buf.update_count == 0 -> refresh adv_buf.data in next set_adv_data()
				if (++adv_buf.call_count > adv_buf.update_count) // refresh adv_buf.data ?
					set_adv_data();
			}
#endif
		} else { // th sensor bad
			adv_buf.data_size = 0;
			load_adv_data();

		}
#else
	set_adv_data();
#endif
#if (DEV_SERVICES & SERVICE_KEY) || (DEV_SERVICES & SERVICE_RDS)
		if(ext_key.rest_adv_int_tad) {
			ext_key.rest_adv_int_tad--;
#if (!USE_EPD)
			if (ext_key.rest_adv_int_tad & 1)
				SET_LCD_UPDATE(); // show "ble"
#endif
		}
#endif // (DEV_SERVICES & SERVICE_KEY) || (DEV_SERVICES & SERVICE_RDS)
	}
#if (DEV_SERVICES & SERVICE_RDS)
	else
	{
#if USE_SYNC_SCAN
		if(!scan.enabled)
#endif
		// restore next adv. interval
		blta.adv_interval = EXT_ADV_INTERVAL*625*CLOCK_16M_SYS_TIMER_CLK_1US; // system tick
	}
#endif
	return 1;		// = 1 ready to send ADV packet, = 0 not send ADV
}

[pvvx]

But that also means that the switch state is unknown if the sensor has not changed state at least once and is received at least once.

Transferring the current state

Button: pvvx/THB2#94