Fibaroextra

[Neo Andersson 186]

Hi @jgab, i am getting this warning in fibaroExtra

[13.11.2023] [11:49:46] [WARNING] [QUICKAPP413]: Variable  TPUBSUB not found

??

[jgab 2,057]

9 hours ago, Neo Andersson said:

Hi @jgab, i am getting this warning in fibaroExtra

[13.11.2023] [11:49:46] [WARNING] [QUICKAPP413]: Variable  TPUBSUB not found

??

Are you using the pubsub feature? 

In general it's just that code that tries to retrieve a quickAppVariable to see if there are any subscriptions.

Unfortunately, fibaro's self:getVariable logs a warning if one tries to get a non existent variable.

The Lua paradigm would be to return nil - now they log a warning and return an empty string "" 😕 

[Neo Andersson 186]

1 hour ago, jgab said:

Are you using the pubsub feature? 

In general it's just that code that tries to retrieve a quickAppVariable to see if there are any subscriptions.

Unfortunately, fibaro's self:getVariable logs a warning if one tries to get a non existent variable.

The Lua paradigm would be to return nil - now they log a warning and return an empty string "" 😕 

I am not using it, and i havent ever got this message so far. After update it started to emerge

[jgab 2,057]

7 hours ago, Neo Andersson said:

I am not using it, and i havent ever got this message so far. After update it started to emerge

Are you using the whole fibaroExtra.lua file or the module files?

version of fibaroExtra?

[Neo Andersson 186]

Jan i can't recall it as it was at my customers house, when we were solving there some other issues. There is multiple Qas running using fibaroExtra, an i forgot to mark which one, and which version. But never mind, if this is a harmlass warning anyway i will just let it be

If it emergs again seomwhere, i will make notes about version. So far thanks. / i hope it is a harmless warning

 

[gurpal2000 1]

On 11/14/2023 at 9:01 AM, Neo Andersson said:

Jan i can't recall it as it was at my customers house, when we were solving there some other issues. There is multiple Qas running using fibaroExtra, an i forgot to mark which one, and which version. But never mind, if this is a harmlass warning anyway i will just let it be

If it emergs again seomwhere, i will make notes about version. So far thanks. / i hope it is a harmless warning

 

 

Can't the variable just be defined somewhere to get rid of the warning though? If i give it an arbitrary value does something break?