Today's fix for the bad beta fixed nothing!

[petro_cz 31]

So I installed the patched Update 5.171 Beta today and no change for the better! The scenes just don't work the system reboots and freezes! And I was hoping for a quick fix. I understand that beta can have bugs, but this is a fatal flaw and I don't understand why no one is testing it. 

[Tony270570 107]

I'm must admit it was not the best release of the year

From my side mqtt and custom events have stopped working, it was enough for a rollback.

[petro_cz 31]

7 minutes ago, Tony270570 said:

 

So I was expecting a quick fix, now I'm on the stable previous version, I just lost my data history, take it easy, but my heating is working:))))))

Edited December 3, 2024 by petro_cz

[Tony270570 107]

35 minutes ago, petro_cz said:

but my heating is working:))))))

So everything is ok 🥶☺️ 

 

[trob 7]

14 hours ago, petro_cz said:

So I installed the patched Update 5.171 Beta today and no change for the better! The scenes just don't work the system reboots and freezes! And I was hoping for a quick fix. I understand that beta can have bugs, but this is a fatal flaw and I don't understand why no one is testing it. 

Hi,
It would be helpful for us if you could provide some more details:
1) did all of your scenes stopped working? Or only some specific ones?

2) when does your system reboot? is it connected with viewing/executing scenes? Or perhaps doing some other specific action? Or does it seem just random?
3) what do you mean by "freeze"? Perhaps its connected with rebooting problem?

It might be something specific to your system, we did not take under consideration in our tests. If you would be willing to enable "6. Access -> Remote Access -> Support Access" we would gladly look at your system logs and analyze whats wrong.

[Raf.Kal 2]

15 hours ago, Tony270570 said:

I'm must admit it was not the best release of the year

From my side mqtt and custom events have stopped working, it was enough for a rollback.

Hello, I would like to take a look at the problem with MQTT. Could you please provide more data with some part of the code explaining how you use the MQTT protocol: subscribe, publish, or both? Don't hesitate to contact me via Private Message.

[marczu_83 29]

15 godzin temu, Tony270570 napisał:

I'm must admit it was not the best release of the year

From my side mqtt and custom events have stopped working, it was enough for a rollback.

MQTT works fine for me

[Tony270570 107]

Hi @Raf.Kal yes sure, here is a simple one : 

Please login or register to see this code.

 

3 minutes ago, marczu_83 said:

MQTT works fine for me

Am I the only one in this world having this issue ?

When I saw that I was having this issue I didn't spent to much time before to rollback, but in the mean time I saw like I wrote in another thread that all the mqtt were not affected. 

I'll not be able to update to 5.171.15 again during the day, but I'll give another try this evening, just in case something went bad yesterday.

[trob 7]

15 hours ago, Tony270570 said:

I'm must admit it was not the best release of the year

From my side mqtt and custom events have stopped working, it was enough for a rollback.

Could you please also specify what are the symptoms of custom events not working? Does emitting not work for you? Or maybe using it as trigger? Do you see any errors in scene/quickapp logs?

[Tony270570 107]

Hi @trob, the communication was refused. end of the process

 

 

[Raf.Kal 2]

35 minutes ago, Tony270570 said:

Hi @Raf.Kal yes sure, here is a simple one : 

Please login or register to see this code.

 

Am I the only one in this world having this issue ?

When I saw that I was having this issue I didn't spent to much time before to rollback, but in the mean time I saw like I wrote in another thread that all the mqtt were not affected. 

I'll not be able to update to 5.171.15 again during the day, but I'll give another try this evening, just in case something went bad yesterday.

 

Could you please change the way you pass QoS in publish method like below and let here know if it will solve the problem just for now?

Please login or register to see this code.

Edited December 4, 2024 by Raf.Kal

[Tony270570 107]

@Raf.Kal I've just reinstalled 5.171.15. I've amended the code with your suggestion but it doesn't makes the trick. 

Please login or register to see this code.

Let me know if you require something more.

[Raf.Kal 2]

@Tony270570 Oh, I see that it even failed to connect in the first place. In such case, please switch remote support access on, so that we can try to check the problem on your HC.

[Tony270570 107]

The HC3 is currently restoring the stable version.

Please give me about 1 hour and I'll reupdate to the beta again and give you the access.

Thank you @Raf.Kal

[Tony270570 107]

Hi @Raf.Kal key is yours you can connect. Thanks !

[petro_cz 31]

7 hours ago, trob said:

 

The device after reboot works for about 5 minutes but very slowly, then it can not control a single scene, can not switch the profile home/xxx, does not work temperature program, only works by turning the device on and off, but here often there are hiccups and soft reboots (for a minute the gate is unavailable, the green LED goes out and only 3 right are red) the original fibaro button does not work, the button does not even flash green that communicates. Nothing changed after the update, I was forced to upload the previous version. So I lost all the history data but the heater was not working and that was the priority. 

 

I can provide you with my backup and try to install it if it helps others, I have no problem with it

Edited December 4, 2024 by petro_cz

[Tony270570 107]

I would like to thanks @trob and @Raf.Kal for the time spent today analysing the source of my issue with mqtt and proposing solutions.

It was due to anupdate of the mqtt library which in certain case with old style code like the one I was using might cause some issues, explaining why not all my mqtt QAs were impacte, as I was not always using the same pattern.

I talked in another thread about custom event issues, but nothing to have with that, it was also a indirect impact of the mqtt topic.

Thanks again guys for your professionalism

 

 

[jgab 2,641]

1 hour ago, Tony270570 said:

I would like to thanks @trob and @Raf.Kal for the time spent today analysing the source of my issue with mqtt and proposing solutions.

It was due to anupdate of the mqtt library which in certain case with old style code like the one I was using might cause some issues, explaining why not all my mqtt QAs were impacte, as I was not always using the same pattern.

I talked in another thread about custom event issues, but nothing to have with that, it was also a indirect impact of the mqtt topic.

Thanks again guys for your professionalism

 

 

Could you elaborate what needed to be changed in your code to adhere to the "new style"... ?

[Tony270570 107]

Hi @jgab old/new just a way to popularize

 

I've change , well it has been suggested by the support to change :

from

self.client:publish(topic, message)
to:
self.client:publish(topic, message, {qos = mqtt.QoS.AT_LEAST_ONCE}) 

 

and I've removed lastWill object from connect options

 

And i just found a new problem that i don't understand for now.

ok just found example of change required :

 

FROM :

function QuickApp:DeviceIdentify()

    self.client:publish("fp2/identify", "identify"})

end

TO :

 

function QuickApp:DeviceIdentify()

    self.client:publish("fp2/identify", "identify", {qos=1})

end

 

Same issue same fix

 

Don't know if the MQTT library that has been updated is to upgrade to V5, just an assumption, no details.

 

Hope that it clarify a bit.

Edited December 4, 2024 by Tony270570

[jcichon01 13]

12 godzin temu, Tony270570 napisał:

Hi @Raf.Kal yes sure, here is a simple one : 

Please login or register to see this code.

 

Am I the only one in this world having this issue ?

When I saw that I was having this issue I didn't spent to much time before to rollback, but in the mean time I saw like I wrote in another thread that all the mqtt were not affected. 

I'll not be able to update to 5.171.15 again during the day, but I'll give another try this evening, just in case something went bad yesterday.

no, you are not. Same here.