QuickApp crashed with hub.alert('simplePush'

[TitiXsi 0]

Hello,
I have updated my HC3 FW 5.190.39 -> 5.200.8 this day and I am facing an issue mentioned on

hub.alert('simplePush', OneMobile,'['..currentFullTime..']'..myMsg, false, '')

[14.01.2026] [00:32:01] [ERROR] [QUICKAPP1768]: QuickApp crashed
[14.01.2026] [00:32:01] [ERROR] [QUICKAPP1768]: main.lua:61: Wrong parameter type, string required. Provided param 'false' is type of boolean

This function is shared in all my QA and Scene, how can we proceed to a Stable updated by having those changes in basing functions ... ?

Have you a fix to provide or a documentation about this function ?

Edited January 15 by TitiXsi

[m.roszak 765]

regards,
Michal

PS
QuickApps never got this 4th parameter - which you are providing as "false".

 

[TitiXsi 0]

Hello,
I have used the same syntax in my Scenes and QuickApps for this call to Push Message... It's curious that this parameter as been removed/changed instead although it was unused...

The Topic Mentioned is talking about 'email' sending with the first parameter, why you are not talking about the others like 'simplePush' commonly used and this Major changes ?

Thanks.

[m.roszak 765]

It was before just ignoring the parameter which was redundant, never handled.
Those enviroments differs a bit and there is not always possible to make them identical due the backward compatibilty. 

[TitiXsi 0]

On 1/20/2026 at 2:01 PM, m.roszak said:

due the backward compatibilty. 

The first backward compatibility was to do not remove a parameter previously declared... But declare it as optional to avoid a crash ...

You are not agree with this ?

[DJ6971 1]

And as usual  no response. I’d really like to see their list of what actually doesn’t work.
I wish that one day the Fibaro team would sit down and start patching all the issues (of course, that will never happen), and only then introduce new features and work on other gadgets. But well, they’re under pressure from other companies that use their technology.

[cag014 731]

On 1/20/2026 at 3:01 PM, m.roszak said:

It was before just ignoring the parameter which was redundant, never handled.
Those enviroments differs a bit and there is not always possible to make them identical due the backward compatibilty.

@m.roszak

I am using Yubii Home mobile application

no combination for push notification is working. (notification permission on the phone granted)

 

email  ID  -> hub.alert("push",{2}, "message") 

mobile ID -> hub.alert("push",{41}, "message") 

 

email  ID  -> hub.alert("simplePush",{2}, "message") 

mobile ID -> hub.alert("simplePush",{41}, "message") 

 

Any of above commands (in QA or in scene) are sending notification to mobile phone.

Any idea how to send it?

By the way, creating a block scene with push notification and converting to LUA, here is the output

 

hub.alert('push', {[1] = 2, }, 'pushTest', false, '', false)

 

what these extra parameters doing there?

In any case it does not working too

 

Using Yubii Home Center, push does work?

Edited January 24 by cag014

[m.roszak 765]

19 hours ago, TitiXsi said:

The first backward compatibility was to do not remove a parameter previously declared... But declare it as optional to avoid a crash ...

You are not agree with this ?

To be honest, yes - I dont agree.

If you got a function which is desinged to use 3 args, and you are providing 4 the last one is just ignored and function still works.
We did add 4th arg handling for allowing to set the title for the notification and you expect to get backward compatiblity with the calls you made which was not correct at the beggining

From the other hand I agree that we should try to keep the enviroments for Lua scenes and QuickApps as much alligned as possible, but its not always possible due the historical reasons. 

EDIT
Or there is something else going on here, devs are on it
 

 

11 hours ago, cag014 said:

@m.roszak

I am using Yubii Home mobile application

no combination for push notification is working. (notification permission on the phone granted)

 

email  ID  -> hub.alert("push"),{2}, "message") 

mobile ID -> hub.alert("push"),{41}, "message") 

 

email  ID  -> hub.alert("simplePush"),{2}, "message") 

mobile ID -> hub.alert("simplePush"),{41}, "message") 

 

Any of above commands (in QA or in scene) are sending notification to mobile phone.

Any idea how to send it?

By the way, creating a block scene with push notification and converting to LUA, here is the output

 

hub.alert('push', {[1] = 2, }, 'pushTest', false, '', false)

 

what these extra parameters doing there?

In any case it does not working too

 

Using Yubii Home Center, push does work?

I will forward your comment to the right tech person for explanation/investigation

 

[m.roszak 765]

11 hours ago, DJ6971 said:

And as usual  no response. I’d really like to see their list of what actually doesn’t work.

You mean that there was no response on community forum for 8h? 
I won't comment that. 

[Raf.Kal 2]

11 hours ago, cag014 said:

@m.roszak

I am using Yubii Home mobile application

no combination for push notification is working. (notification permission on the phone granted)

 

email  ID  -> hub.alert("push"),{2}, "message") 

mobile ID -> hub.alert("push"),{41}, "message") 

 

email  ID  -> hub.alert("simplePush"),{2}, "message") 

mobile ID -> hub.alert("simplePush"),{41}, "message") 

 

Any of above commands (in QA or in scene) are sending notification to mobile phone.

Any idea how to send it?

By the way, creating a block scene with push notification and converting to LUA, here is the output

 

hub.alert('push', {[1] = 2, }, 'pushTest', false, '', false)

 

what these extra parameters doing there?

In any case it does not working too

 

Using Yubii Home Center, push does work?

Hi,

You can send push to the mobile device in two ways:

1. simplePush - sends push to the given mobile device ids: 

   Please login or register to see this code.

2. push - sends push to last used mobile device by given user ids:

   Please login or register to see this code.

In your case there is an error in all 4 attached calls - closing bracket after alert type, it cannot work properly. 

Edited January 22 by Raf.Kal

[Raf.Kal 2]

According to sending alerts in LUA scenes please stick to documentation that can be found here: 

Please login or register to see this link.

Additionally, sending alerts from QuickApps uses different internal SDK than LUA Scenes, so list of parameters differs.

We plan to not so strictly assert 4th parameter which is an email title, that was introduced after the following request from the forum:  

 

Edited January 22 by Raf.Kal

[cag014 731]

On 1/22/2026 at 12:29 PM, Raf.Kal said:

Hi,

You can send push to the mobile device in two ways:

1. simplePush - sends push to the given mobile device ids: 

   Please login or register to see this code.

2. push - sends push to last used mobile device by given user ids:

   Please login or register to see this code.

In your case there is an error in all 4 attached calls - closing bracket after alert type, it cannot work properly. 

Is just a copy-paste error (copied from pcall(...) function). Same calls are working with Yubii Home Center mobile app.

 

@Raf.Kal

I am wondering is it working for you while using Yubii Home mobile app.?

Edited January 24 by cag014

[Sankotronic 2,370]

Hi all,

 

there is no support for push messages in Yubii app. As soon as a message is received on your mobile telephone, if you tap it to see complete message it will start Yubii app and you will not be able to see it anymore. Fibaro added Notifications option in Yubii app does not have anything to do with the push messages send by user code from either scenes or quick apps. Actually I do not see any benefit of having this since they never explained how can be used.

 

On iPhone if you want to see complete push message then to see entire message you need to tap and keep it pressed until it show up complete message. Don't know how is on Android mobile phones since I never liked anything related to it and in my opinion is complete crap even hardware can be one of the best. I did once had Android phone and it was always just updating and updating and then more updating until it get so slow and became unusable. After some time its battery get inflated and not possible to charge so I just throw it in the garbage for electronics (trying to be environment and ecology aware)   

 

Sorry if I missed the point, do not throw stones at me  

 

BTW I use in my QA what Fibaro suggested and it is working flawlessly for both push messages and e-mails including title for e-mails. Good work Fibaro and thank you! 👍 ❤️

Edited January 29 by Sankotronic

[cag014 731]

Global Market Share: Android vs. iPhone

Region	Android	iPhone (iOS)
Worldwide	70–75%	24–30%
United States	40–42%	58–59%
Active Devices	3+ billion	1+ billion

36 minutes ago, Sankotronic said:

As soon as a message is received on your mobile telephone, if you tap it to see complete message

You can open and read the message by tapping the down‑arrow on the notification. It works almost the same way as on an iPhone.

 

What I said that Yubii Home application doesn't receive push notification at all while Yubii Home Center app works fine. So the issue is in Yubii Home android app.

[SmartHomeEddy 1,006]

52 minutes ago, Sankotronic said:

Fibaro added Notifications option in Yubii app does not have anything to do with the push messages send by user code from either scenes or quick apps. Actually I do not see any benefit of having this since they never explained how can be used.

 

Well. I use the notifications to tell the user of my quickapp there is a new version. 

[Sankotronic 2,370]

22 minutes ago, cag014 said:

Region    Android                 iPhone (iOS)    Worldwide    70–75% 24–30%   United States    40–42% 58–59%   Active Devices    3+ billion 1+ billion  

Hi @cag014,

 

I wrote "in my opinion Android is crap", which means that I think is crap, not entire world, so let us stay at this point. I could mention that I have some friends that use Android phones, but they complain that Android software is a crap 💩, not phones, since some of the hardware is really excellent, just unfortunately running that Android crap  

 

To be honest it is not much different with iPhones and their software is becoming more and more crappy

 

Still when I compare software Android and iOS, iOS seems still a bit better and more safe than Android. If you don't believe me you can search how iOS handle payments and how Adroid does the same thing.

 

Regarding mobile apps, I use Yubii Home:

 

and what I wrote about push messages on iPhone is valid for this app.

I do not use Yubii Home Center:

 

since what I understood this app was made with backward compatibility with HC2 and for me it never worked neither with my HC2 (always dropping out) neither with HC3 due to some different approach to show quick apps (actually not show master quick app of some types).

 

I hope that @m.roszak can maybe once and for all explain difference between this two apps and which one is recommended to use with HC3 and Yubii gateways?

 

33 minutes ago, SmartHomeEddy said:

 

Well. I use the notifications to tell the user of my quickapp there is a new version. 

 

That is interesting. I know there is mention of this type of notifications in old and outdated developer "manual" that was not very useful to me. If you can find little time to give your code example how to send this type of notifications? It is very possible that I didn't properly understand that "manual" and was doing something wrong.

 

Thank you!

[m.roszak 765]

Yubii Home Center is compatible with HC2/HCL hubs, in maintanace mode mostly.

Yubii Home (the new one) is compatible with all new hubs - HC3, HC3L, Yubii Home and Yubii Home Pro, this one is for sure the best one to use with the new hubs as all the new featurs comes to this one. 

[cag014 731]

5 hours ago, m.roszak said:

Yubii Home Center is compatible with HC2/HCL hubs, in maintanace mode mostly.

Yubii Home (the new one) is compatible with all new hubs - HC3, HC3L, Yubii Home and Yubii Home Pro, this one is for sure the best one to use with the new hubs as all the new featurs comes to this one. 

Yubii Home does not receive push notification on Android phone, any update on that?

[m.roszak 765]

Very strange, no reports like that from the field and it works without any issues on my Android phone.

Please PM me with some details (phone model, andorid version, how you are triggering the push messeges) - we will check it out :)

[cag014 731]

1 hour ago, m.roszak said:

Very strange, no reports like that from the field and it works without any issues on my Android phone.

Please PM me with some details (phone model, andorid version, how you are triggering the push messeges) - we will check it out

I’ve identified the cause of the issue. I had to delete the registered mobile ID from the Access Panel on all my hubs and register it again. After doing that, everything started working normally.

What I’m trying to understand is how it was still possible to access the hub remotely, while the registered mobile ID itself wasn’t functioning. It seems like remote access and mobile‑ID authentication were out of sync, and I’m wondering how that situation can occur.

 

I also tested Geofence afterwards, and it is still not working.

 

 

Edited January 31 by cag014