Domoticz app 2.0 Topic is solved

[sammyke007]

I might be blind or no widgets in the 0.2.192 (6889) release?
Can't find them in the list when I try to re-add them again. Had lots of widgets..

Widgets stopped working indeed and no way to readd them

Verstuurd vanaf mijn ONEPLUS A6003 met Tapatalk

EDIT: removed for now by the author because of problems. Check GitHub for more info.

[NiklasO]

I might be blind or no widgets in the 0.2.192 (6889) release?
Can't find them in the list when I try to re-add them again. Had lots of widgets..

Widgets stopped working indeed and no way to readd them

Verstuurd vanaf mijn ONEPLUS A6003 met Tapatalk

EDIT: removed for now by the author because of problems. Check GitHub for more info.

Oh. That's too bad.

Edit:
https://github.com/domoticz/domoticz-android/issues/575
The widgets has always worked fine here except when updating the app, they could stop working and look strange but it worked to just remove them and add them back again. I would help if I knew how to develop for Android. Too bad i don't.

[Geitje]

Thanks for the update! I do not use widgets myself, but can understand people feeling sad about removing them...

[EddyG]

Installed the latest beta. This problem still exists: https://www.domoticz.com/forum/viewtopi ... 37&t=31162

[galadril]

Installed the latest beta. This problem still exists: https://www.domoticz.com/forum/viewtopi ... 37&t=31162

So opening the app triggers a device to be turned on / off.. eehhh... what if your clean your app cache/data and reconfigure from start?
Maybe some url got stuck in the request queue.. (never heard of this)

[galadril]

Do you guys see any issues with the latest beta?
Please test and ill push it to prod after this weekend..?

[EddyG]

Tnx. It looks like clearing the cache did the trick.
So this was not related to the latest beta.
No further issues.

[sammyke007]

Do you guys see any issues with the latest beta?
Please test and ill push it to prod after this weekend..?

Working fine here!
Widgets working back as before, tnx!
Merci man!

[aBjerris]

I'm running version 0.2.187 (6509) of the app.
Since Android 10 notifications do not appear promptly while the phone is in standby. It can take 10-15 minutes before the app show a notification.
This was not the case on Android 9 where the notifications showed promptly (within 1-2s) in the phone.
I use Firebase cloud messaging (Former Google Cloud messaging)
I can reproduce this problem on Xperia 1 and Pixel.
Maybe it is fixed in the current Beta version?

[sammyke007]

I'm running version 0.2.187 (6509) of the app.
Since Android 10 notifications do not appear promptly while the phone is in standby. It can take 10-15 minutes before the app show a notification.
This was not the case on Android 9 where the notifications showed promptly (within 1-2s) in the phone.
I use Firebase cloud messaging (Former Google Cloud messaging)
I can reproduce this problem on Xperia 1 and Pixel.
Maybe it is fixed in the current Beta version?

Battery saving or battery optimization disabled for the app?

Verstuurd vanaf mijn ONEPLUS A6003 met Tapatalk

[Geitje]

I have this problem for a long time already (since Android 9). In my case may be related to Oxygen OS. Eventually I found out that disabling Android Doze does the job. Running

Code: Select all

su
dumpsys deviceidle disable

in an Android terminal (I made a tasker task to do this) does the job for me. From then I get notifications immediately. Battery use is only slightly more. Enabling doze can be done with the same command, ofcourse changing disable to enable.

I'm running version 0.2.187 (6509) of the app.
Since Android 10 notifications do not appear promptly while the phone is in standby. It can take 10-15 minutes before the app show a notification.
...

[sammyke007]

I have this problem for a long time already (since Android 9). In my case may be related to Oxygen OS. Eventually I found out that disabling Android Doze does the job. Running

Code: Select all

su
dumpsys deviceidle disable

in an Android terminal (I made a tasker task to do this) does the job for me. From then I get notifications immediately. Battery use is only slightly more. Enabling doze can be done with the same command, ofcourse changing disable to enable.

I'm running version 0.2.187 (6509) of the app.
Since Android 10 notifications do not appear promptly while the phone is in standby. It can take 10-15 minutes before the app show a notification.
...

Exactly. I also have a Oneplus running OxygenOS and since Android Pie (9) they started killing apps agressively. Therefor my pushsafer app always warns me too late (same with Whatsapp, ...). It's only a couple of minutes later, but I don't like that. Disabling battery optimization is not enough. You need to run "dumpsys deviceidle disable" after each reboot to completely disable Doze via ADB or the way you explained with Tasker.

[aBjerris]

I have this problem for a long time already (since Android 9). In my case may be related to Oxygen OS. Eventually I found out that disabling Android Doze does the job. Running

Code: Select all

su
dumpsys deviceidle disable

in an Android terminal (I made a tasker task to do this) does the job for me. From then I get notifications immediately. Battery use is only slightly more. Enabling doze can be done with the same command, ofcourse changing disable to enable.

I'm running version 0.2.187 (6509) of the app.
Since Android 10 notifications do not appear promptly while the phone is in standby. It can take 10-15 minutes before the app show a notification.
...

Exactly. I also have a Oneplus running OxygenOS and since Android Pie (9) they started killing apps agressively. Therefor my pushsafer app always warns me too late (same with Whatsapp, ...). It's only a couple of minutes later, but I don't like that. Disabling battery optimization is not enough. You need to run "dumpsys deviceidle disable" after each reboot to completely disable Doze via ADB or the way you explained with Tasker.

Thanks for the prompt responses.
I'm not very keen on changing the battery optimization settings but I found this article:
https://firebase.google.com/docs/cloud- ... -a-message

In my understanding the FCM messages can be sent with Normal priority or High priority.
Also in case messages are sent with high priority there is a built in learning mechanism which causes the priority to be lowered in case the end user do not act on the notifications.
Anyone who knows what priority is used by Domoticz?

[galadril]

Thanks for the prompt responses.
I'm not very keen on changing the battery optimization settings but I found this article:
https://firebase.google.com/docs/cloud- ... -a-message

In my understanding the FCM messages can be sent with Normal priority or High priority.
Also in case messages are sent with high priority there is a built in learning mechanism which causes the priority to be lowered in case the end user do not act on the notifications.
Anyone who knows what priority is used by Domoticz?

I know that Xiaomi and OnePlusOne are way to aggressive with the battery optimalisation software. For example, by Ring doorbell wouldn't even send notifications within 4 minuten when somebody is in front of the door with the Xiaomi optimalisation on.. And it works correctly with turned of.

You dont need to turn if off for everything.. you can do it on a app per app basis.. just to see if this is your issue..

[sammyke007]

I know that Xiaomi and OnePlusOne are way to aggressive with the battery optimalisation software. For example, by Ring doorbell wouldn't even send notifications within 4 minuten when somebody is in front of the door with the Xiaomi optimalisation on.. And it works correctly with turned of.

You dont need to turn if off for everything.. you can do it on a app per app basis.. just to see if this is your issue..

For me (Oneplus 6), disabling battery optimization is not enough. I still need to run the

Code: Select all

dumpsys deviceidle disable

to make sure I receive my notifications right away. It has nothing to do with priority in my case. Just too agressive app killing by OxygenOS. .

[galadril]

I've pushed the new version from beta to prod for the Android app today.

[aBjerris]

Thanks for the prompt responses.
I'm not very keen on changing the battery optimization settings but I found this article:
https://firebase.google.com/docs/cloud- ... -a-message

In my understanding the FCM messages can be sent with Normal priority or High priority.
Also in case messages are sent with high priority there is a built in learning mechanism which causes the priority to be lowered in case the end user do not act on the notifications.
Anyone who knows what priority is used by Domoticz?

I know that Xiaomi and OnePlusOne are way to aggressive with the battery optimalisation software. For example, by Ring doorbell wouldn't even send notifications within 4 minuten when somebody is in front of the door with the Xiaomi optimalisation on.. And it works correctly with turned of.

You dont need to turn if off for everything.. you can do it on a app per app basis.. just to see if this is your issue..

Ok. I found a setting in Settings/Apps & Notifications/Advanced/Special app access/Power-saving feature.
This is what you are referring to. Right? Here I selected to not optimise the Domoticz app.

[aBjerris]

Thanks for the prompt responses.
I'm not very keen on changing the battery optimization settings but I found this article:
https://firebase.google.com/docs/cloud- ... -a-message

In my understanding the FCM messages can be sent with Normal priority or High priority.
Also in case messages are sent with high priority there is a built in learning mechanism which causes the priority to be lowered in case the end user do not act on the notifications.
Anyone who knows what priority is used by Domoticz?

I know that Xiaomi and OnePlusOne are way to aggressive with the battery optimalisation software. For example, by Ring doorbell wouldn't even send notifications within 4 minuten when somebody is in front of the door with the Xiaomi optimalisation on.. And it works correctly with turned of.

You dont need to turn if off for everything.. you can do it on a app per app basis.. just to see if this is your issue..

Ok. I found a setting in Settings/Apps & Notifications/Advanced/Special app access/Power-saving feature.
This is what you are referring to. Right? Here I selected to not optimise the Domoticz app.

Changing the power-saving option have not had any effect. The notifications are still delayed by several minutes. Anyone knows if Domoticz is using High or Normal priority?

[Geitje]

If disabling battery management not helps: Disable Android Doze, check some posts back: https://www.domoticz.com/forum/viewtop ... 98#p236051

[zwerfkat]

I was able to get rid of the notifications delay by disabling Doze Light only:

Code: Select all

adb shell dumpsys deviceidle disable light

This command should be applied after a restart again, since my phone is not rooted.

Hopefully Android will make it possible to apply these settings manually in the future, but I doubt they will.