Found I think a bug in BLE connect

If you use the status up down for any actions, when my iPhone setup as BLE, if it leaves and is no longer connected, the software continually switches to on and off then on and off as it checks for status of the device. I would have expected continual checks to see if it is active but not to toggle the status to on while doing so and then flipping it back off.

thanks

Will check

So when eg switching the phone off
You see
Status going down up down ... several times while the phone is still off?




Sent from my iPhone using Tapatalk

I haven’t turned off my phone but did try Bluetooth off. Status keeps cycling on and off.

yes its a bug.. fixing it

thank you

its ready, plugin store refuses my uploads right now.. did not pay my dues .. here the new version on GitHub https://github.com/kw123/pibeacon/releases/tag/v7.100.267

[edit]all on plugin store now

Thank you

my iPhone has been up now for > 18 hours w/o being charged. - also overnight.- exp timer set to 120 secs

using 10 RPI to test the BLEconnect presence of the phone.

Karl

I tested and I think it’s better but still one minor thing. If you use a trigger that acts on any status change, the trigger keeps going when your phone is not connected. While the device status no longer toggles on and off, it seems to toggle a null state which triggers any action with status change. It would work if I set the trigger to be status on do some action. But if the condition is status change, it also continually runs over and over. So it seems when you disconnect completely the status doesnts stay off and only off until it finds you again.

Thanks

the plugin only updates with up/down/expired. not NULL... Could you post the exact trigger you are using .. ie screen shots.

Karl

Ok so there is no Null. However I did conclude that during the period at which you set your BLE device to transition from Up to Down to expired, the status keeps flipping to On/active for a brief second while it checks if you are there. After that timer expires it leaves the device as expired and the trigger stops happening.

Ok I can check for this.

How many rpi do you have > 1 ?
This might be some timing issue when one rpi thinks it’s away and the other still thinks it’s there. There might be some few seconds where that can happen

Karl


Sent from my iPhone using Tapatalk

I am adding a time window after the last status change of 2 secs where it can not change the status again. That should take care of it.. I still need to test this a little further.

Thanks. Sorry for the delay. I now have 5 Pi's.

Will publish later tonight. Still locking at one issue.
Karl


Sent from my iPhone using Tapatalk