Fyi, it seems to work with miner tweaks to the pyhoma library:
I’ll have to wait for proper devices to be sure, but this looks promising 
1 Like
Hello Donny,
First of all great work.
I’m allways in for some hacking 
but i’m not a programmer or something, and i do’nt like cloud solutions either.
Do you think, when i use your guide to “root” the software, the orignally functions to somfy will still keep working? Now we are using the official HA addon to control the 2 blinds via the somfy cloud.
It woul be nice to experiment with the “open” variant of yours, while the somfy variant will still be working.
Thanks, regards,
Hey Donny,
Any updates? Or did you settle for the Velux KFL200 local box :D.
Hello I’ve a cozytouch myself and would highly appreciate to remote this device locally as I hate cloud services. Any progress here ?
No, the local API seems crippled on purpose. Whatever you do you cannot seem to add new devices. Another option would be to snuff the DBUS messages but my Connexoon was un-rooted by an update and haven’t gotten around to re-rooting it.
Okay so I put some more time into this. I tweaked the Tahoma integration a bit to allow for communication with the local API:
It can now talk to the connexoon over HTTP directly to its local IP address without the need for any sort of cloud:
I’ve also gotten several questions from people wanting to know how exactly you modify the firmware once you extract it (see my blog for instructions on that). No guarantees but here are my notes on that:
mkdir ubi-root
mkdir ubi-rootB
mkdir extract
sudo modprobe nandsim first_id_byte=0xec second_id_byte=0xa1 third_id_byte=0x00 fourth_id_byte=0x15;
sudo flash_erase /dev/mtd0 0 0
sudo nandwrite /dev/mtd0 ubi-volume.bin
sudo modprobe ubi
sudo ubiattach -p /dev/mtd0 -O 2048
sudo mount -t ubifs -o rw /dev/ubi0_7 ubi-root
sudo mount -t ubifs -o rw /dev/ubi0_9 ubi-rootB
cd ubi-root/etc/rc5.d
sudo ln -s ../init.d/dropbear S06dropbear
cd ubi-root/etc/rc2.d
sudo ln -s ../init.d/dropbear S06dropbear
cd ubi-rootB/etc/rc5.d
sudo ln -s ../init.d/dropbear S06dropbear
cd ubi-rootB/etc/rc2.d
sudo ln -s ../init.d/dropbear S06dropbear
edit etc/shadow -> add root hash (both root and rootB)
sudo umount ubi-root
sudo umount ubi-rootB
for i in {0..10}; do name=$(ubinfo -d 0 -n $i | grep Name | awk '{print $2}'); sudo dd if=/dev/ubi0_$i of=extract/$name.bin; done
cd extract
for i in {0..5}; do name=$(ubinfo -d 0 -n $i | grep Name | awk '{print $2}');size=$(ubinfo -d 0 -n $i | grep Size | cut -d '(' -f 2 | cut -d ' ' -f 1); echo -en "[$name]\nmode=ubi\nimage=$name.bin\nvol_id=$i\nvol_size=$size\nvol_type=static\nvol_name=$name\nvol_alignment=1\n\n"; done > config.ini
for i in {6..10}; do name=$(ubinfo -d 0 -n $i | grep Name | awk '{print $2}');size=$(ubinfo -d 0 -n $i | grep Size | cut -d '(' -f 2 | cut -d ' ' -f 1); echo -en "[$name]\nmode=ubi\nimage=$name.bin\nvol_id=$i\nvol_size=$size\nvol_type=dynamic\nvol_name=$name\nvol_alignment=1\n\n"; done >> config.ini
ubinize -o ../ubi-volume_patched.bin -p 131072 -m 2048 -O 2048 -s 512 -Q 1056559212 config.ini
cd ..
sudo umount /dev/ubi0_*
sudo ubidetach -p /dev/mtd0
sudo rmmod ubifs ubi nandsim
./sam-ba_3.5/sam-ba -p usb -b sam9xx5-ek -a lowlevel
./sam-ba_3.5/sam-ba -p usb -b sam9xx5-ek -a extram
./sam-ba_3.5/sam-ba -p usb -b sam9xx5-ek -a nandflash:::0xc0902405 -c erase:0x20000 -c write:ubi-volume_patched.bin:0x20000 -c verify:ubi-volume_patched.bin:0x20000
Not quite sure where to go from here to be honest :).
4 Likes
Wow…this is amazing…local support
Does it also works with the Tahoma v1?
Not sure, I don’t have one to test
FYI it seems you can generate a token using this endpoint:
https://tahomalink.com/enduser-mobile-web/enduserAPI/config/<gateway id>/local/tokens/generate
1 Like
Neat find!
Have anyone tried this with their new TaHoma Switch hub?
Hello,
It’s a great job.
I will use your guide to “root” the software.
Do you think that the original functions of Somfy will continue to work?
I use my connexoon to fly 3 integra windows with 3 flaps via the Somfy cloud.
I want to draw the dialogue between Connexoon and the servers.
Do you have an idea of the Principle of Exchanges?
Since there is no open port:
Does the Connexoon open a VPN with the servers?
Does the Connexoon act as a web client of SOMFY servers?
Does the Removal SSL do not send the connection to the servers?
Do you have technical documentation on Connexonnon
Thanks best regards,
Hello Yves,
I recently used the guide to root mij connexoon and it is working.
The old way, via the somfy cloud also keeps working, it’s a sort of hybrid situation.
Just a small tip, edit the /etc/hosts file and add:
127.0.0.1 ha-upgrade.overkiz.com
127.0.0.1 ha-update.overkiz.com
Because else, the somfy cloud server will update and overwrite your rooted firmware and you will loose the root.
Another tip, when you reboot the connexoon or you power cycle it, you have to do again:
mount -o remount,rw /
rm /etc/lighttpd.d/ssl.conf
/etc/init.d/webserver start
/etc/init.d/local start
So i make a start.sh file in /etc/init.d and symlinked it in /etc/rc2.d and /etc/rc5.d and name it S99start symlinked to …/init.d/start.sh
Good luck,
Regards,
3 Likes
Hi, thanks for posting about it. I also went down that route a while ago but I had not much successs controling my deives localy. They always went offline a few seconds after beeing controlled by homeassistant.
Does it currently work for you on a daily basis?
There’s currently a bug in the local version of the python tahoma API library that’s causing this disconnect. I’ll drop a message here when it’s been adressed 
Do you need help? In the last fix I missed that the order of the parameters should be different. (optional not before others).
1 Like
I’ve just pushed a commit that seems to fix the issue, at least for the one test user I’m in contact with . If anyone else wants a go: GitHub - dmaasland/ha-tahoma: Custom component for Home Assistant to interact with smart devices via Somfy TaHoma or other OverKiz based API's.. If you’ve already installed, you also need an updated pyhoma: GitHub - dmaasland/python-tahoma-api: Async Python wrapper to interact with internal Somfy TaHoma API, or other OverKiz API's..
Disclaimer: I did the absolute bare minimum in order to make this work. Because of that I probably introduced other weird bugs. Don’t rely on this for production use
2 Likes
Yes, the test user can confirm that it is working, without errors. 
Just download a new version of the custom_components from Donny, and reinstall in HA.
Thanks for the good work!.
Regards.
If anyone is looking to automate Somfy blinds with HA and doesn’t want to shell out the quite frankly extortionate £149 for the hub, take a look here: GitHub - paultbarrett/esphome-somfy: Esphome configuration for Somfy Blind
< £10 worth of components and 30 minutes of soldering and you have your very own offline hub, I’m using it with 4x blinds and it seems to work perfectly.
Hello Swifty,
The problem is that Somfy has two types of protocols.
The RTS 433Mhz protocol, wich is cheap to assemble.
The IO 868Mhz protocol, wich is not cheap, and not yet to integrate without a Hub.
I have the IO 868Mhz protocol, and the connexoon Hub to integrate it.
So if you have a DIY solution for IO 868Mhz protocol, it would be nice?.
Regards.
1 Like