@designsymbiosis Look at the light color while pressing the button. Is it red and flashing?

I changed the battery of 1 of my buttons after only 3 months. When looking at the battery, it was abnormally oxidized on one side. I replaced it and was able to get the 2 red flash upon pressing.

I use IFTTT and get the clickTime as an ingredient from the button. Usually, event is received by IFTTT right after (within 5s). However, sometimes, event is delayed to tens of second or even 1mn. Probably because of Internet unavailability from my smart phone or on the IFTTT web site since the phone receives the button click immediately (it beeps). In these situations, I would expect to get the actual (original) click time in the IFTTT ingredient but instead I get the delayed forwarding timestamp in it.

I used 2 buttons integrated with Microsoft flow using a single flic connection in flow.

After several tests, it looks like the very first button press is not forwarded immediately to flow.
However, when pressing the button a second time, the first button press gets forwarded.

This is no a huge problem when using a single button but not ideal since need for 2 button press the very first time the flow is activated. However, when using 2 buttons and press them alternatively, actions triggered by flow are the ones from the other button press!

Has some encountered a similar issue?

I use Microsoft flow as my integration path with forward location enabled. However, I frequently don't get any location within my flow:(
Is there any thing I can change to have this more reliable?

Thanks,

Camille