How to inform user about device being disabled

[Neo Andersson 143]

Hello

 

Can we somehow inform user, if Quickapp device has been disabled?

Like print it on some label on QA's interface.

Problem is, that i can't make it by any code, as the code is not run, while device is disabled..

Is there any workaround?

[SmartHomeEddy 818]

You could build a QuickApp that checks now and then which devices are disabled and show them in the label of that new QuickApp. 

[Neo Andersson 143]

2 minutes ago, SmartHomeEddy said:

You could build a QuickApp that checks now and then which devices are disabled and show them in the label of that new QuickApp. 

Thanks, yes i know that, but i was looking for some solution, that can be used on the Quickapp itself, internally, and not by checking from another quickapp.

But probably this is not possible,  as device is disabled, so there is no way to interact with it.

[SmartHomeEddy 818]

Ah, ok

 

You can see it in the debug log when the QuickApp is being disabled with this code in onInit():

 

Please login or register to see this code.

You could add some other code to show it somewhere else. 

[Neo Andersson 143]

1 minute ago, SmartHomeEddy said:

Ah, ok

 

You can see it in the debug log when the QuickApp is being disabled with this code in onInit():

 

Please login or register to see this code.

You could add some other code to show it somewhere else. 

Yeah, but how to cacth it? How to cacth, when this DISABLED state occours.. Does it trigger some event? Ot how else to cacth it from inside the quickapp. Should I listen in a loop to the ENABLED property change??? But if I do so, and the quickapp gets disabled, my code also stops working...thats the point...

[SmartHomeEddy 818]

If the QuickApp runs and you disable it, it starts the onInit() and you catch it with this code. 
 

BTW without this code, the QuickApp still runs. 

[jgab 1,957]

yes, but @Neo Andersson uses fibaroExtra, or? that code intercepts onInit and disables the QA, like in your example.

[Neo Andersson 143]

1 minute ago, jgab said:

yes, but @Neo Andersson uses fibaroExtra, or? that code intercepts onInit and disables the QA, like in your example.

yes i am using Fibaroextra

[jgab 1,957]

ok, I pushed a new version of fibaroExtra v0.957 with a fix.

define the function fibaro.__disabled and it will be called when the qa is disabled. there you can set a label or something in the qa ui.

Please login or register to see this code.

 

Edited March 11, 2023 by jgab

[Neo Andersson 143]

2 hours ago, jgab said:

ok, I pushed a new version of fibaroExtra v0.957 with a fix.

define the function fibaro.__disabled and it will be called when the qa is disabled. there you can set a label or something in the qa ui.

Please login or register to see this code.

 

Great..thanks

[Neo Andersson 143]

1 hour ago, Neo Andersson said:

Great..thanks

Jan, when i disable the QA, it still reacts to button clicks. (ofcourse throwing some errors, as all the variables are not loaded)

Is this normal? I mean, is it normal, that user can still click on buttons and functions are called on button clicks?

Edited March 11, 2023 by Neo Andersson

[jgab 1,957]

13 hours ago, Neo Andersson said:

Jan, when i disable the QA, it still reacts to button clicks. (ofcourse throwing some errors, as all the variables are not loaded)

Is this normal? I mean, is it normal, that user can still click on buttons and functions are called on button clicks?

Yes it is. You need to redefine action and UI handler to not accept any events.
 

Please login or register to see this code.