Timeout, no ACK received

[vladulkom]

Hello,

I have implemented this new version into my setup. It was working fine (very nice work btw), once I pushed to production "for my wife :)" I have discovered the wrong status for one of the dimmer. Wall switches are working fine, only can not read the actor status - Timeout, no ACK received, and therefore no mqtt message is sent. I tried to revert back to C++ version, same behavior. Any suggestion?

Feb 04 00:19:37 openhabian xcomfortd-go[31727]: 2021/02/04 00:19:37 MQTT message; topic: 'xcomfort/3/set/swi tch', message: 'true' Feb 04 00:19:38 openhabian xcomfortd-go[31727]: 2021/02/04 00:19:38 TX command failed, retrying (1/2): Timeo ut, no ACK received Feb 04 00:19:39 openhabian xcomfortd-go[31727]: 2021/02/04 00:19:39 TX command failed, retrying (2/2): Timeo ut, no ACK received Feb 04 00:19:41 openhabian xcomfortd-go[31727]: 2021/02/04 00:19:41 WARNING: command for datapoint 3 failed, state now unknown: Timeout, no ACK received Feb 04 00:19:41 openhabian xcomfortd-go[31727]: 2021/02/04 00:19:41 MQTT message; topic: 'xcomfort/3/set/swi tch', message: 'false'

Thank you, V.

[karloygard]

Very cool that you have this up and running in openhab!

The error message Timeout, no ACK received comes from the USB stick itself. Put simply, it means that the USB stick did not receive a response from the actuator. This either means that the xcomfort routing is wrong, or that the actuator is too far away from the USB stick and that packets are lost.

This should be resolved by running the MRF tool, and re-reading reception quality + recalculate routing (I forget the actual terms used). If you have no powerline/routing devices between the USB stick and the actuator, you may have to put one in, or move the USB stick closer to the actuator.

For older actuators the latter is especially true, since old status messages are not routed. If these actuators are switched by e.g. light switches, the USB stick may never see the status message if it's too far away from the actuator, causing your view of the world to go out of sync (depending on your use case, this may not be a showstopper). Newer actuators support extended status messages which are routed, and do not suffer this issue.