Hi,
I have Mobilus GTW gateway which is used to manage roller shutters.
Link to the device description: https://mobilus.pl/en/mobilus-products/sterowanie-mobilus/sterowanie-radiowe-mobilus/cosmo-gtw/
It is possible to connect to this device by local network or cloud service - MOBILUS
It would be nice to have it integrated with HA.
BR,
TL
Hi @tomecheq,
You have a better chance if you send an email to Mobilus and ask them if it is possible to integrate the Gateway through a local API. And if the API is public.
I don’t think that Mobilus really into IoT anymore. They stopped selling ages ago their Z-Wave gateway, none of their product is ZWave plus, and they went on the road with Cosmo which is not used really by any other company.
I know them, because I have their Z-Wave Roller Shutter controllers, but it would have been a better investment if I would have bought Qubino or Fibaro ones.
Hi @tomacheq,
I have created a small project that addresses this problem:
it requires basic soldering skills to create a MQTT adapter that forwards published messages to mobilus cosmo hm remote.
It can be then easily configured in HA. Worth giving a try.
Is it any option to integrate COSMO | GTW and Home Assistance?
HI there,
I was looking for something to control my mobilus shutters without success, until now!
Thank you for sharing your project.
I may want to implement it someday but with a different type of remote control…
I own Cosmo H5 - it will be easier to determine the remote control’s current position. 
I was looking at your wiring schematics and I was wondering if optocouplers PC817 are correctly connected – shouldn’t transistor side be connected with remote control momentary switch and LED side to be connected with Weemos output? Am I missing something?
Marcin
Few days later…
I successfully implemented your solution… thanks again for sharing!
I used esp32 - I know, overkill. but its cheap as well.
I had to adjust timings, delays , add some of these here and there,few minor tweaks in code to adjust to different type of remote… and I had to rebuild Wifi connection configuration ,- Not sure why, but it didn’t want to cooperate with my ESP32 board.
Thanks to you I don’t have to put 6 shutters modules and I don’t need to worry about how I get them squeeze under wall switches
As I wrote in my previous post, schematic you shared is a bit wrong… Optocouplers should be connected the other way around.
Marcin
Is it possible, that You can share your project?
This is how it looks like…
It’s based on pwrozycki schematics, idea and ESP32 Program
Just changed few bits to adjust it to my mobilus remote control.
Hi @tykasan,
Thanks for sharing your solution, sounds very good. Last year I tried to find a solution with Shelly 2.5 to control my shutters, but the connection doesn’t work correctly (e.g. due to missing information about shutter position). So maybe this solution can solve my problem to integrate the shutters within HA.
Another question: if I understand your solution correct, you are using the remote control at a fix place in your home. Are you facing any problems with low signal because of too long distance to the shutters?
Best regards
Matze
@matze_ha
I do not face any issues with low signal due to low distance, as Mobilus motors have signal repeater build in…
If you have mobilus motors, read on manual on how to enable that feature.
@pwrozycki or @tykasan what has to be changed in home assistant? The configurations from GIT should be integrated in configuration yaml correct? But how to control the shutters/send commands to it? In my home assistant ZigBee2mqtt is running and normally I connect new devices with it.
Hi. Any news on this topic? Did someone integrate Mobilus GTW with HA?
@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
