Shutter protocols limited to 4 Channels (especially shutter4)

---

Hi all,
I decide to switch from Jarolift rf shutter controllers to 3t or Rohrmotor24.

As I learned the rohrmotor24 device should work with shutter4 protocol, see here. In an other thread I found that the rohrmotor24 and 3t should works with the same protocol.

My question now is if the protocol is limited to 1-4/all channels or is it possible to have 8 channels? I ask, because on the supplier sides are remotes which can provide up to 15 channels.

I don’t know the answer of your question, but please let me/us know if the switch with you will buy work.
I search also for a solution to cotroll my shutters.

said in Shutter protocols limited to 4 Channels (especially shutter4):

My question now is if the protocol is limited to 1-4/all channels or is it possible to have 8 channels? I ask, because on the supplier sides are remotes which can provide up to 15 channels.

The shutter4 protocol uses 3 bits for the channel decoding where 000 is interpreted as “all channels”. So, it can handle 7 channels. However, note, the protocol implementation contains a bug which causes the received channel to be always 0 --> ‘all’. I am suprised nobody recognized this so far. Or is it a feature?

I also think the bit-width of the channel decoding is wrong as other sources are suggesting it is a 4-bit value which would be good for 15 channels, btw. The encoding function (sending commands from pimatic to the shutter) also looks odd to me.

@all, @rowoy, @ghv I need a user with rohrmotor24 for testing the modified protocol and to get more test data, please

@mwittig: I ordered yesterday my equipment incl. an hand sender so I can provide it shortly. Do you think you are able to implement the 4 bit width shortly?

@OrTiN said in Shutter protocols limited to 4 Channels (especially shutter4):

I ordered yesterday my equipment incl. an hand sender so I can provide it shortly.

That’s great

Do you think you are able to implement the 4 bit width shortly?

Yes. I have it on my test system already, but I don’t have the hardware to test with. Just unit tests from pre-recorded messages.
Once you have the hardware we can do some real life tests. It would also be great to see more users testing it, as there will be some breaking changes. Apart from the issues already mentioned I noticed that the decoding of the unit id is also wrong (currently 29 bits instead of 28 bits). Thus users will have to change their existing device setup with a future release.

https://github.com/pimatic/rfcontroljs/commit/ceade288fa650c3ee03b33dc345a4d81bbc42177

I think I will install the controller tomorrow or Friday, so we can do some magic from then.
I can provide debug messages from homeduino maybe today.

Info for all you guy who are interested in Rohrmotor24 remote RF wall controller.

The controller works with shutter3 protocol. The dev @mwittig extended the protocol to handle up to 15 channels (+1 channel for all). Works like a charm!

The ID can be defined free, e.g. 12345678. It is not necessary to buy a remote sender.

@OrTiN said in Shutter protocols limited to 4 Channels (especially shutter4):

The controller works with shutter3 protocol. The dev @mwittig extended the protocol to handle up to 15 channels (+1 channel for all). Works like a charm!

That sounds good! I have read (in the German section) that it gives a problem with the Alexa controll.
So you can’t stop the shutter with Alexa, can you confirm this (when you have Alexa )

Hi @V1per. I’M not using Alexa, sorry!

@OrTiN
very nice to hear that this works! could solve some problems with installation.
Actually i am having two devices - 1 Intertecno CMR500 shutter device and 1 wall switch. so the costs are twice as much as the rohrmotor switch.
Also it has a nice design.

Hi,
I want to ask when the rohrmotor24 extended version of homeduino will be released officially? I tried to ask this the dev mwittig two or more times, but got no answer, is there anybody else who can give an answer for this? Is there a special reason to hold back the update?

@ortin Sorry for not having consolidated the code changes in a new release, yet. Hopefully, I can find some time to do it after the summer break. The code and tests are 99% complete, but I need to double-check a few things.