How is the ACK handled?

---

Hey,

I started again playing with a relay node. At the moment it’s only on desk, but in future I want to integrate into my wall switches. But I wondered how pimatic is handling the ACK or better the case of getting no ACK when it is requested.
As far as I understood in the mysensors.coffee on line 1470 and following the MySensorsSwitch is requesting an ACK.
In my setup I have a few lost messages due to problems with signing. So when the message is dropped during transport pimatic gui shouldn’t switch it’s state, right? But it does in my case. The message is not received properly (and relay is not switched) but pimatic shows it’s done. To resend the on command I have to first switch off in pimatic. Is that the wanted behaviour?

+1 same here

@Anduril This is a really good question, I am also looking for some answers. I would also prefer that the ACK is somehow handled by pimatic. And also for a way to toggle a switch without actually sending the command, i.e., resetting it to the correct state.

In my installation pimatic is toggling the switch, even if the message is “failed”.

this is could do together with this:

https://forum.pimatic.org/topic/1336/mysensors-gw-ack-failed-resend/

I had anouther litte bit deeper look at the code. I have to say that I don’t know anything about js or coffee, but I used to programm a little with basic and c++, so I can see some logic structures.
Maybe @sweebee or @Oitzu can help, as they made huge improvements to the plugin with ethernet support.
Is the line 1503 changeStateTo: (state) -> the event that is invoked when switching the state in gui? If I understand it right then it will send the message to mysensors in line 1514 and change state of the switch in line 1515. Wouldn’t it be better to leave line 1515? So it just sends out the data and when ack comes in it will be received by the plugin and switch will be changed to the real state.

https://github.com/DheerajKhajuria/pimatic-mysensors/blob/development/MySensors.coffee#L1503

@Anduril I thought the same, but when you switch in in the gui, the switch will always change when you click it. If you refresh the gui it goes back again, but there must be a way to leave the switch off when switching on. If you know what i mean.

@sweebee yeah I know what you mean, what about switching it back after you clicked it by code and wait for the ACK to switch it to the new state? Would look a little strange at first because your switch would be flickering, but maybe we can find a way to disable gui update later.

or can we somehow trigger a refresh of the gui after a specific time?
Example for switching from off to on: Then we could leave out line 1515 and when switching the gui shows on. If the ACK comes in we will have the correct on state without noticing anything in gui. If no ACK comes we force a refresh of the gui and it will show off again.
Maybe thats more a question to the core @developer than for plugin defs…

@sweebee don’t know if you read this, but there was an topic about how to update the ui without reloading the page. Maybe this can be used in our case too: https://forum.pimatic.org/topic/2326/solved-refresh-value-on-the-ui