changed behaviour of fibaro.call()

[NLWaard 12]

I recently updated my Fibaro 3 system from version 5.161.15 to 170.16, and a day later to 5.171.13 (beta). Unfortunately, I am not sure which version introduced the following issue:

In one of my scenes, I use a table of devices to switch off the lights by calling fibaro.call(devices, 'turnOff'). This worked fine before the updates. However, after the updates, running the scene now results in the error: "String expected, got table." or something like that.

 

This is puzzling, as the call uses a number, string or table.

To work around this issue, I now loop through the table and send multiple fibaro.call commands, but this is not ideal.

 

 

Please login or register to see this code.

 

The workaround is simple, but not ideal...

Please login or register to see this code.

 

 

[Joep 200]

This is a breaking change. I'm curious what FIBARO says about this @K.Drozynski 

[Neo Andersson 230]

 I am running on 5.170.16 and tried it in quickapp and there this works 

Please login or register to see this code.

 

Edited December 1, 2024 by Neo Andersson

[jgab 2,641]

14 hours ago, Neo Andersson said:

 I am running on 5.170.16 and tried it in quickapp and there this works 

Please login or register to see this code.

 

Did you try both Scene and QA?

[Neo Andersson 230]

8 minutes ago, jgab said:

Did you try both Scene and QA?

Did not try scene..Evening i can try

[jgab 2,641]

So for me it works both in scenes and QAs, on FW 5.171.13

[jgab 2,641]

So, it seems that the bug is caused by the extra argument to turnOff - 

Please login or register to see this code.

Without that it works with a table...

(usually turnOff doesn't take an argument) 

[tinman 1,070]

yeah there is something strange in 5.171.13, in my case scenes simply does nothing after 20-30min HC runtime, no trigger, no action, no errors, while QAs stopped to report tasks status or UI updates (definitely not memory issue). I had to downgrade my prod HC3.

[Neo Andersson 230]

probably this is also a reason why that FW had been withdrawn. It is no more available..

 

 

Please login or register to see this image.

/monthly_2024_12/image.png.ce5b3fadf10a96ffbee398429ccd54c1.png" />

Edited December 2, 2024 by Neo Andersson

[NLWaard 12]

Hotfix 5.171.15 fixed this.
I had this problem in both QuickApps and Scenes.

 

@jGab, you are right. The extra info 'sender' is for internal QuickApps (so that I know where the call is coming from) and not for devices.

Even though it now works as it did before these updates, I will remove this extra info when the call is to devices.

 

Thanks...

 

Edited December 4, 2024 by NLWaard