Add event based popup or notification

[carp3-noctem]

Is there a way to use a PopUp on the Remote / App that can indicate a change in the Device state?
As Example:
1:
Implementation of smart Heating System (tado°) can provide a Away, Home or Sun state. So I would like to (if i implement the System to NEEO) to be able to send out an Popup to the Remote, when the Sun is shining with much force, to ask the user if he like to lower sunshades / lower heatingpower.
2:
For the Enigma2 Implementation i can display Massages that are displayed from Enigma2 (on the TV) also on the Remote. This mainly are Info Messages like "Recording Started", "Update available".

If this is not yet possible, then see it as feature request

[pfiaux]

This isn't currently possible, I think the only pop up exposed is in lists for info items but it's triggered by user action not by driver.

Currently devices only have UI elements on their own controls or on the controls of other devices (via wiring/shortcuts), so pop ups might be exposed there. For non active devices we're talking about a global pop up, no matter if the device is on or off it might show a popup. I'm guessing based on the examples you have you would like global anywhere pop ups?

Since pop ups can be annoying we'll have to check with the design team if this can be added as a feature.

[carp3-noctem]

Also helpful might be a info bar at the upper part of the display, like ios behaves when an app is open.

Both cases would be good, but it also would help that a person using a device can decide if he is willed to see the pop-ups or not.

Thanks anyway, for the fast and detailed feedback.

[neophob]

Other option: there is the Event Log - which might be more suitable (think about your remote is sleeping or powered off). exposing this to the remote might make more sense imho.

@carp3-noctem - waiting on your feedback

[carp3-noctem]

I don't think the event log is suitable for my idea, since normally I don't look into it. It is definitely a nice feature when it comes to errors or testing but not for events, like user action or Informations like Löw battery on a unit. Therefor nobody normally looks into the event log.
When the remote is sleep, there should be no attention to such things, but as new example related to battery:
When tado is implemented and the system detects low battery neeo can inform the user about it, so a replacement can be done.
But definitely to not disturb a user, it must be configurable through the driver how often it is used and from the user if it should be lower or higher or fully silent (e.g. Popup by every pickup, popup once a day, no popup for this device)

[tmrobert8]

Just to add another use case:
Russound whole house system has a big dynamic UI section to it (hard to explain but it will manage the media for you and provide, via it's API, dynamic information to display).

Example - let's say I startup a Pandora source. While listening to that source, there will be a button to create a 'station' similar to what is currently playing (a station is like a playlist of related music). If I press that button, the system will create a new station and provide a popup information stating something similar to "Station 'xxxx' created" (where 'xxxx' is the name of the new station - important information).

Right now - I can easily put the create station button on the remote however the plugin would need the ability to 'popup' the message when the station is created. Note: the popup is done async to the button press since it takes time to create - so it can't simply be a response to the button press. So the popup let's me know two things: 1. that the station has been created finally and is available and 2. what the name of the station is.

I could state a couple more use cases - but that's a pretty simple one to understand.

Ideally the popup would also allow a yes/no (ok/cancel) type of thing as well.

[carp3-noctem]

@neophob @pfiaux are there still infos required for this one?

[pfiaux]

We'll need to explore various points internally since pop ups can be quite disruptive on the user experience such as

• adding a kind of notification as well, which is less disruptive when no input is needed
• limitations imposed on driver popups (only as result of user action or only if recipe is active, or based on permissions granted by user...)
• technical requirements and changes needed

High level summary of use-cases/possibilities:

• display a popup/notification as a response to a user action (async)
• display a popup/notification as a response to a driver event

In the pop up case it needs to have further callbacks based on the options selected.