Interest in a homeduino binding

The sounds half a day too old, can you please check with this one

Sorry for the inconvenience, but I caused it by trimming away the reference which I still had to a subType, but I forgot half of them.

The download which I put online half a day later does not contain that specific log message anymore, so it should work with that download, maybe it has something to do with some caching? Or maybe the new file downloads under the same name?

I’ll will try to add the number which you see in the dashboard also to the download-link / filename.

Note: I always store the most recent download also at the Homeduino feature request

I switched to a new note-taking, which supports markdown:

Thank you Martin, i will try it this evening.
Have a good day!

Hi Martin, it works very good! Thanks for your work!!

Many greeting Karl Heinz

got this error with the new version:

2017-02-15 18:34:24.539 [ERROR] [org.openhab.binding.homeduino       ] - FrameworkEvent ERROR - org.openhab.binding.homeduino
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.homeduino [229]
  Another singleton bundle selected: osgi.identity; osgi.identity="org.openhab.binding.homeduino"; type="osgi.bundle"; version:Version="2.1.0.201702122015"; singleton:="true"

        at org.eclipse.osgi.container.Module.start(Module.java:434)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1562)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
2017-02-15 18:34:24.565 [ERROR] [org.openhab.binding.homeduino       ] - FrameworkEvent ERROR - org.openhab.binding.homeduino
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.homeduino [230]
  Another singleton bundle selected: osgi.identity; osgi.identity="org.openhab.binding.homeduino"; type="osgi.bundle"; version:Version="2.1.0.201702122015"; singleton:="true"

        at org.eclipse.osgi.container.Module.start(Module.java:434)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1562)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
2017-02-15 18:35:00.356 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Checking Homeduino transceiver connection, thing status = ONLINE

and the shutter3 protocol seems broken:

2017-02-15 18:36:16.802 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 5108 1720 724 360 11012 0 0 0 0123232323232323223223323232323232322332233232233232232332322332323223322332233224
2017-02-15 18:36:16.813 [ERROR] [ernal.messages.HomeduinoEventMessage] - Unsupported token :'11' for protocol Protocol
2017-02-15 18:36:21.526 [DEBUG] [duino.handler.HomeduinoBridgeHandler] - Message received (HOMEDUINO_RF_EVENT): RF receive 5268 1720 724 360 10964 0 0 0 0123232323232323223223323232323232322332233232233232232332322332323223322332233224
2017-02-15 18:36:21.528 [ERROR] [ernal.messages.HomeduinoEventMessage] - Unsupported token :'11' for protocol Protocol

Previous version also seemed to give an error but protocol receiving worked fine

2017-02-15 18:41:22.815 [ERROR] [org.openhab.binding.homeduino       ] - FrameworkEvent ERROR - org.openhab.binding.homeduino
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.homeduino [229]
  Another singleton bundle selected: osgi.identity; osgi.identity="org.openhab.binding.homeduino"; type="osgi.bundle"; version:Version="2.1.0.201702122015"; singleton:="true"

        at org.eclipse.osgi.container.Module.start(Module.java:434)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1562)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
2017-02-15 18:41:22.818 [DEBUG] [org.openhab.binding.homeduino       ] - BundleEvent STARTING - org.openhab.binding.homeduino
2017-02-15 18:41:22.829 [ERROR] [org.openhab.binding.homeduino       ] - FrameworkEvent ERROR - org.openhab.binding.homeduino
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.homeduino [230]
  Another singleton bundle selected: osgi.identity; osgi.identity="org.openhab.binding.homeduino"; type="osgi.bundle"; version:Version="2.1.0.201702122015"; singleton:="true"

        at org.eclipse.osgi.container.Module.start(Module.java:434)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1562)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
2017-02-15 18:41:22.887 [DEBUG] [org.openhab.binding.homeduino       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=342, service.bundleid=235, service.scope=singleton} - org.openhab.binding.homeduino
2017-02-15 18:41:22.894 [DEBUG] [org.openhab.binding.homeduino       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={component.name=org.openhab.binding.rfxcom.internal.RFXComHandlerFactory, component.id=205, service.id=341, service.bundleid=235, service.scope=bundle} - org.openhab.binding.homeduino
2017-02-15 18:41:22.895 [DEBUG] [org.openhab.binding.homeduino       ] - BundleEvent STARTED - org.openhab.binding.homeduino
2017-02-15 18:41:22.913 [ERROR] [org.openhab.binding.homeduino       ] - FrameworkEvent ERROR - org.openhab.binding.homeduino
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.homeduino [236]
  Another singleton bundle selected: osgi.identity; osgi.identity="org.openhab.binding.homeduino"; type="osgi.bundle"; version:Version="2.1.0.201702122015"; singleton:="true"

        at org.eclipse.osgi.container.Module.start(Module.java:434)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1562)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
        at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]

Maybe its because there is a wrong configuration component.name=org.openhab.binding.rfxcom.internal.RFXComHandlerFactory. I’m in the process of working on all incorrect references to RFXCom

This makes me curious I just added an actual test to rfcontrolJS with this input and it fails there as well. I have no clue whats going on. Did you actually send and receive signals via pimatic with the current version of the software and your homeduino?

The strange thing is that the signal is converted to

3210101010101010110110010101010101011001100101100101101001011001010110011001100114

Which I actually also tested with an additional rfcontrol unit test

Than it is split up in tokens of a length 2, then at one moment it runs into the token 11 which is an invalid token, I cannot make something else of it looking at rfcontroljs implementation.

As far as i can remember, yes it worked with pimatic … but to be on safeside, i’ll install it and report back ok.
The last error doesn’t appear on earlier versions of the binding.

No, I just give up now if the mapping fails instead of returning null pointers later on :slight_smile:

The funny thing is that the receving of messages you reported back weeks ago does work with both my code and rfcontrol… However sending them seems to replicated properly by me but seems to fail as well.

Im just creating a snapshot of my test raspbian to install the pimatic and i’ll be able to check …

OK:
The pimatic log for sending:

22:01:04.783 [pimatic-homeduino] Sending Protocol: shutter3 id:65542026 channel:1 command:up all:false state:true Pin:4 Repeats:7
22:01:05.245 [pimatic-homeduino] data: "ACK"
22:01:08.276 [pimatic-homeduino] Sending Protocol: shutter3 id:65542026 channel:1 command:stop all:false state:true Pin:4 Repeats:7
22:01:08.738 [pimatic-homeduino] data: "ACK"
22:01:09.977 [pimatic-homeduino] Sending Protocol: shutter3 id:65542026 channel:1 command:down all:false state:false Pin:4 Repeats:7
22:01:10.434 [pimatic-homeduino] data: "ACK"

Homeduino #2 captures:

ACK
RF receive 5272 1604 376 744 10960 0 0 0 0123232332323232322332232323232323322332323232232323322332232323322323233223232334
RF receive 5264 1612 376 748 10960 0 0 0 0123232332323232322332232323232323322332323232232323322332232323322332233223322334
RF receive 5268 1608 376 748 10960 0 0 0 0123232332323232322332232323232323322332323232232323322332232323322323323223233234

Shutters respond normally.
I’m trying to see if there is a way for me to see exactly what command is sent to homeduino.

So the first one is sending from pimatic homeduino and leads to the messages as displayed in #2?

The messages in #2 convert to up / undef / down in the homeduino binding.

Correct … All commands are sequence UP, STOP (UNDEF), DOWN
Homeduino #2 is connected to my PC for the purpose of sniffing the 433 trafic. I didn’t test the conversion on the homeduino binding.

Here is also the cleaned up capture of communication between pimatic and homeduino sending UP, STOP and DOWN commands

Host   --> RF send 4 7  366 736 1600 5204 10896 0 0 0 3201010110101010100110010101010101100110101010010101100110010101100101011001010114<LF>

Device --> ACK<CR><LF>

Host   --> RF send 4 7  366 736 1600 5204 10896 0 0 0 3201010110101010100110010101010101100110101010010101100110010101100110011001100114<LF>

Device --> ACK<CR><LF>

Host   --> RF send 4 7  366 736 1600 5204 10896 0 0 0 3201010110101010100110010101010101100110101010010101100110010101100101101001011014<LF>

Device --> ACK<CR><LF>

and in the pure capture form

Host   --> R (082) F (070) <SPACE> (032) s (115) e (101) n (110) d (100) <SPACE> (032) 4 (052) <SPACE> (032) 7 (055) <SPACE> (032) <SPACE> (032) 3 (051) 6 (054) 6 (054) <SPACE> (032) 7 (055) 3 (051) 6 (054) <SPACE> (032) 1 (049) 6 (054) 0 (048) 0 (048) <SPACE> (032) 5 (053) 2 (050) 0 (048) 4 (052) <SPACE> (032) 1 (049)

Host   --> 0 (048) 8 (056) 9 (057) 6 (054) <SPACE> (032) 0 (048) <SPACE> (032) 0 (048) <SPACE> (032) 0 (048) <SPACE> (032) 3 (051) 2 (050) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 0 (048) 1 (049) 1 (049)

Host   --> 0 (048) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 1 (049) 0 (048) 0 (048) 1 (049) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 1 (049)

Host   --> 0 (048) 0 (048) 1 (049) 1 (049) 0 (048) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 1 (049) 0 (048) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 1 (049) 0 (048) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 1 (049) 4 (052) <LF> (010)

Device --> A (065) C (067) K (075) <CR> (013) <LF> (010)

Host   --> R (082) F (070) <SPACE> (032) s (115) e (101) n (110) d (100) <SPACE> (032) 4 (052) <SPACE> (032) 7 (055) <SPACE> (032) <SPACE> (032) 3 (051) 6 (054) 6 (054) <SPACE> (032) 7 (055) 3 (051) 6 (054) <SPACE> (032) 1 (049) 6 (054) 0 (048) 0 (048) <SPACE> (032) 5 (053) 2 (050) 0 (048) 4 (052) <SPACE> (032) 1 (049)

Host   --> 0 (048) 8 (056) 9 (057) 6 (054) <SPACE> (032) 0 (048) <SPACE> (032) 0 (048) <SPACE> (032) 0 (048) <SPACE> (032) 3 (051) 2 (050) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 0 (048) 1 (049) 1 (049)

Host   --> 0 (048) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 1 (049) 0 (048) 0 (048) 1 (049) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 1 (049)

Host   --> 0 (048) 0 (048) 1 (049) 1 (049) 0 (048) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 1 (049) 0 (048) 0 (048) 1 (049) 1 (049) 0 (048) 0 (048) 1 (049) 1 (049) 0 (048) 0 (048) 1 (049) 1 (049) 0 (048) 0 (048) 1 (049) 1 (049) 4 (052) <LF> (010)

Device --> A (065) C (067) K (075) <CR> (013) <LF> (010)

Host   --> R (082) F (070) <SPACE> (032) s (115) e (101) n (110) d (100) <SPACE> (032) 4 (052) <SPACE> (032) 7 (055) <SPACE> (032) <SPACE> (032) 3 (051) 6 (054) 6 (054) <SPACE> (032) 7 (055) 3 (051) 6 (054) <SPACE> (032) 1 (049) 6 (054) 0 (048) 0 (048) <SPACE> (032) 5 (053) 2 (050) 0 (048) 4 (052) <SPACE> (032) 1 (049)

Host   --> 0 (048) 8 (056) 9 (057) 6 (054) <SPACE> (032) 0 (048) <SPACE> (032) 0 (048) <SPACE> (032) 0 (048) <SPACE> (032) 3 (051) 2 (050) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 0 (048) 1 (049) 1 (049)

Host   --> 0 (048) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 1 (049) 0 (048) 0 (048) 1 (049) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 1 (049)

Host   --> 0 (048) 0 (048) 1 (049) 1 (049) 0 (048) 0 (048) 1 (049) 0 (048) 1 (049) 0 (048) 1 (049) 1 (049) 0 (048) 0 (048) 1 (049) 0 (048) 1 (049) 1 (049) 0 (048) 1 (049) 0 (048) 0 (048) 1 (049) 0 (048) 1 (049) 1 (049) 0 (048) 1 (049) 4 (052) <LF> (010)

Device --> A (065) C (067) K (075) <CR> (013) <LF> (010)

If you send those signals from pimatic to OH2 and vice versa does that work?

A new version with support for pir2 has just been published:

2.1.0.201702152209

Also the logging should be way better if you get into the initialization problems again please provide me with the logging so I can resolve it. I also scanned for RFXCom references and they should now be gone except for references about the origin of some files.

I’m afraid i’ cant test that easily - only one rpi3 (EDIT:ok maybe two different ports)
But i can try and figure something out.
What do you hope to accomplish?
What would you like me to test?

Good question, I want to make sure that I’m actually compatible with the code of the rfcontrol (used by pimatic). And I hope the result to be, that I’m (because of that) compatible with your setup.

The problem is that my unit tests tell me that I am compatible but every time it’s just a little bit different in practice than I hoped it to be.

What is the type and brand of your remote and is it affordable?

You’ve got PM…

Here si the comparison of code what is sent via Pimatic and OH2

The way i see it is that everythin is the same with exception of the second to last bit (before 4) - OH sends 0, Pimatic 1

UP
OH2
RF send 4 3 366 736 1600 5204 10896 0 0 0 3201010110101010100110010101010101100110101010010101100110010101100101011001010104
PIMATIC
RF send 4 7 366 736 1600 5204 10896 0 0 0 3201010110101010100110010101010101100110101010010101100110010101100101011001010114

STOP
OH2
RF send 4 3 366 736 1600 5204 10896 0 0 0 3201010110101010100110010101010101100110101010010101100110010101100110011001100104
PIMATIC
RF send 4 7 366 736 1600 5204 10896 0 0 0 3201010110101010100110010101010101100110101010010101100110010101100110011001100114

DOWN
OH2
RF send 4 3 366 736 1600 5204 10896 0 0 0 3201010110101010100110010101010101100110101010010101100110010101100101101001011004
PIMATIC
RF send 4 7 366 736 1600 5204 10896 0 0 0 3201010110101010100110010101010101100110101010010101100110010101100101101001011014

Would you prefer me to increase the number of transmits or should I make it configurable?

I tried increasing the number to 7 to see if it would work but it didn’t help.
Making it configurable would be a great thing, however we should test to see that this isn’t a per protocol setting.
I’m now trying to see what pimatic thinks of codes sent by OH2 … can it decode them …

EDIT:
Here’s the log:

00:00:43.695 [pimatic-homeduino] shutter3:  { id: 65542026, channel: 1, command: 'up' }
00:00:52.205 [pimatic-homeduino] data: "RF receive 5244 1628 372 748 10984 0 0 0 0123232332323232322332232323232323322332323232232323322332232323322332233223322324"
00:00:52.210 [pimatic-homeduino] received: [ 372, 748, 1628, 5244, 10984 ] 3201010110101010100110010101010101100110101010010101100110010101100110011001100104
00:00:52.218 [pimatic-homeduino] shutter3:  { id: 65542026, channel: 1, command: 'stop' }
00:01:01.660 [pimatic-homeduino] data: "RF receive 5244 1624 372 748 10984 0 0 0 0123232332323232322332232323232323322332323232232323322332232323322323323223233224"
00:01:01.664 [pimatic-homeduino] received: [ 372, 748, 1624, 5244, 10984 ] 3201010110101010100110010101010101100110101010010101100110010101100101101001011004
00:01:01.675 [pimatic-homeduino] shutter3:  { id: 65542026, channel: 1, command: 'down' }

Pimatic seems to decode them OK, but shutters don’t react.
However changing the second to last 0->1 makes everything work … even with 3 repeats

New version with 14 in the end and repeat = 7 (not yet configurable)

org.openhab.binding.homeduino-2.1.0-SNAPSHOT-201702152258.jar.zip