Somfy 5 io Pure II @MQTT

Hardware
1

I wanted to share my small hardware adapter for the Somfy remote as the community here helped me a lot just while reading. Goal was to not solder to the board and remove the battery. ESP8266 based D1 mini is used. Needed just to press the button but I managed to controll the remote for all channels.

And: the adapter was easily built using Fusion360 with a picture of the adapter inserted. In case anyone wants to safe time, this is an idea worth considering.

Hope the pictures are enough, along the code and STL.

If someone wants to make it more adjustable, please create a PR.

2 Likes
2

Hi
Thank you for this.
Can you share detailes how did you set up ESP8266 and Home Assistant? ESPhome, schematics etc?

3

The HASS setup in the yaml is accordingly:

> cover:
> 
>   - platform: mqtt
> 
>     name: "eg_terasse_alle"
> 
>     command_topic: "shades/terasse/cmd/channel0"
> 
>     payload_open: "up"
> 
>     payload_close: "down"
> 
>     payload_stop: "stop"
> 
>     optimistic: true
> 
>     value_template: "{{ value.x }}"

Please check the github link, and let me know - the code should compile with plattform.io under Visual Code, programmed via an Micro-USB-cable. If you have any targeted questions, feel free to ask =)

4

Hello Axel
I’ve just got such a SOmfy 5 io Pure II remote control and would like to control it by MQTT. I can not find any documents here or in github showing the wiring connections from the board to the remote itself. Would it be possible to provide a schematic diagram?
Thanks,
Dieter

5

I will create one later - the trick/information is yet in the code and the PCB is described. But I will make a better documentation to be clear. =)

6

@devau : does this help? https://github.com/lxnoid/SomfyIO/blob/c1a4ee1ab20e0cd95213c6cc1ef700d739b76f50/SomfyIOZeichnung.svg

7

Perfect, thanks a lot Alex! In fact I’m using SmartHomeNG with the mosquitto MQTT-Broker and not HomeAssistant.io. So I’m trying now to understand your code to adapt it. This will take quite some time as I’m only familiar with Tasmota-based implementations :slight_smile:

8

oh, the code is fairly simple for MQTT

In HA:

- name: "eg_terasse_alle"
  command_topic: "shades/terasse/cmd/channel0"
  payload_open: "up"
  payload_close: "down"
  payload_stop: "stop"

The d1 mini listens to all cmds in topic “shades/terasse/cmd/channel” - 0 is all channels 1-4, else the dedicated channel is triggered. You can move with up/down or stop.

9

The code itself can be compiled successfully. Running the program gives “Config File missing.”. And the program seems not to go any further because there is an endless loop
for (;;) delay(1)
If I remove that “for-loop” I get the following output:
Connecting to WiFi
fpm close 3
mode : sta(d8:bf:c0:14:37:96)
add if0
sleep disable
...Connecting to WiFi
...Connecting to WiFi
...Connecting to WiFi
scandone
state: 0 -> 2 (b0)
...Connecting to WiFi
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 3
cnt
connected with XYZNET, channel 4
dhcp client start...
ip:192.168.1.194,mask:255.255.255.0,gw:192.168.1.1
Connected to WiFi
...Connecting to MQTT
Connected to MQTT
-- End of Setup --
loop -> Queue count: 1
loop -> Queue full : 0
loop -> Queue Popped.
loop -> # of edges 0
loop -> # of edges 0
here I manually stopped it. What’s the problem of the config.file “config.json”?

10

I think I forgot to mention explicitly in the readme more details. The config.json needs your matching credentials for wifi and MQTT, then you need to create a littleFS filesystem from this. This needs to be flashed/uploaded in platform.io to the d1 mini.
Should to the trick.

11

Why using such a file? I simply can put in the credentials hardcoded into main.cpp at the following location, isn’t it?
image
If there’s no other reason using the LittleFS then I think I can remove the whole FS code part?
But if there’s a reason, then I have to update my brains how the LittleFS works and how to create it by a small code in VS Code to upload it…And also I need to know the exact syntax rules for the config file (best if you could supply an example of it).

12

you can find an example on github in the data folder.
I chose this approach as we have dozens of projects in multiple houses using this approach. No code to change for my dad e.G.