New Elero TransmitterStick Binding

Hi Stefan

Thanks for your hint. I have taken a close look at the logging. The stick is initialized correctly. However, I get no response from the stick for AA024A0A. Although I have programmed the shutter on the sixth channel. With the buttons on the stick I can control the shutter. The channel I have also manually recorded in openhab.

Is your stick working correctly now? Have you programmed the shutter again on the stick?

Hi Clivaz

You’re welcome. That’s wierd actually

Yes I’ve done a full re-config of the stick and removed everything from openHAB.
After successful finish of the stick pairing to the receiving Elero Device.
I’ve continued with openHAB config and it’s working now.

Bridge (i.e. Stick itself) config

Channel config

The following is an excerpt from the log, command was issued using mobile phone app.

2022-06-13 13:43:46.461 [hab.event.ItemCommandEvent] - Item 'EleroChannel_Control' received command DOWN
2022-06-13 13:43:46.469 [nt.ItemStatePredictedEvent] - Item 'EleroChannel_Control' predicted to become DOWN
2022-06-13 13:43:46.473 [vent.ItemStateChangedEvent] - Item 'EleroChannel_Control' changed from 0 to 100
2022-06-13 13:43:46.573 [vent.ItemStateChangedEvent] - Item 'EleroChannel_Status' changed from TOP to MOVING_DOWN
2022-06-13 13:43:46.574 [vent.ItemStateChangedEvent] - Item 'EleroChannel_Control' changed from 100 to 50
2022-06-13 13:43:49.625 [hab.event.ItemCommandEvent] - Item 'EleroChannel_Control' received command STOP
2022-06-13 13:43:49.726 [vent.ItemStateChangedEvent] - Item 'EleroChannel_Status' changed from MOVING_DOWN to STOPPED
2022-06-13 13:43:54.488 [hab.event.ItemCommandEvent] - Item 'EleroChannel_Control' received command UP
2022-06-13 13:43:54.489 [nt.ItemStatePredictedEvent] - Item 'EleroChannel_Control' predicted to become UP
2022-06-13 13:43:54.490 [vent.ItemStateChangedEvent] - Item 'EleroChannel_Control' changed from 50 to 0
2022-06-13 13:43:54.622 [vent.ItemStateChangedEvent] - Item 'EleroChannel_Status' changed from STOPPED to MOVING_UP
2022-06-13 13:43:54.623 [vent.ItemStateChangedEvent] - Item 'EleroChannel_Control' changed from 0 to 50


Thanks again for the help. I have now found the problem. The USB stick was always plugged into a USB 3.0. The stick only works on a normal USB. Now everything works and I can continue with the HABPanel.

@Lolipop - what a stupid thing but yes. I’m glad your able to use it now :slight_smile:

Hi Peter, did you find the reason for the warning “response does not match command channels. Skipping response”? I have the same warning, but elero shutters works fine.

Hi Barnecke, no solution yet.
I changed my setup to use additional variables holding an “expected” state which works as long as the marquees are controlled via openHAB. If someone uses the elero remote, these expected_state variables are out of sync and thing behave badly.
I’d be happy to help solving the problem if I can

Hi guys,

the stick seems to have a tendency to not follow its own protocol. If you look at the log lines, the command that is send to the stick is AA054C000240C3, which means it is an EASY_SEND to channel 2, but the response the stick send is AA054D00000004, which means it is an EASY_ACK for no channels at all (the channel bits are 0000) and state NO_INFORMATION.

2022-05-14 16:49:39.643 [DEBUG] [tick.internal.stick.SerialConnection] - Writing packet to stick: AA054C000240C3
2022-05-14 16:49:39.645 [TRACE] [tick.internal.stick.SerialConnection] - Waiting 4000 ms for answer from stick...
2022-05-14 16:49:42.997 [TRACE] [tick.internal.stick.SerialConnection] - parsing input...
2022-05-14 16:49:42.999 [TRACE] [tick.internal.stick.SerialConnection] - input parsed. buffer contains 7 bytes.
2022-05-14 16:49:43.002 [TRACE] [tick.internal.stick.SerialConnection] - buffer contains bytes: AA054D00000004

This is why the answer is being discarded, hence the warning. I do not know why the stick does that, but is surely does not conform to what elero documented. This results in the fact that the shutter will not report that it is moving until the next time it is polled. It seems to get a correct answer next time, as you wrote that everything seems to work as expected.