Is it possible to set a bluetooth condition for ProfileMatic the same way as there are WLAN based conditions, i.e. to have an action (e.g. launch application) when connected to specified Bluetooth device?
Is it possible to set a bluetooth condition for ProfileMatic the same way as there are WLAN based conditions, i.e. to have an action (e.g. launch application) when connected to specified Bluetooth device?
It's not possible currently. I did start to work on implementing that, and used quite a bit time on it, but the Bluetooth APIs did not seem to work as documented. I got pretty fed up with it, so I abandoned working on it as I don't need it myself.
Is it possible to make a custom action to wait for data transfer to stop? If the rule is setting filght mode or using recipe for setting off internet connections, it would be nice to prevent this cutting data transfer or Skype call for example.
It seems to me, that there is something wrong with the net connection rule.
Anyone else experiencing a situation, where the ProfileMatic seems to always think there is no net connection?
I tried a rule where one condition is "no net connection" and it evaluates anyway despite of mobile data or WiFi being active. I also tried to create rule with only "any net connection" rule, and it never gets active.
It seems to me, that there is something wrong with the net connection rule.
Anyone else experiencing a situation, where the ProfileMatic seems to always think there is no net connection?
It has happened to me. But very rarely (like, I've only noticed it once or twice). Judging by console output it seemed to be a platform bug. Ie. even though there was connection, ProfileMatic did not get the notification of it.
Originally Posted by
I tried a rule where one condition is "no net connection" and it evaluates anyway despite of mobile data or WiFi being active. I also tried to create rule with only "any net connection" rule, and it never gets active.
I can't reproduce this. You can of course send the console output when this happens and I can take a look if I see anything weird.
I probably made a mistake last week in uploading the updated deb. I did a new upload on monday so I hope everything goes fine now and it'll be available soon.