This is a Somfy TaHoma NodeServer plugin for controlling shades and scenarios (RTS, io, Zigbee, and other TaHoma applications) on Polyglot for EISY/Polisy.

This is the model Tahoma Box / Switch , I am on Firmware version 2026 2.3-5

Phantom Blinds (RTS) is the primary application this project was built for, because that was my need, but I quickly came to conclusion that this could be used for quite a bit more.

Take a look at the readme if you would like to see more: https://github.com/sejgit/udi-tahoma-pg3x

and the config https://github.com/sejgit/udi-tahoma-pg3x/blob/main/POLYGLOT_CONFIG.md

I am using this now at home, seems to be handling my 8 RTS Phantom Blinds well.

commands: Open / Close / Stop / MyPosition

status: id / battery (if it has them) / last command (on the rts this is just success or failure if the Tahoma processed your command.

io & zigbee can give you much more including position commands and status, these are in plugin but not tested.

Next on the agenda is to add scenes which can be defined in the Tahoma box.

Very interested in feedback, while it should bring in an io or zigbee device, they have not been tested... send me your logs!

Neat stuff! I actually have the previous TaHoma hub, the Beecon. I wonder if the software functionality is the same? I'll probably give it a try. I'm currently using a UTRSI-II with the Somfy plugin and it has been very reliable, so there is no urgency, but it's always interesting to try new things.

Thanks for working on this. I have the Tahoma Switch and 24 Somfy Zigbee motors and will give this plug-in a try once I get back from traveling.

Glad to hear there is some interest here.

@Guy Lavoie let me know if the Beecon works, if it does I'll add it to the docs, if not I could do some research on the differences and see if possible.

@jfai let me know if the Zibee motors works, and if not quite DM me some logs.

BTW: : I was able to spend some time this afternoon and work on the scenes working as well. Not working yet but they show up. There may be an update since you installed.

Edited Saturday at 08:46 PM2 days by sjenkins

Well I had a bit of time so I installed the shiny new plugin on one of my test Polisys and set it up. Verdict: it works great with the Beecon! 🙂

I did have to configure the gateway-ip parameter, which took a bit of searching on my eero router device table. For those searching for it, it appears as "gateway-XXXX-XXXX-XXXX" (the unit's PIN number). The first tahoma-token I generated failed, the second one worked. Maybe the first one timed out between the time it was generated and when I used it.

Restarting the nodeserver had it find my 4 RTS blinds, names and all. Restarting admin console made the controls appear. Resync UDMobile and I was in business. 🙂 Only minor quibble is that UDMobile shows the devices as a light bulb by default. I set a custom icon to be a roller shade. Cool!!

The Tahoma app also supports generic Zigbee devices. In fact that's one of the differences beween the TaHoma Beecon and the Switch: the Beecon supports RTS and Zigbee, while the Switch also supports something called IO. The Beecon is sometimes also called the Smart Gateway. I might try adding a generic Zigbee bulb to it in the next few days and see how the Tahoma app sees it, and then the plugin.

Thanks for creating this!

Took a bit but got scenes working, unfortunately also found an issue that say Tahoma only lets control happen through the cloud and they have no plans to change that. sigh.

So optionally you can add your Tahoma/Somfy login to the plugin and it will activate the scenes you make on the app. Leave blank if you don't want it.

The shades are still local api and the scenes will populate through local only (but are useless and won't activate).

Kind of a bummer and my tinfoil hat gets warm going through the cloud for almost anything except Universal Devices Its likely better just to make Eisy scenes and use them ; I just wanted to see if I could make it happen.

So there you go, play with it as it is, up to v0.0.22 . Leaving it in beta / non-production for a while until it feels stable.

Full disclosure I used my Hunter Douglas plugin as the base for this, which I wrote by hand, then used Cursor to help me mod it for this one. I read all the code over and am cool with it. There are some word choices in the docs I have been correcting as I go, but let me know if anyone finds something they think sounds weird. For sure any code you don't like.

4 minutes ago, Guy Lavoie said:

Well I had a bit of time so I installed the shiny new plugin on one of my test Polisys and set it up. Verdict: it works great with the Beecon! 🙂

I did have to configure the gateway-ip parameter, which took a bit of searching on my eero router device table. For those searching for it, it appears as "gateway-XXXX-XXXX-XXXX" (the unit's PIN number). The first tahoma-token I generated failed, the second one worked. Maybe the first one timed out between the time it was generated and when I used it.

Restarting the nodeserver had it find my 4 RTS blinds, names and all. Restarting admin console made the controls appear. Resync UDMobile and I was in business. 🙂 Only minor quibble is that UDMobile shows the devices as a light bulb by default. I set a custom icon to be a roller shade. Cool!!

The Tahoma app also supports generic Zigbee devices. In fact that's one of the differences beween the TaHoma Beecon and the Switch: the Beecon supports RTS and Zigbee, while the Switch also supports something called IO. The Beecon is sometimes also called the Smart Gateway. I might try adding a generic Zigbee bulb to it in the next few days and see how the Tahoma app sees it, and then the plugin.

Thanks for creating this!

@Guy Lavoie , very cool !! Glad the Beecon worked ! Took me two shots at the token too!

hey if the instructions are different to get the token, pass them to me , and I'll put them in the config instructions.

Not sure which version you ended up with as I have been pushing all day v0.0.22 is latest.

Feel free to list off the gripes. On my eisy-ui and remote app the shades show as two arrows in opposite directions, but in the admin they are a light bulb, that's odd.

btw: : the io are shades you can set the position and read the position, unlike the rts shades which are fire and forget.

Edited Sunday at 02:17 AM2 days by sjenkins

To my knowledge there is only one Somfy app, supporting both the Beecon and the Switch (like UDM supporting both Polisy and eisy), so getting the token is the same procedure. You might want to add the Somfy app menu path and procedure to generate the token to your instructions.

The one or two arrows thing seems standard for controls that have child nodes. Hue plugin does that too. There might be a way for UDMobile to improve that.

I'll check which version I have tomorrow.

@Guy Lavoie Instructions to generate the bearer token are in the polyglot config file which shows up when you hit config after installation.

I will add something about Brecon compatibility tomorrow

Just for kicks today, I added a Zigbee device to the Somfy app (a simple on/off appliance module) just to see what would happen. The app sees it as a on/off device, and I can control it from the app. Then I did a rediscover in the plugin. It added three nodes: two "ZIGBEE" nodes, and a third one with the name I gave to the device in the Somfy app: "Light". Looks like this:

The three new devices have the same controls, which are more numerous than the RTS shades. Here is the one for the "Light" device:

It seems to be assuming that the device is a Zigbee shade. Pressing the buttons don't actually control the device in any way.

Maybe there is additionnal information that would allow the plugin to identify it as a non-shade device, and allow simple on/off control. It would make an alternative to the ZMatter dongle for simple Zigbee device control. But don't waste time on it, this is beyond the scope of the plugin.

Just thought you'd find this interesting.

@Guy Lavoie

When making the node there was a generic zigbee device which I ended up filtering. The device you got with all the parameters is the fallback shade device with every parameter. This plugin got its origin from my Hunter Douglas plugin, it only knows shades as that was really my scope here. If we want to go further not sure what deep end we are getting into. If this has value you can dm me a copy of your logs (don’t put in open forum can’t remember if I have scrubbed them yet for personal info, on my todo list) I can try to do something with them. Not sure if there is a table somewhere or I will need to do it device by device. If you send it to me include the model number of the zigbee device so I can reference.

7 hours ago, sjenkins said:

@Guy Lavoie

When making the node there was a generic zigbee device which I ended up filtering. The device you got with all the parameters is the fallback shade device with every parameter. This plugin got its origin from my Hunter Douglas plugin, it only knows shades as that was really my scope here. If we want to go further not sure what deep end we are getting into.

Well that's it. As my post started, I tried this just for kicks, because it was easy. If the "generic zigbee device" means that you could theoretically send standard zigbee on/off,etc commands (if there is such a thing) and that you "filtered out" all commands that didn't pertain to blinds, then that would explain the specific commands seen at the bottom of the node screen. If something simple like an optional parameter to allow all generic zigbee commands to appear could be added, then it might be worthwhile. If it's not that straigtforward and this takes you down a rabbit hole, then don't bother. The plugin does what it's meant to do very well!

@Guy Lavoie ,

Agree, I think let's let this one stabilise with rts, zigbee, io somfy blinds. If in the future there is a bit of demand and some free time we can move in that direction. In the mean time I am moving my dhcp from my router to an independent server, my whole house has been grumpy for two days. sigh.