dubocr / homebridge-tahoma Goto Github PK

I‘m using the Tahoma plugin since last summer with nearly no problems, but with the cold temperatures in the last couple of weeks I noticed that while the Tahoma App shows the right temperature Even with minus degrees (e.g -5C) in Homekit only 0C is shown. When it‘s warmer then 0C everything works perfect. I have the io- temperature sensor from Somfy. Anyone else having such an issue?

Hi dubocr,

On a good morning scene, I would just like to turn the blinds to 45 degrees but first turn around and then go down. That means it closes again

Thanks for helping.

[2018-10-10 21:36:00] [Tahoma] [Televize] setOrientation[48]
[2018-10-10 21:36:00] [Tahoma] [Obyvak] setOrientation[50]
[2018-10-10 21:36:00] [Tahoma] [Loznice] setOrientation[52]
[2018-10-10 21:36:00] [Tahoma] [Ostruvek] setOrientation[50]
[2018-10-10 21:36:00] [Tahoma] [Pracovna] setOrientation[50]
[2018-10-10 21:36:00] [Tahoma] [Stul] setOrientation[53]
[2018-10-10 21:36:02] [Tahoma] [Ostruvek] setClosure[100]
[2018-10-10 21:36:02] [Tahoma] [Stul] setClosure[100]
[2018-10-10 21:36:02] [Tahoma] [Obyvak] setClosure[100]
[2018-10-10 21:36:02] [Tahoma] [Loznice] setClosure[100]
[2018-10-10 21:36:02] [Tahoma] [Televize] setClosure[100]
[2018-10-10 21:36:02] [Tahoma] [Pracovna] setClosure[100]
[2018-10-10 21:36:03] [Tahoma] [Obyvak] setOrientation COMPLETED
[2018-10-10 21:36:03] [Tahoma] Error 400 Execution queue is full on gateway: #0813-6854-2124 (soft limit: 10) (EXEC_QUEUE_FULL)
[2018-10-10 21:36:07] [Tahoma] [Televize] setOrientation COMPLETED
[2018-10-10 21:36:07] [Tahoma] [Stul] setOrientation CMDCANCELLED
[2018-10-10 21:36:07] [Tahoma] [Pracovna] setOrientation COMPLETED
[2018-10-10 21:36:07] [Tahoma] [Ostruvek] setOrientation CMDCANCELLED
[2018-10-10 21:36:09] [Tahoma] [Ostruvek] setClosure CMDCANCELLED
[2018-10-10 21:36:09] [Tahoma] [Loznice] setOrientation COMPLETED
[2018-10-10 21:36:09] [Tahoma] [Obyvak] setClosure COMPLETED
[2018-10-10 21:36:11] [Tahoma] [Loznice] setClosure COMPLETED
[2018-10-10 21:36:11] [Tahoma] [Stul] setClosure COMPLETED
[2018-10-10 21:36:11] [Tahoma] [Televize] setClosure COMPLETED

Hi, thanks for your great plugins.

I want to close the blinds to "my-Position", so there are some gaps left in the top of the blind.
Is this possible?

When I try to close it to 45 % or sth like this via homekit, the blind drive to my-position but then there is an error, because homekit can't find out the position of the blind (according to homekit it´s still open).

Do u have an idea?

Today I installed the TaHoma Premium and configured my awning on the terrace to work with Homebridge. It’s an older Somfy motor with Rts control. Unfortunately it reacts only on fully open (100%) or on close (0%). If I select another value HomeKit shows the value but the awning is not doing anything.

Bonjour Romain,

Je viens d'installer une interface de chauffage Somfy io.
Il est bien reconnu sous Tahoma, fonctionne.

En revanche lors de l'ajout à HomeKit, il me signale que l'accessoire est "sans réponse".
Il est pourtant bien chargé par homebridge, il s'appelle Veranda.

Une idée ?

Hey folks,

I am currently working on an little project with my Tahoma shutters.
For this I really would like to use node-red to set my shutter opening value. So far I only find the option to use mqtt to connect homebridge with node-red, for that I would use all my shutters as single accessories in homebridge.

How can I access and set the value for the Tahoma shutters from the outside of Homekit (Node-Red)?

Cheers
Alex

I'm have two questions about the functionality of the Tahoma shutters. I can set the shutters from 0% to 100% with 1% increment steps. I would like a possibility to change this value to 5%, like 0%, 5%, 10%, ..., 95%, 100%. Would this be possible?

When I'm moving for example the shutter slider in HomeKit from 100 % to 15%, the movement of the shutter is "lagging". On the Tahoma website I can see that 4, 5 or even more SetClosure commands are executed. Is there a possibility to add a tiny delay before the movement of the slider is executed?

Thanks in advance.

Bonjour,

Serait-il possible de préciser le type de device dans les logs ?
En effet voici ce que me retourne la page http://home.dubocr.fr/tools/setup :

1 RollerShutter > PositionableTiltedRollerShutter
1 Window > PositionableTiltedWindow

Malheureusement on ne retrouve pas cette info dans le plugin :

[2018-6-15 18:04:38] [Connexoon] Initializing Tahoma platform...
[2018-6-15 18:04:41] [Connexoon] Device type Pod unknown
[2018-6-15 18:04:41] [Connexoon] [Volet Velux] core:NameState=Volet Velux
[2018-6-15 18:04:41] [Connexoon] [Volet Velux] core:PriorityLockTimerState=0
[2018-6-15 18:04:41] [Connexoon] [Volet Velux] core:StatusState=available
[2018-6-15 18:04:41] [Connexoon] [Volet Velux] core:RSSILevelState=100
[2018-6-15 18:04:41] [Connexoon] [Volet Velux] core:ClosureState=99
[2018-6-15 18:04:41] [Connexoon] [Volet Velux] core:OpenClosedState=open
[2018-6-15 18:04:41] [Connexoon] [Fenêtre toit cha] core:NameState=Fenêtre toit cha
[2018-6-15 18:04:41] [Connexoon] [Fenêtre toit cha] core:PriorityLockTimerState=0
[2018-6-15 18:04:41] [Connexoon] [Fenêtre toit cha] core:StatusState=available
[2018-6-15 18:04:41] [Connexoon] [Fenêtre toit cha] core:RSSILevelState=98
[2018-6-15 18:04:41] [Connexoon] [Fenêtre toit cha] core:ClosureState=100
[2018-6-15 18:04:41] [Connexoon] [Fenêtre toit cha] core:OpenClosedState=closed
[2018-6-15 18:04:41] [Connexoon] Device WaterHeatingSystem ignored
[2018-6-15 18:04:41] [Connexoon] Device ElectricitySensor ignored
[2018-6-15 18:04:41] [Connexoon] Initializing platform accessory 'Volet Velux'...
[2018-6-15 18:04:41] [Connexoon] Initializing platform accessory 'Fenêtre toit cha'...

Cordialement,
Ludovic

Bonjour,

Tout d'abord merci pour ce plugin génial qui me permet de commander les appareils suivants depuis ma box Somfy Connexoon :

• Fenêtre de toit Velux Integra
• Volet fenêtre de toit roulant électrique (VELUX Sml)

Voici le log de démarrage:

pi@raspberrypi:~/.homebridge $ homebridge -D 2>&1 |egrep "Connexoon|tahoma"
Loaded plugin: homebridge-tahoma
homebridge-tahoma API version: 2.2  
[2018-6-4 22:09:12] [Connexoon] Initializing Tahoma platform...
[2018-6-4 22:09:12] [Connexoon] Connecting TaHoma server...
[2018-6-4 22:09:12] [Connexoon] Connecting TaHoma server...
[2018-6-4 22:09:14] [Connexoon] Device type Pod unknown
[2018-6-4 22:09:14] [Connexoon] Device WaterHeatingSystem ignored
[2018-6-4 22:09:14] [Connexoon] Device ElectricitySensor ignored
[2018-6-4 22:09:14] [Connexoon] Initializing platform accessory 'Shutter'...
[2018-6-4 22:09:14] [Connexoon] Initializing platform accessory 'Window operator'...

Je rencontre un souci sur le retour d'état dans un cas d'erreur. En effet, lorsque la fenêtre à été ouverte manuellement (débrayée), une tentative remonter une erreur dans les logs mais rien dans l'application HomeKit "Maison", la fenêtre repasse alors grisée car l'ouverture à échouée.

Voici ce que remontent les logs à ce moment précis:

[2018-6-4 22:29:28] [Connexoon] [Window operator] setClosure[0]
[2018-6-4 22:29:33] [Connexoon] [Window operator] setClosure WHILEEXEC_MANUALLY_CONTROLLED

Serait-il possible de remonter une notification pour signaler ce défaut dans HomeKit ?
Eventuellement ça : HMError.Code.actionSetExecutionFailed

Cordialement,
Ludovic

Bonjour,
Je vais faire installer une climatisation Hitachi chez moi (compatible Tahoma)
Je voulais savoir si le plugin était compatible avec la partie clim ou s'il n'avait pas été testé sur cette partie ?

Merci :-)

Morgane

Bonjour,
Tout d'abord un très GRAND merci pour ce plugin, depuis le temps que j'en cherchais un je suis comblée !! Merci beaucoup.

Je voulais regarder si je pouvais faire fonctionner mes radiateurs chez moi sur HomeKit.
Actuellement je les vois, mais lorsque je clique dessus ça me fait planter mon homebridge :-) J'ai bien vu que le fonctionnement n'était pas testé sur les radiateurs donc que le fonctionnement n'était pas garanti.

Au niveau de l'installation il s'agit de 2 thermostats
https://boutique.somfy.fr/programmateur-radio-fil-pilote-1-recepteur-dispo-fevrier-2015.html
https://www.somfy.fr/produits/2401242/thermostat-programmable-sans-fil-contact-sec

Et j'ai des récepteurs sur les radiateurs
https://boutique.somfy.fr/recepteur-sans-fil-fil-pilote-pour-programmateur-radio-fil-pilote.html

Mon homebridge tourne dans un docker sous debian 9.

Pensez-vous que je peux réussir à le faire fonctionner ? Par où dois-je commencer ?

Merci encore

Morgane.

Hi Dubocr,

I would like to have to possibility to see the light value from my sensors. I tried to add following code in beneath line 34:
this.log('['+this.name+'] Luminance value : ' + value);

In syslog I get following error, when I try to restart Homebridge:
Mar 4 12:11:38 Homebridge homebridge[1364]: [2018-3-4 12:11:38] Loaded plugin: homebridge-tahoma Mar 4 12:11:38 Homebridge homebridge[1364]: homebridge-tahoma API version: 2.2 Mar 4 12:11:38 Homebridge homebridge[1364]: /usr/lib/node_modules/homebridge-tahoma/accessories/LightSensor.js:36 Mar 4 12:11:38 Homebridge homebridge[1364]: else Mar 4 12:11:38 Homebridge homebridge[1364]: ^^^^ Mar 4 12:11:38 Homebridge homebridge[1364]: SyntaxError: Unexpected token else Mar 4 12:11:38 Homebridge homebridge[1364]: at createScript (vm.js:80:10) Mar 4 12:11:38 Homebridge homebridge[1364]: at Object.runInThisContext (vm.js:139:10) Mar 4 12:11:38 Homebridge homebridge[1364]: at Module._compile (module.js:607:28) Mar 4 12:11:38 Homebridge homebridge[1364]: at Object.Module._extensions..js (module.js:654:10) Mar 4 12:11:38 Homebridge homebridge[1364]: at Module.load (module.js:556:32) Mar 4 12:11:38 Homebridge homebridge[1364]: at tryModuleLoad (module.js:499:12) Mar 4 12:11:38 Homebridge homebridge[1364]: at Function.Module._load (module.js:491:3) Mar 4 12:11:38 Homebridge homebridge[1364]: at Module.require (module.js:587:17) Mar 4 12:11:38 Homebridge homebridge[1364]: at require (internal/module.js:11:18) Mar 4 12:11:38 Homebridge homebridge[1364]: at /usr/lib/node_modules/homebridge-tahoma/accessories/AbstractAccessory.js:37:39 Mar 4 12:11:38 Homebridge homebridge[1364]: at Array.forEach (<anonymous>) Mar 4 12:11:38 Homebridge homebridge[1364]: at module.exports (/usr/lib/node_modules/homebridge-tahoma/accessories/AbstractAccessory.js:33:36) Mar 4 12:11:38 Homebridge homebridge[1364]: at Plugin.module.exports [as initializer] (/usr/lib/node_modules/homebridge-tahoma/index.js:17:68) Mar 4 12:11:38 Homebridge homebridge[1364]: at Server.<anonymous> (/usr/lib/node_modules/homebridge/lib/server.js:160:14) Mar 4 12:11:38 Homebridge homebridge[1364]: at Array.forEach (<anonymous>) Mar 4 12:11:38 Homebridge homebridge[1364]: at Server._loadPlugins (/usr/lib/node_modules/homebridge/lib/server.js:138:22) Mar 4 12:11:38 Homebridge systemd[1]: homebridge-haussteuerung.service: Main process exited, code=exited, status=1/FAILURE

Do you know what is wrong with that code?

Second, quite often HomeKit loses the connection to the light sensors. Tahoma has a connection. Do you know why, or is this a bug?

Hey,

First thank for this amazing Plugin,
but i can't change the Temeperature of my heater.
Every time i try to change the temperature it jumps back to the temperature before and this error message appears in the console:

[2018-4-2 00:32:30] [Tahoma] [Schlafzimmer Schrank] setHeatingTargetTemperature[24]
[2018-4-2 00:32:30] [Tahoma] Error 400 Managed action group is invalid : No such command : setHeatingTargetTemperature on device zwave://1202-5713-2283/19 (zwave:ProgrammableAndProtectableThermostatSetPointZWaveComponent) (UNSPECIFIED_ERROR)

And it doesn't show me what stands currently either:

But if i open the Heater it shows me what it stands currently:

I don't know if iit's necessary but i use this device:

I hope you can help me :)
(sorry for bad english ^^)

At first a big "thank you" for programming this plugin,

maybe you can help me with this little beauty issue. I have an Somfy RTS awning without position signal installed. Controlling my awning works just fine (up and down) but the up and down commands are reversed. Normaly, on shutters, the commands where correct. Shutter closed = down, shutter open = up. But it doesn't make sense on an awning. When awning has moved outside it's like open and when awning has moved back it's like closed. I'm not a coding specialist. Can you tell me how to change up and down commands in awning.js?

Regards Oli

Hello,
I've an error when I start a scene with more 10 blinds, is it possible to control more ?
This limit is in the plugin or in homekit?
Best Regards
Christopher

Hi Romain
I guess you speak french so it would be easier to communicate but the problem is I have 2 roof windows registered with rts and 3 rollers still registered in rts in my Tahoma box and they don't appear.
Any help would be greatly appreciated.

Thx

Laurent

I'm certain that my credentials are correct. After adding the needed lines to my config file Homebridge won't start up. It gives me the following log error:

[Tahoma] Loggin fail: Too many requests, try again later

When I remove the Tahome platform lines in config again, everything is starting up nicely but without Tahoma 👎

Bonjour,

Tout d'abord merci pour ce plugin génial qui me permet de commander les appareils suivants depuis ma box Somfy Connexoon :

• Fenêtre de toit Velux Integra
• Volet fenêtre de toit roulant électrique (VELUX Sml)

Voici le log de démarrage

pi@raspberrypi:~/.homebridge $ homebridge -D 2>&1 |egrep "Connexoon|tahoma"
Loaded plugin: homebridge-tahoma
homebridge-tahoma API version: 2.2  
[2018-6-4 22:09:12] [Connexoon] Initializing Tahoma platform...
[2018-6-4 22:09:12] [Connexoon] Connecting TaHoma server...
[2018-6-4 22:09:12] [Connexoon] Connecting TaHoma server...
[2018-6-4 22:09:14] [Connexoon] Device type Pod unknown
[2018-6-4 22:09:14] [Connexoon] Device WaterHeatingSystem ignored
[2018-6-4 22:09:14] [Connexoon] Device ElectricitySensor ignored
[2018-6-4 22:09:14] [Connexoon] Initializing platform accessory 'Shutter'...
[2018-6-4 22:09:14] [Connexoon] Initializing platform accessory 'Window operator'...

Je rencontre un souci sur le retour d'état. En effet dans l'application HomeKit "Maison", le volet apparaît ouvert à 1% alors qu'il a bien été fermé via cette même application.
Même chose via l'application "Eve" Elgato.
De fait on a l'impression que le volet est resté ouvert car l'icone n'est pas grisée.

Voici pourtant que je peux voir dans les logs:

[2018-6-4 22:18:17] [Connexoon] [Shutter] setClosure[100]
[2018-6-4 22:18:20] [Connexoon] [Shutter] setClosure COMPLETED

Connaissez-vous ce problème ? Je peux faire des tests pour essayer de comprendre.
Y'a un un moyen de le corriger ?

Ludovic

Hi!

Thanks for this great plugin.
But I have serveral issues

1. With Somfy iO motors you are able to set the heights in percent. Means I can say open 15% for example.
   That works not proper. Homekit jumps between the heights so I can't drive my 15%. Maybe 5% or 2%. But the height sets to 85%
   Full open or full close works perfect

2. I can't combine the iO motors into the automatic scenes. Homekit complains I have to update my Homekit hub to make it work.
   Problem is that my homebridge hub is up to date.

3. The attached enocean temperture sensor is visible, but greyd out and spitts out 0° instead of the real temperature as seen in my Tahoma interface

Is there any way to make my 3 points work? Where can I give support? What do you need from me?

Many thanks in advance

URBANsUNITED

I upgraded from Tahoma Box V1 to Tahoma Box V2, also selled as Tahoma Premium.
Does this plugin support also this newer Box?

Thanks in advance,
Phill

I‘m thinking about buying that Somfy One camera and alarm system and was wondering, if this device is supported by this plugin when I integrate it with my Tahoma setup. And if yes, what functions are supported, e.g. camera live feed, Alarm activation/deactivation.

Hi Romain,

I try to connect my 3 new Atlantics Heaters with Cozytouch/HomeBridge and your plugin.

My setup: rPI 3 / Fresh Raspbian / Fresh HomeBridge / Your plugin & a minimalist config.json

Below, the Homebridge log:

[2018-11-14 20:19:10] Loaded config.json with 0 accessories and 1 platforms.
[2018-11-14 20:19:10] ---
[2018-11-14 20:19:10] Loaded plugin: homebridge-tahoma
homebridge-tahoma API version: 2.2
[2018-11-14 20:19:10] Registering platform 'homebridge-tahoma.Tahoma'
[2018-11-14 20:19:10] ---
[2018-11-14 20:19:10] Loading 1 platforms...
[2018-11-14 20:19:10] [Cozytouch] Initializing Tahoma platform...
[2018-11-14 20:19:12] [Cozytouch] Device type Pod unknown
[2018-11-14 20:19:12] [Cozytouch] [I2G_Actuator] device type: HeatingSystem, name: io:AtlanticElectricalHeaterWithAdjustableTemperatureSetpointIOComponent, protocol: io
[2018-11-14 20:19:12] [Cozytouch] [IO (1468835#2)] device type: TemperatureSensor, name: io:TemperatureInCelciusIOSystemDeviceSensor, protocol: io
[2018-11-14 20:19:12] [Cozytouch] [IO (1468835#3)] device type: ContactSensor, name: io:ContactIOSystemDeviceSensor, protocol: io
[2018-11-14 20:19:12] [Cozytouch] [IO (1468835#4)] device type: OccupancySensor, name: io:OccupancyIOSystemDeviceSensor, protocol: io
[2018-11-14 20:19:12] [Cozytouch] [IO (1468835#5)] device type: ElectricitySensor, name: io:CumulatedElectricalEnergyConsumptionIOSystemDeviceSensor, protocol: io
[2018-11-14 20:19:12] [Cozytouch] [I2G_Actuator] device type: HeatingSystem, name: io:AtlanticElectricalHeaterWithAdjustableTemperatureSetpointIOComponent, protocol: io
[2018-11-14 20:19:12] [Cozytouch] [IO (503269#2)] device type: TemperatureSensor, name: io:TemperatureInCelciusIOSystemDeviceSensor, protocol: io
[2018-11-14 20:19:12] [Cozytouch] [IO (503269#3)] device type: ContactSensor, name: io:ContactIOSystemDeviceSensor, protocol: io
[2018-11-14 20:19:12] [Cozytouch] [IO (503269#4)] device type: OccupancySensor, name: io:OccupancyIOSystemDeviceSensor, protocol: io
[2018-11-14 20:19:12] [Cozytouch] [IO (503269#5)] device type: ElectricitySensor, name: io:CumulatedElectricalEnergyConsumptionIOSystemDeviceSensor, protocol: io
[2018-11-14 20:19:12] [Cozytouch] [I2G_Actuator] device type: HeatingSystem, name: io:AtlanticElectricalHeaterWithAdjustableTemperatureSetpointIOComponent, protocol: io
[2018-11-14 20:19:12] [Cozytouch] [IO (7288378#2)] device type: TemperatureSensor, name: io:TemperatureInCelciusIOSystemDeviceSensor, protocol: io
[2018-11-14 20:19:12] [Cozytouch] [IO (7288378#3)] device type: ContactSensor, name: io:ContactIOSystemDeviceSensor, protocol: io
[2018-11-14 20:19:12] [Cozytouch] [IO (7288378#4)] device type: OccupancySensor, name: io:OccupancyIOSystemDeviceSensor, protocol: io
[2018-11-14 20:19:12] [Cozytouch] [IO (7288378#5)] device type: ElectricitySensor, name: io:CumulatedElectricalEnergyConsumptionIOSystemDeviceSensor, protocol: io
[2018-11-14 20:19:12] [Cozytouch] Initializing platform accessory 'I2G_Actuator'...
[2018-11-14 20:19:12] [Cozytouch] Initializing platform accessory 'IO (1468835#2)'...
[2018-11-14 20:19:12] [Cozytouch] Initializing platform accessory 'IO (1468835#3)'...
[2018-11-14 20:19:12] [Cozytouch] Initializing platform accessory 'IO (1468835#4)'...
[2018-11-14 20:19:12] [Cozytouch] Initializing platform accessory 'IO (1468835#5)'...
[2018-11-14 20:19:12] [Cozytouch] Initializing platform accessory 'I2G_Actuator'...
/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:264
      throw new Error("Cannot add a bridged Accessory with the same UUID as another bridged Accessory: " + existing.UUID);
      ^

Error: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: e2a1545d-9063-47b4-ab6c-7079a4914e6f
    at Bridge.Accessory.addBridgedAccessory (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:264:13)
    at Server.<anonymous> (/usr/lib/node_modules/homebridge/lib/server.js:399:24)
    at /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:16:19
    at /usr/lib/node_modules/homebridge-tahoma/index.js:67:16
    at /usr/lib/node_modules/homebridge-tahoma/index.js:125:5
    at /usr/lib/node_modules/homebridge-tahoma/overkiz-api.js:176:5
    at Request.authCallback [as _callback] (/usr/lib/node_modules/homebridge-tahoma/overkiz-api.js:208:17)
    at Request.self.callback (/usr/lib/node_modules/homebridge-tahoma/node_modules/request/request.js:185:22)
    at emitTwo (events.js:126:13)
    at Request.emit (events.js:214:7)

I think is not a cached accessories issue like #22 (fresh install, up-to-date, Homebridge « accessories » and « persist » directories are empties).

I have found this previous issue #47, so I have replace the line 85 of the AbstractAccessory.js file located in « accessories » tahoma plugin folder by this code :

this.UUID = UUIDGen.generate(serial);

Same error…

[2018-11-14 20:22:19] Loaded config.json with 0 accessories and 1 platforms.
[2018-11-14 20:22:19] ---
[2018-11-14 20:22:20] Loaded plugin: homebridge-tahoma
homebridge-tahoma API version: 2.2
[2018-11-14 20:22:20] Registering platform 'homebridge-tahoma.Tahoma'
[2018-11-14 20:22:20] ---
[2018-11-14 20:22:20] Loading 1 platforms...
[2018-11-14 20:22:20] [Cozytouch] Initializing Tahoma platform...
[2018-11-14 20:22:21] [Cozytouch] Device type Pod unknown
[2018-11-14 20:22:21] [Cozytouch] [I2G_Actuator] device type: HeatingSystem, name: io:AtlanticElectricalHeaterWithAdjustableTemperatureSetpointIOComponent, protocol: io
[2018-11-14 20:22:21] [Cozytouch] New Device : I2G_Actuator ID:1468835#1
[2018-11-14 20:22:21] [Cozytouch] [IO (1468835#2)] device type: TemperatureSensor, name: io:TemperatureInCelciusIOSystemDeviceSensor, protocol: io
[2018-11-14 20:22:21] [Cozytouch] New Device : IO (1468835#2) ID:1468835#2
[2018-11-14 20:22:21] [Cozytouch] [IO (1468835#3)] device type: ContactSensor, name: io:ContactIOSystemDeviceSensor, protocol: io
[2018-11-14 20:22:21] [Cozytouch] New Device : IO (1468835#3) ID:1468835#3
[2018-11-14 20:22:21] [Cozytouch] [IO (1468835#4)] device type: OccupancySensor, name: io:OccupancyIOSystemDeviceSensor, protocol: io
[2018-11-14 20:22:21] [Cozytouch] New Device : IO (1468835#4) ID:1468835#4
[2018-11-14 20:22:21] [Cozytouch] [IO (1468835#5)] device type: ElectricitySensor, name: io:CumulatedElectricalEnergyConsumptionIOSystemDeviceSensor, protocol: io
[2018-11-14 20:22:21] [Cozytouch] New Device : IO (1468835#5) ID:1468835#5
[2018-11-14 20:22:21] [Cozytouch] [I2G_Actuator] device type: HeatingSystem, name: io:AtlanticElectricalHeaterWithAdjustableTemperatureSetpointIOComponent, protocol: io
[2018-11-14 20:22:21] [Cozytouch] New Device : I2G_Actuator ID:503269#1
[2018-11-14 20:22:21] [Cozytouch] [IO (503269#2)] device type: TemperatureSensor, name: io:TemperatureInCelciusIOSystemDeviceSensor, protocol: io
[2018-11-14 20:22:21] [Cozytouch] New Device : IO (503269#2) ID:503269#2
[2018-11-14 20:22:21] [Cozytouch] [IO (503269#3)] device type: ContactSensor, name: io:ContactIOSystemDeviceSensor, protocol: io
[2018-11-14 20:22:21] [Cozytouch] New Device : IO (503269#3) ID:503269#3
[2018-11-14 20:22:21] [Cozytouch] [IO (503269#4)] device type: OccupancySensor, name: io:OccupancyIOSystemDeviceSensor, protocol: io
[2018-11-14 20:22:21] [Cozytouch] New Device : IO (503269#4) ID:503269#4
[2018-11-14 20:22:21] [Cozytouch] [IO (503269#5)] device type: ElectricitySensor, name: io:CumulatedElectricalEnergyConsumptionIOSystemDeviceSensor, protocol: io
[2018-11-14 20:22:21] [Cozytouch] New Device : IO (503269#5) ID:503269#5
[2018-11-14 20:22:21] [Cozytouch] [I2G_Actuator] device type: HeatingSystem, name: io:AtlanticElectricalHeaterWithAdjustableTemperatureSetpointIOComponent, protocol: io
[2018-11-14 20:22:21] [Cozytouch] New Device : I2G_Actuator ID:7288378#1
[2018-11-14 20:22:21] [Cozytouch] [IO (7288378#2)] device type: TemperatureSensor, name: io:TemperatureInCelciusIOSystemDeviceSensor, protocol: io
[2018-11-14 20:22:21] [Cozytouch] New Device : IO (7288378#2) ID:7288378#2
[2018-11-14 20:22:21] [Cozytouch] [IO (7288378#3)] device type: ContactSensor, name: io:ContactIOSystemDeviceSensor, protocol: io
[2018-11-14 20:22:21] [Cozytouch] New Device : IO (7288378#3) ID:7288378#3
[2018-11-14 20:22:21] [Cozytouch] [IO (7288378#4)] device type: OccupancySensor, name: io:OccupancyIOSystemDeviceSensor, protocol: io
[2018-11-14 20:22:21] [Cozytouch] New Device : IO (7288378#4) ID:7288378#4
[2018-11-14 20:22:21] [Cozytouch] [IO (7288378#5)] device type: ElectricitySensor, name: io:CumulatedElectricalEnergyConsumptionIOSystemDeviceSensor, protocol: io
[2018-11-14 20:22:21] [Cozytouch] New Device : IO (7288378#5) ID:7288378#5
[2018-11-14 20:22:21] [Cozytouch] Initializing platform accessory 'I2G_Actuator'...
[2018-11-14 20:22:21] [Cozytouch] Initializing platform accessory 'IO (1468835#2)'...
[2018-11-14 20:22:21] [Cozytouch] Initializing platform accessory 'IO (1468835#3)'...
[2018-11-14 20:22:21] [Cozytouch] Initializing platform accessory 'IO (1468835#4)'...
[2018-11-14 20:22:21] [Cozytouch] Initializing platform accessory 'IO (1468835#5)'...
[2018-11-14 20:22:21] [Cozytouch] Initializing platform accessory 'I2G_Actuator'...
/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:264
      throw new Error("Cannot add a bridged Accessory with the same UUID as another bridged Accessory: " + existing.UUID);
      ^

Error: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: e2a1545d-9063-47b4-ab6c-7079a4914e6f
    at Bridge.Accessory.addBridgedAccessory (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:264:13)
    at Server.<anonymous> (/usr/lib/node_modules/homebridge/lib/server.js:399:24)
    at /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:16:19
    at /usr/lib/node_modules/homebridge-tahoma/index.js:67:16
    at /usr/lib/node_modules/homebridge-tahoma/index.js:125:5
    at /usr/lib/node_modules/homebridge-tahoma/overkiz-api.js:176:5
    at Request.authCallback [as _callback] (/usr/lib/node_modules/homebridge-tahoma/overkiz-api.js:208:17)
    at Request.self.callback (/usr/lib/node_modules/homebridge-tahoma/node_modules/request/request.js:185:22)
    at emitTwo (events.js:126:13)
    at Request.emit (events.js:214:7)

As you can see, I have uncomment the line 86 to log ’New Device’ : « this.displayName » and « serial ».
All « serial » seem unique… Come from « io:ControllerAddressState » (+1) of the CozyTouch API (thanks for your config reader tool)

Between the two try, the UUID is the same (e2a1545d-9063-47b4-ab6c-7079a4914e6f) as if the modification line 85 seems useless...

And I have no more idea to how I can investigate... ^^’

Could you please help me ?

I've got issue with Somfy Motion Sensor - it got detected, I can see it in the Home app, I think it was correctly working at the beginning but as soon as I created an automation it keeps saying Triggered. The sensor works fine in Somfy. I've been thinkering with homebridge for only couple of days but could help debugging with some guidance (I'm short on time for this sort of things).

Bonjour,

Je tente de faire apparaître les scénarios que j'ai crée dans l'application Connexoon dans HomeKit et j’obtiens cette erreur:

/usr/lib/node_modules/homebridge-tahoma/index.js:51
                                if (accessory.deviceURL.startsWith(baseURL))
                                                        ^

TypeError: Cannot read property 'startsWith' of undefined

J'ai mis un debug sur le chargement des scénarios pour essayer de comprendre d'où vient l'erreur:

[2018-6-16 00:35:03] [Connexoon] [Volet Velux] device type: RollerShutter, name: io:RollerShutterVeluxIOComponent, protocol: io
[2018-6-16 00:35:03] [Connexoon] [Volet Velux] core:NameState=Volet Velux
[2018-6-16 00:35:03] [Connexoon] [Volet Velux] core:PriorityLockTimerState=0
[2018-6-16 00:35:03] [Connexoon] [Volet Velux] core:StatusState=available
[2018-6-16 00:35:03] [Connexoon] [Volet Velux] core:RSSILevelState=88
[2018-6-16 00:35:03] [Connexoon] [Volet Velux] core:ClosureState=99
[2018-6-16 00:35:03] [Connexoon] [Volet Velux] core:OpenClosedState=open
[2018-6-16 00:35:03] [Connexoon] [DHWP Actuator] device type: WaterHeatingSystem, name: io:AtlanticDomesticHotWaterProductionIOComponent, protocol: io
[2018-6-16 00:35:03] [Connexoon] [IO (7190495#2)] device type: ElectricitySensor, name: io:DHWCumulatedElectricalEnergyConsumptionIOSystemDeviceSensor, protocol: io
[2018-6-16 00:35:03] [Connexoon] [Velux chambre] device type: Window, name: io:WindowOpenerVeluxIOComponent, protocol: io
[2018-6-16 00:35:03] [Connexoon] [Velux chambre] core:NameState=Velux ch. Gaspar
[2018-6-16 00:35:03] [Connexoon] [Velux chambre] core:PriorityLockTimerState=0
[2018-6-16 00:35:03] [Connexoon] [Velux chambre] core:StatusState=available
[2018-6-16 00:35:03] [Connexoon] [Velux chambre] core:RSSILevelState=88
[2018-6-16 00:35:03] [Connexoon] [Velux chambre] core:ClosureState=100
[2018-6-16 00:35:03] [Connexoon] [Velux chambre] core:OpenClosedState=closed
[2018-6-16 00:35:03] [Connexoon] Search extended : io://0808-0476-7160/7190495
[2018-6-16 00:35:03] [Connexoon] Device WaterHeatingSystem ignored
[2018-6-16 00:35:03] [Connexoon] Search extended : io://0808-0476-7160/7190495
[2018-6-16 00:35:03] [Connexoon] Device ElectricitySensor ignored
[2018-6-16 00:35:03] [Connexoon] Scenarios list:
[2018-6-16 00:35:03] [Connexoon] Scenario: { creationTime: 1529099293000,
  lastUpdateTime: 1529099293000,
  label: 'Window - A LA MAISON - user',
  metadata: '{"connexoonType" : "ConnexoonW","userId" : "user","metaDataVersion" : 3,"position" : 1,"deviceType" : "iOS","name" : "A LA MAISON","internalId" : "C14FB04F-6123-4B62-B4F5-56113EDE05A7", "when" : 1529099294, "presenceProtection" : "off", "lightProtection" : "on","thermicProtection" : "on","windowProtection" : "on", "timeProtection" : "on"}',
  shortcut: false,
  notificationTypeMask: 0,
  notificationCondition: 'NEVER',
  actions: 
   [ { deviceURL: 'io://0808-0476-7160/12852936',
       commands: [ { type: 1, name: 'setClosure', parameters: [ 99 ] } ] } ],
  oid: '0c7d956c-1355-42d2-854c-0e92327db0bf' }
[2018-6-16 00:35:03] [Connexoon] Scenario: -1
[2018-6-16 00:35:03] [Connexoon] Scenario: { creationTime: 1529099304000,
  lastUpdateTime: 1529099304000,
  label: 'Window - VACANCES - user',
  metadata: '{"connexoonType" : "ConnexoonW","userId" : "user","metaDataVersion" : 3,"position" : 3,"deviceType" : "iOS","name" : "VACANCES","internalId" : "E55C9708-110B-4E99-A24A-256526712AA1", "when" : 1529099305, "presenceProtection" : "on", "lightProtection" : "on","thermicProtection" : "on","windowProtection" : "on", "timeProtection" : "on"}',
  shortcut: false,
  notificationTypeMask: 0,
  notificationCondition: 'NEVER',
  actions: 
   [ { deviceURL: 'io://0808-0476-7160/12852936',
       commands: [ { type: 1, name: 'setClosure', parameters: [ 99 ] } ] } ],
  oid: '2326f2a4-0053-4902-b14b-fd87b5d62941' }
[2018-6-16 00:35:03] [Connexoon] Scenario: -1
[2018-6-16 00:35:03] [Connexoon] Scenario: { creationTime: 1529099244000,
  lastUpdateTime: 1529099244000,
  label: 'Window - ABSENT - user',
  metadata: '{"connexoonType" : "ConnexoonW","userId" : "user","metaDataVersion" : 3,"position" : 2,"deviceType" : "iOS","name" : "ABSENT","internalId" : "B69C3ED7-ECF6-4A41-B6EF-3AAF193CBE40", "when" : 1529099245, "presenceProtection" : "on", "lightProtection" : "on","thermicProtection" : "on","windowProtection" : "on", "timeProtection" : "on"}',
  shortcut: false,
  notificationTypeMask: 0,
  notificationCondition: 'NEVER',
  actions: 
   [ { deviceURL: 'io://0808-0476-7160/12852936',
       commands: [ { type: 1, name: 'open', parameters: [] } ] },
     { deviceURL: 'io://0808-0476-7160/944475',
       commands: [ { type: 1, name: 'close', parameters: [] } ] } ],
  oid: '4490cb2c-47ac-4531-a4db-8aea0a007012' }
[2018-6-16 00:35:03] [Connexoon] Scenario: -1
[2018-6-16 00:35:03] [Connexoon] Scenario: { creationTime: 1529099274000,
  lastUpdateTime: 1529099274000,
  label: 'Window - NE PAS ETRE DERANGE - user',
  metadata: '{"connexoonType" : "ConnexoonW","userId" : "user","metaDataVersion" : 3,"position" : 4,"deviceType" : "iOS","name" : "NE PAS ETRE DERANGE","internalId" : "2A8890FE-7DA2-4179-8F99-CF37E3B2839A", "when" : 1529099274, "presenceProtection" : "off", "lightProtection" : "on","thermicProtection" : "on","windowProtection" : "on", "timeProtection" : "off"}',
  shortcut: false,
  notificationTypeMask: 0,
  notificationCondition: 'NEVER',
  actions: 
   [ { deviceURL: 'io://0808-0476-7160/12852936',
       commands: [ { type: 1, name: 'setClosure', parameters: [ 99 ] } ] } ],
  oid: 'bd9d15b2-d281-40b9-b07e-513e34f1cebe' }
[2018-6-16 00:35:03] [Connexoon] Scenario: -1
[2018-6-16 00:35:03] [Connexoon] Initializing platform accessory 'Volet Velux'...
[2018-6-16 00:35:03] [Connexoon] Initializing platform accessory 'Velux chambre'...
[2018-6-16 00:35:03] [Connexoon] Initializing platform accessory 'Window - A LA MAISON - user'...
[2018-6-16 00:35:03] [Connexoon] Initializing platform accessory 'Window - VACANCES - user'...
[2018-6-16 00:35:03] [Connexoon] Initializing platform accessory 'Window - ABSENT - user'...
[2018-6-16 00:35:03] [Connexoon] Initializing platform accessory 'Window - NE PAS ETRE DERANGE - user'...



[2018-6-16 00:35:04] Homebridge is running on port 51826.
[2018-6-16 00:35:13] [Connexoon] [Volet Velux] core:NameState=Volet Velux
[2018-6-16 00:35:13] [Connexoon] [Volet Velux] core:PriorityLockTimerState=0
[2018-6-16 00:35:13] [Connexoon] [Volet Velux] core:StatusState=available
[2018-6-16 00:35:13] [Connexoon] [Volet Velux] core:RSSILevelState=88
[2018-6-16 00:35:13] [Connexoon] [Volet Velux] core:ClosureState=99
[2018-6-16 00:35:13] [Connexoon] [Volet Velux] core:OpenClosedState=open
[2018-6-16 00:35:13] [Connexoon] Search extended : io://0808-0476-7160/7190495
/usr/lib/node_modules/homebridge-tahoma/index.js:51
                                if (accessory.deviceURL.startsWith(baseURL))
                                                        ^

TypeError: Cannot read property 'startsWith' of undefined
    at TahomaPlatform.getAccessory (/usr/lib/node_modules/homebridge-tahoma/index.js:51:29)
    at TahomaPlatform.onStatesChange (/usr/lib/node_modules/homebridge-tahoma/index.js:142:26)
    at /usr/lib/node_modules/homebridge-tahoma/overkiz-api.js:129:55
    at /usr/lib/node_modules/homebridge-tahoma/overkiz-api.js:177:5
    at Request.authCallback [as _callback] (/usr/lib/node_modules/homebridge-tahoma/overkiz-api.js:209:17)
    at Request.self.callback (/usr/lib/node_modules/homebridge-tahoma/node_modules/request/request.js:185:22)
    at Request.emit (events.js:182:13)
    at Request.<anonymous> (/usr/lib/node_modules/homebridge-tahoma/node_modules/request/request.js:1157:10)
    at Request.emit (events.js:182:13)
    at IncomingMessage.<anonymous> (/usr/lib/node_modules/homebridge-tahoma/node_modules/request/request.js:1079:12)

On dirait que mon filtre du fichier config.json n'est pas appliqué aux scénarios :
"exclude": ["DHWP Actuator","IO (7190495#2)"]

Comment est-il possible de corriger cette erreur ?

Cordialement,
Ludovic

Hello,

Just tried this plugin since I've got an Tahoma.

Starting homebridge with the homebridge-tahoma plugin gives me this:

[2/5/2017, 1:30:56 PM] Loaded plugin: homebridge-tahoma
homebridge-tahoma API version: 2.1
[2/5/2017, 1:30:56 PM] Registering platform 'homebridge-tahoma.Tahoma'
[2/5/2017, 1:30:56 PM] ---
[2/5/2017, 1:30:56 PM] Loaded config.json with 0 accessories and 1 platforms.
[2/5/2017, 1:30:56 PM] ---
[2/5/2017, 1:30:56 PM] Loading 1 platforms...
[2/5/2017, 1:30:56 PM] [Tahoma] Initializing Tahoma platform...
[2/5/2017, 1:30:56 PM] [Tahoma] Init TaHoma platform
[2/5/2017, 1:30:56 PM] [Tahoma] Fetching Overkiz accessories...
[2/5/2017, 1:30:56 PM] [Tahoma] Log in Overkiz server...
[2/5/2017, 1:30:56 PM] [Tahoma] Device Pod ignored
[2/5/2017, 1:30:56 PM] [Tahoma] Device OnOff ignored
[2/5/2017, 1:30:56 PM] [Tahoma] Device OnOff ignored
[2/5/2017, 1:30:56 PM] [Tahoma] Device OnOff ignored
[2/5/2017, 1:30:56 PM] [Tahoma] Device OnOff ignored
[2/5/2017, 1:30:56 PM] [Tahoma] Device OnOff ignored
[2/5/2017, 1:30:56 PM] [Tahoma] Device OnOff ignored
[2/5/2017, 1:30:56 PM] [Tahoma] Device OnOff ignored
[2/5/2017, 1:30:56 PM] [Tahoma] Device OnOff ignored
[2/5/2017, 1:30:56 PM] [Tahoma] Device Light ignored
[2/5/2017, 1:30:56 PM] [Tahoma] Device OnOff ignored
[2/5/2017, 1:30:56 PM] [Tahoma] Device OnOff ignored
[2/5/2017, 1:30:56 PM] [Tahoma] Device OnOff ignored
[2/5/2017, 1:30:56 PM] [Tahoma] Device OnOff ignored

Seems like it can find some devices.

Can you point me where to go from here?

Thank you!

Hi,
Thank you for your great plugins.

I have RTS and IO operated blinds/curtains/projector screen.
It seems that RTS devices works correctly but only IO devices works reversely.
when I press "open" on homekit menu, it will "close", then "close" is working as "open"

Please kindly give me advice how to fixt it.
Thank you

Do you enter the username with @ symbol (email address)? And you put the whole thing in "[ ]" to make it work? I get an "Unable to login: Error: getaddrinfo ENOTFOUND undefined undefined:443" error when loading homebrige.

Hello,
First, thanks for the plugin you did a great job.

I get a z-wave module connect to a fan, a roof fan.
Actually, HomeKit get this z-wave as a light, i can change image, but always for light.
I was wondering if there is a way to get a fan icon fan.
Is it possible to get a field into the config.json file like:
"fan_ids": []
Or anything else.

Regards

Jerem

Hello,

First, thank you for this plugin, it's really awesome.
I have a tahoma box, and I can perfectly open/close my velux windows through Homekit. (although it's very offen reporting it as not answering, even though it's responding to open/close commands).

Could you help me (or can I help you) to integrate/test the HeatingSystem, because I have a Hitachi Air/Air cooling/heating system with three devices, and I really would like to try adding them. How can I test it? (I know lots of coding, just not so much in nodejs).
In the log I see Ignoring HitachiHeatingSystem, how can I activate it?

Hello,
I have the Homebridge installed on my Mac server. As the only plugin I wanted to use the plugin for TaHoma. I think the installation was successful.

When I start the Homegridge with the plugin installed I get the following error message:

> /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:264
>       throw new Error("Cannot add a bridged Accessory with the same UUID as another bridged Accessory: " + existing.UUID);
>       ^
> 
> Error: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: 866498a5-0cc7-4f3a-8307-a375efcecf16
>     at Bridge.Accessory.addBridgedAccessory (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:264:13)
>     at Server.<anonymous> (/usr/local/lib/node_modules/homebridge/lib/server.js:399:24)
>     at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:16:19
>     at /usr/local/lib/node_modules/homebridge-tahoma/index.js:67:16
>     at /usr/local/lib/node_modules/homebridge-tahoma/index.js:125:5
>     at /usr/local/lib/node_modules/homebridge-tahoma/overkiz-api.js:176:5
>     at Request.authCallback [as _callback] (/usr/local/lib/node_modules/homebridge-tahoma/overkiz-api.js:208:17)
>     at Request.self.callback (/usr/local/lib/node_modules/homebridge-tahoma/node_modules/request/request.js:185:22)
>     at Request.emit (events.js:182:13)
>     at Request.<anonymous> (/usr/local/lib/node_modules/homebridge-tahoma/node_modules/request/request.js:1161:10)

I searched TaHoma for duplicate names. A room had the same name as a window blind. I have adapted these names. After that I still get the error.

Also, I tried it to delete the folder "accessories" and "persist". Without success.

Can you help me to find the mistake?

Thank you, mahuch.

Hi! First of all thank you for this homebridge plugin! For me, it works like a charm, despite one thing:

I have several window blinds and two sun blinds. The sun blinds are treated like regular window blinds in Homekit, however, their direction is reversed. If I want to "open" the sun shades, I want the shades to go out / close. The Tahoma app handles this correctly, the homebridge plugin doesn't. It'd be great, if the plugin could "reverse" the open and close states for this device type.

Is the version of the Tahomo box relevant, or with other words - which Tahomo box do you use. Maybe a good add-on for the description.

Bonjour,

J'ai un nouveau bug au démarrage d'homebridge :

`Oct 18 10:18:43 rasphomebridge homebridge[1661]: /usr/lib/node_modules/homebridge-tahoma/accessories/HitachiHeatingSystem.js:209

Oct 18 10:18:43 rasphomebridge homebridge[1661]: var converted = parseInt(value.substring(0,value.length-3));
Oct 18 10:18:43 rasphomebridge homebridge[1661]: ^
Oct 18 10:18:43 rasphomebridge homebridge[1661]: TypeError: value.substring is not a function
Oct 18 10:18:43 rasphomebridge homebridge[1661]: at HitachiHeatingSystem.onStateUpdate (/usr/lib/node_modules/homebridge-tahoma/accessories/HitachiHeatingSystem.js:209:41)
Oct 18 10:18:43 rasphomebridge homebridge[1661]: at /usr/lib/node_modules/homebridge-tahoma/index.js:97:21
Oct 18 10:18:43 rasphomebridge homebridge[1661]: at /usr/lib/node_modules/homebridge-tahoma/overkiz-api.js:176:5
Oct 18 10:18:43 rasphomebridge homebridge[1661]: at Request.authCallback [as _callback] (/usr/lib/node_modules/homebridge-tahoma/overkiz-api.js:208:17)
Oct 18 10:18:43 rasphomebridge homebridge[1661]: at Request.self.callback (/usr/lib/node_modules/homebridge-tahoma/node_modules/request/request.js:185:22)
Oct 18 10:18:43 rasphomebridge homebridge[1661]: at emitTwo (events.js:106:13)
Oct 18 10:18:43 rasphomebridge homebridge[1661]: at Request.emit (events.js:194:7)
Oct 18 10:18:43 rasphomebridge homebridge[1661]: at Request. (/usr/lib/node_modules/homebridge-tahoma/node_modules/request/request.js:1161:10)
Oct 18 10:18:43 rasphomebridge homebridge[1661]: at emitOne (events.js:96:13)
Oct 18 10:18:43 rasphomebridge homebridge[1661]: at Request.emit (events.js:191:7)`

Hello, My sunscreen works fine with this plugin, only home kit indicates that the sunscreen is still 50% open while it is closed.

Someone how this comes

Bonne nouvelle,

ils parlent de Homekit pour mi-2018
https://service.somfy.com/downloads/fr_v4/somfy-cp_ces2018.pdf

Bonjour,

J'ai installé le plugin tahoma sur mon raspberry pi.
Les volets (RTS) fonctionnent parfaitement dans homekit.
Par contre les portes de garage et le portail ne fonctionnent pas.
J'ai les messages suivants :
[Portail] cycle[]
Error 400 Managed action group is invalid : No such command : cycle on device rts://1206-7815-0303/15711817 (rts:SlidingGateOpenerRTSComponent) (UNSPECIFIED_ERROR)

[Porte Garage 1] cycle[]
Error 400 Managed action group is invalid : No such command : cycle on device rts://1206-7815-0303/16721696 (rts:GarageDoorWithVentilationPositionRTSComponent) (UNSPECIFIED_ERROR)

[Porte Garage 2] cycle[]
Error 400 Managed action group is invalid : No such command : cycle on device rts://1206-7815-0303/16759743 (rts:GarageDoorWithVentilationPositionRTSComponent) (UNSPECIFIED_ERROR)

Merci pour votre aide.

Marc

Integrating the Plugin into Homebridge application results in the following error message:

Error: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: bf30e9f0-fbd3-4e4b-b514-026a854f0e98                                                                     
    at Bridge.Accessory.addBridgedAccessory (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:258:13)                                                            
    at Server. (/usr/local/lib/node_modules/homebridge/lib/server.js:377:24)                                                                                                         
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:16:19                                                                                                    
    at /usr/local/lib/node_modules/homebridge-tahoma/index.js:66:16                                                                                                                             
    at /usr/local/lib/node_modules/homebridge-tahoma/index.js:115:5                                                                                                                             
    at /usr/local/lib/node_modules/homebridge-tahoma/overkiz-api.js:175:5                                                                                                                       
    at Request.authCallback [as _callback] (/usr/local/lib/node_modules/homebridge-tahoma/overkiz-api.js:207:17)                                                                                
    at Request.self.callback (/usr/local/lib/node_modules/homebridge-tahoma/node_modules/request/request.js:186:22)                                                                             
    at Request.emit (events.js:159:13)                                                                                                                                                          
    at Request. (/usr/local/lib/node_modules/homebridge-tahoma/node_modules/request/request.js:1163:10)                                                                              
    at Request.emit (events.js:159:13)                                                                                                                                                          
    at IncomingMessage. (/usr/local/lib/node_modules/homebridge-tahoma/node_modules/request/request.js:1085:12)                                                                      
    at Object.onceWrapper (events.js:254:19)                                                                                                                                                    
    at IncomingMessage.emit (events.js:164:20)                                                                                                                                                  
    at endReadableNT (_stream_readable.js:1054:12)                                                                                                                                              
    at _combinedTickCallback (internal/process/next_tick.js:138:11)    

Somfy instead of io-homecontrol with tahoma, offers also the connexxoon box that is more simple of Tahoma respect to the function.
Is possible that the plugin works also with connexxon as for the tahoma?

Hello, thanks to all who have made the Homebridge and Tahoma code which I have running on my Raspberry Pi along with Sonos plugin too.

I have curtains in the bedroom and roman blinds in the living room which are both powered by Somfy Tahoma, and I can raise/lower and open/close using the Somfy Tahoma app. I've added the Tahoma plugin to my homebridge and immediately can see the living room blinds which work perfectly with Siri. However the bedroom curtains do not appear in the Home app on my iPhone.

Is there a limit to only one curtain/blind device? Or is there a known problem with curtains? Or perhaps I've done something wrong?

Very grateful for any help! Thank you!

Bonjour,

Je rencontre assez souvent le cas de mon volet qui se bloque lorsque la fenêtre Velux est ouverte entièrement.
J'aimerais être averti dans Homebridge comme c'est le cas si je lance l'application Connexoon. Il faut ouvrir l'application pour remarquer l'erreur, ce n'est pas pratique.

Voici ce que retourne l'API Tahoma au moment du blocage :

[{
	"execution": {
		"eventTime": 1530354922928,
		"owner": "[email protected]",
		"source": "mobile:connexoon",
		"endTime": 1530354937044,
		"effectiveStartTime": 1530354922928,
		"duration": 14116,
		"id": "5042f5ae-2e69-7448-5ca5-6448a99715f8",
		"label": "Volet Velux - Fermer - user",
		"executionType": "Immediate execution",
		"executionSubType": "MANUAL_CONTROL",
		"type": "Immediate execution - MANUAL_CONTROL",
		"failureType": "WHILEEXEC_BLOCKED_BY_HAZARD",
		"state": "FAILED",
		"commands": [{
			"deviceURL": "io://0808-0476-7160/12852936",
			"command": "close",
			"parameters": [],
			"rank": 0,
			"dynamic": false,
			"failureType": "WHILEEXEC_BLOCKED_BY_HAZARD",
			"state": "FAILED"
		}]
	}

1. On remarque qu'une erreur est bien retournée "failureType": "WHILEEXEC_BLOCKED_BY_HAZARD",
2. J'ai trouvé un moyen de lever des erreurs dans HomeKit et générer une alerte avec la Characteristic ObstructionDetected :

HMCharacteristicTypeObstructionDetected
Indicates whether the accessory has detected an obstruction—for example, an automatic garage door opener may have the ability to tell if something is blocking the door. The value is a boolean indicating whether an obstruction was detected.

J'ai fait un premier test en publiant le service et cela apparaît dans HomeKit

Voici un exemple

volet
        .getService(Service.WindowCovering)
        .setCharacteristic(Characteristic.ObstructionDetected, true);

Serait-il possible de vérifier le retour de l'API et lever une alerte ?

Cordialement
Ludovic

Bonjour Romain,

Je tourne sur un raspberry pi b3+ sous Raspbian lite.

Après avoir suivi le tutoriel, je démarre homebridge manuellement avec le plugin homebridge-Tahoma installé et configuré, la connection se fait, ça fonctionne, parfait.

Au passage merci beaucoup pour cette réalisation vraiment pratique et indispensable.

Je fais les manipulations qu'il faut pour obtenir le lancement de homebridge au démarrage du système avec systemd, je fais un sudo reboot, mais homebridge ne se lance pas.
Voici le log que j'obtiens

J'essaye d'aller me logger sur le site de Tahoma et sur l'appli, impossible.
Sur la page web j'ai le message "too many request, try later"
Sur l'appli, problème de mot de passe ou de compte d'utilisateur (qui sont pourtant les bons)

Si j'enlève les informations Tahoma dans le config.json, alors homebridge démarre bien au boot.

Y aurait-il une solution pour résoudre ce problème?
Si tu as besoins de testeurs ça serait avec plaisir.

Par avance merci.

Jérémie

Hi!
First I would like to thank you about this great Homebridge plugin.
I was finally able to integrate all our window blinds into Homekit :)

After this experience we decided also to integrate the garage door into Tahoma.
So we purchased a "Radio set RTS for retrofitting" from Somfy.
The device is working well via Tahoma and was also be recognized from your plugin.
Unfortunately the Homekit App shows always the status "open" or hangs at "refresh" and the door can not be controlled at all.

The Homebridge log shows the following error:
[Tahoma] Error 400 Managed action group is invalid : No such command : close on device io://1211-9928-2780/14694237 (io:CyclicGarageOpenerIOComponent) (UNSPECIFIED_ERROR)

It would be great if we could solve this issue.
Thank you very much and have a nice weekend!

Hi There!

It is really awesome plugin but I have problems with my Awning :( Guy who programmed this awning do this on the opposite way. I mean "down" button is to open and "up" is to close. They told me that is correct because this is only way to wind sensor work properly. What does it mean? When is open in real world is closed on HomeKit. So I can't open and close this stuff. Only what I can do is to set some % but it is also no correct (20% close is 80% open in real).

I try to change this values on Awning.js but it doesn't work properly. Please help me :)

Hi,

I have a Somfy Protect Alarm, which is visible in Tahoma (see picture) , but the plugin does not expose this alarm in homeKit.

I used the config item:
"Alarm": {
"STAY_ARM": "A,C",
"NIGHT_ARM": "B"
},
But this does not work with the Somfy protect.

Can you please help me get this working ?

Is it possible to do it at all? Would be awesome to have it as part of a Home app Scenario. Thanks!

I have some problems with Tahoma after install iOS 11 beta 4. When I try to use plugin (paste config to config file) HomeKit devices (home bridge ones) are not responding and Homebridge is blocked.

The strange thing is that this worked until last week. Other findings:

The Homebridge seems to run fine. It does not show any issues or errors (nothing in the error log, nothing in the log)
Rebooting iOS devices and the Bridge does not bring the devices back, still "No Response"
Disabling plugins does not change anything
Deleting the persistent folder and the accessories folder and restarting home bridge does not change anything
Reinstalling the homebridge and the plugins does not change anything
However, there is one combination that brings back the devices for a couple of minutes:

Stopping the homebridge
Removing the bridge from HomeKit
Deleting persistence and accessories
Starting the homebridge
Adding the bridge to HomeKit
This brings back all devices and accessories for a couple of minutes. After then they go grey again with the obvious "No Response".

I read on the other topic that this is plugin issue. Something is wrong in the code:

homebridge/homebridge#1390

Others plugins (when Tahoma plugin is off) works perfectly. One more thing... I don't know why but first time when I updated iOS only one device was "blocked" and unsupported by HomeKit. It was one screen the same like the others... No idea why?

Hi,

First, thanks for the job done!
For myself, the 6 RTS roller shutters works fine with your plugin.
That was my first goal, to get the roller shutters in homekit world. That's done!

I also have 5 IO radiators connected to the tahoma box.
They appears in homekit but in a strange way.
I could command the temperature I want with a slider (that is declared as a clim) but it does not work (got "no response" message when I tried to modify the temperature). In addition, the temperature shown on this clim accessory is 0.0°C...
I also got a temperature sensor (that seems to get the info from the radiator) and a controlled outlet (also coming from the radiator).

I have smart radiator valves (homekit compatible) and the temperature command and feedbacks is in the same accessory, here I have 2 different accessories for normally one only.

Any chance to get this modified to work properly?

Again, very good job for RTS Roller shutters!

Couple of weeks ago Tahoma API was down a couple of times and it wasn't clear why my accessories are not responding.
When the Tahoma API is down the accessories should be reported as not responding.
See homebridge/homebridge#1651

Dear developer and users,

at first a big thank you for developing this plugin.

I use Tahoma with Smoove Uno A / M io roller shutter controls for shutters without io. Smoove Uno A / M io does not know in which position the roller shutter has stopped. But Tahoma knows the last direction in which the roller shutter moved. My problem is the following. In the Home app the roller shutters are always closed. The roller shutters can only be raised. After the roller shutters have been raised, the Home app still shows status closed. Is there a way for asking Tahoma which direction was last approached? To use this information for open / closed status in the home app?

Esszimmer (RollerShutter,PositionableRollerShutterUno)

Commands:
close
delayedStopIdentify (1 paramètres)
down
getName
identify
my
open
refreshMemorized1Position
setClosure (1 paramètres)
setDeployment (1 paramètres)
setMemorized1Position (1 paramètres)
setName (1 paramètres)
setPosition (1 paramètres)
setSecuredPosition (1 paramètres)
startIdentify
stopIdentify
up
wink (1 paramètres)

States:
core:NameState
core:PriorityLockTimerState
core:TargetClosureState
core:StatusState
core:RSSILevelState

Regards, Oli

I'm running Homebridge on a Synology NAS and have the latestTahoma plugin installed, version v0.1.22
It's working fine with Homekit and Siri on my 6 venetian blinds and my garage door, all IO type devices
I also have 3 roller shutters (also IO devices) and there it seems okay using Siri, "open" really opens them and "close" is closing.
But in the Homekit app the status seems to be wrong.
In the open position the app tells me they are closed and touching he button therefore has no effect.
Using the slide I can close them and the app still tells me they are closed.
Touching the button now opens them, the button turns white and tells me they are opening.
After reaching the fully open position the button tells me they are closed again.
Could you advice me on what to do or edit in the Awnings.js file
Thanks in advance
Eric