@tykasan ,
I hope you’re doing well out there! Are you still active in here? I was about to start working on this project, but I haven’t managed to figure out which pins have you used for this one. Could you share some schematics or maybe pictures how you connected them? Did you had to do some coding with it as well?
Cheers,
Mike
I was reading on another forum about this issue and found some interesting stuff on the net in a Domoticz forum. It is a WIP, but seems to be really promissing:
Hey,
I was able to create a plugin for home assistant that talks locally to Mobilus Cosmo GTW. (@GSzabados thank you for sharing). Please check:
Is this correct?
The Mobilus COSMO 2WAY shutters do not report their state. As a result, the cover entities in Home Assistant will not reflect the actual position of the shutters after they are moved.
I would have assumed that the controllers have an option to calibrate and report to the Gateway their actual position, which would be avaialable through the MQTT client.
(At least the Mobilus/MOB.IQ Z-Wave shutter controllers do have that feature, but that is Z-Wave.)
Indeed one of the remote manuals suggests that you can position the blind to a percentage position in III Control Mode. But is the 2 way communication not supported by the controllers, only just by the motors?
Edit:
The C-ZR manual suggests that the module can report the position to the Gateway, but it has to be set up for bi-directional communication and III Operation mode as I understand.
Hi @GSzabados,
Yes, it uses the mobilus-client mentioned earlier. That client simply hooks into GTW MQTT broker and acts similar as frontend client (that is present on the device).
Hmm, good question. I have read that manual too, but I wasn’t able to make it work on my shutters (COSMO 2WAY). Maybe the newer that you have (Z-wave) has this working, I’m not sure.
There is a command in GTW that returns current_state (and is currently supported in the client), but in my case it didn’t returned any meaningul data (example: some shutters were reported they were closed but they wasn’t). So I decided to just switch it off on home assistant side. However maybe I’m mistaken here, if so, that could be easily added via current_state menitoned earlier. But currently I’m simply not able to test it properly.
The Z-wave ones are EOL, Mobilus is not selling them anymore. I believe it was a joint-venture developed thing with Fakro, as some system recognised it as a Fakro product.
I’ve never understood why Mobilus developed the COSMO setup the way they did. It is just an unknown standard in home automation, meanwhile Z-wave is out there and many different brand uses it.
At some point Mobilus used to have even a Z-wave gateway, but it has first disappeared from the market, you could barely find it around 2018.
https://mobilus.pl/en/technologie/z-wave/
If the COSMO is similar in any form to the Z-wave ones, it should have a calibration function to learn the end positions of the blind. It should go fully open, then fully close and should stop at 50% when finished.
The communication of the position should come with the 2WAY function of the COSMO system.
By any chance, aren’t those blinds just wired incorrectly, or the motor has been reversed? Or wasn’t that the case as it was showing just opposite position?
I would assume, that if specific position can be sent to the module like 30%, then the system knows the position of the blind correctly.
Actually I think you are right and there is some status retained. However there is some latency with synchronizing the state (that probably confused me). I will do some more testing and add this feature to the plugin, this shouldn’t be hard, as the main code is there.
I see that you have a big knowledge about this shutters. I didn’t know that, I thought they abandoned this COSMO 2WAY protocol. I haven’t follow their offer either, as naturally you just buy the shutters live with it to the end 
The Z-wave one behaves the same, you set the percentage and reports that as position, but a second later reports the actual position, so I had to set up an automation to after a minute fetch the correct value. It should report it when stopped, but it doesn’t do that for some reason.
I played with them quite a lot, they set me on the home automation path. First I had just a remote with them only for a few roller blinds, but then I wanted to control them. I’ve managed to get a SmartThings V2 Hub which had Z-wave (because you couldn’t already buy the Mobilus Z-wave Gateway), but I had to write the Device Handler for it. I learned a lot about them. As I was working on that I contacted Mobilus for some further documentation an the Z-wave parameters how to calibrate them, because the manual was not including those. I have even purchased the rest of the modules which I needed for some blinds which were not automated at that time yet. They sent me a Mobilus cup with the order. They were really helpful. But when I tried to contact the two people there recently, who I changed some emails before, they have not answered it. One of them works for some other company already, the other might have changed positions, who knows.
My choice nowadays would be either a Zigbee module for blinds, which wasn’t an option at that time, or a Fibaro or Qubino Z-Wave roller shutter module. (The Zigbee ones are definitely cheaper.)
I think that whole COSMO ecosystem is a bit of a dead end, but with your integration it makes more sense now.
And I think Fakro took over the Mobilus/MOB.IQ Z-wave line, just compare the remote and module images. (They just look like the COSMO ones 
)
Fakro:
https://allegro.pl/listing?string=fakro%20z-wave
Mob.IQ:
Interesting. When I was looking for an information about COSMO I found Z-Wave on their website. My first thoguht was that the problem is finally solved, because Z-Wave is open protocol. But it looks like not quite as you described.
I agree, I would choose zigbee too, just add it as a part as manual switch on the wall. It would probably be even more reliable than radio protocol provided by manufacturer. But the shutter state will be lost, so this would be a downside.
Anyway it is what it is. The Cosmo GTW is at least the easiest option (for COSMO 2WAY) that does not require any electrical work .
Z-Wave is listed on the website, but if you look at the motors or modules or anywhere else, they don’t have it anymore. The latest one is the Apple HomeKit for modules and the Tuya support for some motors. I believe it is all Bluetooth:
Hey,
really great job, you don’t even know how you made me happy
finally I have blinds in HA 
Cosmo 2WAY reports the status. Additionally, having a Mobilus HCT remote control you can receive notifications on it about an errors, e.g. jammed cover, obstacle detected etc.
On the website dom.mobilus.pl you can also see a status report, e.g. height reached (top right corner):
Hey @srutututu,
Let’s keep English as communication channel on this thread, so other people can read this too
Thanks for the kind words! I’m aware of the shutter status, during the conversation with @GSzabados, he pointed me to look again in this topic. I have already a task for it: Add current state of the shutters · Issue #3 · zpieslak/mobilus-client-home-assistant · GitHub and some idea how to implement it (it should not be hard - in my spare moment I will commit it).
Regaring HCT, I do not know about it, let me read more.
It’s good to hear that the code is used by you! if you found any issues please report in github tracker as I have only tested this on my shutters.
Hey @srutututu,
I have upgraded the component so now it recognizes the shutter state. There are some also more improvements regading stability and the code confronts more with home assistant line.
The state polling is set to be every 10 minutes and on each manual shutter action (open, close, etc). This could be adjusted and / or probably moved to the configuration if necessary.
Also I needed to change the component domain, so unfortunately the old shutters needs to be manually removed from home assistant. Please check it and let me know if you found some issues.
Hi,
sure, you are right. I changed the language to English.
After testing for a few days, I noticed that the integration does not work with the Mobilus C-MR modules.
This is a Mobilus module that can be added to electric roller shutters to control them via remote control or app. This module reports the open/closed status, it does not report the opening height.
I have this module in 4 roller shutters, as these windows were too narrow (approx. 40cm) to include a motor with smart control. In this case Mobilus arms the roller shutter with a normal drive and adds this module to the kit, for mounting in the electrical box, under the switch.
In addition, I purchased 3 such modules for the roof window roller shutters (without smart), in order to have them all controlled from one app.
So I have 7 of them. In summary, at the moment the integration does not work with them.
Great, I’m starting with tests
Of course I will let you know what my observations are.
Currently, as I wrote earlier, the C-MR modules are not working.
hey @srutututu,
Thanks for the report! Just to clarify: by “the C-MR modules are not working” you mean that it cannot be controlled (example stop or start) or it does not report the proper status (is shutter opened or closed) ?
hey,
I meant that they don’t work when you press start/stop.
If I close it with e.g. remote or switch, the status is shown correctly.
Ok, do they work with Moblus GTW? Like can you open / close them from official moblus app or local moblus gtw page?
surely, they work with app, remote, webpage interface, etc. I wouldn’t writing if it didn’t
Here is an example printscreen showing normal shutters and shutters with C-MR. As you can see, you can only send to C-MR commands like open, close and stop. You cannot choose percentage position.
Here is C-MR on mobilus website:
hey @srutututu,
Thanks! I replied in the issue thread: doesn't open shutters controlled by the mobilus C-MR module · Issue #9 · zpieslak/mobilus-client-home-assistant · GitHub. Let’s continue there. I will update that task once done.
