Welcome to Smart Home Forum by FIBARO
Dear Guest,
as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.
As a member you can:
- Start new topics and reply to others
- Follow topics and users to get email updates
- Get your own profile page and make new friends
- Send personal messages
- ... and learn a lot about our system!
Regards,
Smart Home Forum by FIBARO Team

Question
Guest cuprum
Hoi!
First of all - this is a long story and not tightly related with this specific version (but it's related). So, if admins find for the thread better place, You're welcome;)
The problem description: push notifications for "sleeping" phone not delivered, they delivered if phone wakes up (screen lock opens). Sleeping phone is the phone left alone for long time (i think, couple of hours) and not in charger. NB! for fault the long "sleep" is required. If phone is just locked, the notifications are delivered on time.
First seen: After change the phone from Samsung Galaxy Note3 to Note7 (Now the "hand grenade" is changed to Note8) - long time ago.
In parallel: The co-existing Samsung A6 is "immune" - notifications are delivered at the time.
In parallel2: Notifications from other sources (For example Netatmo) are not affected on Note(s), not on A6 - they delivered on time.
This update: Today morning i discovered that the situation is changed. Yesterday evening i left Fibaro app open (just pressed the "square" to get home screen) and left the phone alone. The result was on-time notification today morning. Day before (with this app version, but closed via series of back and dialogue) the notification was not delivered on time.
So, has someone else also experienced such situations (as the fault is hard to reproduce, and actually i'm not 100% sure, is this specific phone's (or setup's) or phone operating system or is this an application's "feature", the statistic's over other sources is welcome. Also may-be some echo from development team - does they already heard such edge conditions? Hmm, some long time ago posted something similar here, but with "very minor priority" - so i think, this post was just red and forget.
3 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.