Domoticz

Do not upgrade to firmware 3.1b
This create issues for pairing devices and also for devices that you power off/on

If you done it alreday, do not downgrade

So you have the same problem, which version do you think is the most stable?

tjabas wrote: ↑Tuesday 21 January 2020 17:55 So you have the same problem, which version do you think is the most stable?

It is not a question of stability. For some 3.1b will work perectly for some other they will have some strange behaviour while doing electrical power Off/On of devices

So for me my recommendation is do not upgrade to 3.1b. If you have already done, let see if you fall into the issues

Thanks for informing, I was about to upgrade!
Is it an idea to also inform about this problem on the Zigate firmware download page?

Firmware 3.1c has been released and solved the issue of 3.1b

Thanks for the information

Hmm, didnt see that new firmware, only 3.1b

tjabas wrote: ↑Wednesday 22 January 2020 18:04 Hmm, didnt see that new firmware, only 3.1b

https://github.com/fairecasoimeme/ZiGat ... /tag/v3.1c

thanks, i looked in the wrong place

Hi,
after 3.1c update the status for offline devices does not change, he remain online in domoticz. The value "HaveTimeout" does not change. In domoticz log display:
2020-01-27 14:20:56.243 (Zigate) Receive an APS Nck from 3500, let's put the device in default/not reachable.

pfloryann wrote: ↑Monday 27 January 2020 13:22 Hi,
after 3.1c update the status for offline devices does not change, he remain online in domoticz. The value "HaveTimeout" does not change. In domoticz log display:
2020-01-27 14:20:56.243 (Zigate) Receive an APS Nck from 3500, let's put the device in default/not reachable.

I don't understand the issue ; could you clarify ?

with old firmware version when a device became unavailable for some reason in domoticz it was displayed that the device is offline because it did not respond at poll. This occurs because the device "HaveTimeOut" parameter from domoticz changes its value from false to true and now remain always false even if the device is offline.

pfloryann wrote: ↑Monday 27 January 2020 20:28 with old firmware version when a device became unavailable for some reason in domoticz it was displayed that the device is offline because it did not respond at poll. This occurs because the device "HaveTimeOut" parameter from domoticz changes its value from false to true and now remain always false even if the device is offline.

And that is still true and had nothing to do with the Firmware version

in this case can be from domoticz?

Please do provide logs with information from that I might help

For example i switch on my offline device(Bec Ikea Dormitor-is a bulb) from domoticz, the widget device is changing status to ON as if the command was sent with success. The same for switch off.

Zigate respond with message "(Zigate) Receive an APS Nck from 3500, let's put the device in default/not reachable" but domoticz do nothing for to put device in to offline.


2020-01-28 20:57:11.826 (Zigate) UpdateDevice - (Bec Ikea Dormitor) 1:On
2020-01-28 20:57:11.819 Status: User: florian initiated a switch command (98/Bec Ikea Dormitor/On)
2020-01-28 20:57:18.304 (Zigate) Receive an APS Nck from 3500, let's put the device in default/not reachable
2020-01-28 20:57:36.819 (Zigate) UpdateDevice - (Bec Ikea Dormitor) 0:Off
2020-01-28 20:57:36.770 Status: User: florian initiated a switch command (98/Bec Ikea Dormitor/Off)
2020-01-28 20:57:43.293 (Zigate) Receive an APS Nck from 3500, let's put the device in default/not reachable

Please update to the latest version of the Plugin

Yes after beta plugin update works, only on beta.
It was a problem between plugin and domoticz?

Thank you!

pfloryann wrote: ↑Wednesday 29 January 2020 7:42 Yes after beta plugin update works, only on beta.
It was a problem between plugin and domoticz?

Thank you!

Problem was on plugin side

With last beta plugin and domoticz 411670 I think something is not working properly because some devices become offline after a few minutes after last use or last polling but not always and become online after a period but
these devices are always connected. I think it should go offline after a longer period of inactivity and only when not responding to polling.