Somfy RTS bug with dzvents 1.1?

Easy to use, 100% Lua-based event scripting framework.

Moderator: leecollings

Post Reply
EddyG
Posts: 1042
Joined: Monday 02 November 2015 5:54
Target OS: -
Domoticz version:

Somfy RTS bug with dzvents 1.1?

Post by EddyG »

I have 5 Somfy RTS motors programmed and running for more than a year now on my Domoticz 3.5877 with DzVents with 1.1 (Production Raspberry Pi)
I had a 6th button already installed for a future RTS motor. That button had already been set with Somfy ID 3.
I now have the 6th RTS motor , so I programmed it with a new button with that same Somfy ID. That did the trick, and I got a message from Domoticz that that ID was already programmed, so I canceled.
The previous installed 6th Button works fine in Domoticz, Up, Down and Stop.
So in Domoticz with my RFXCOM everything works fine, all 6 RTS motors. Hand controllers work fine too.
Now I am facing a challenge.
I had some scripts running close the roller shutters at night and opening them at the morning, etc.
That script worked perfect. I changed the name of the 6th Button to something else and changed the script accordingly.
The script still works fine except for the 6th roller shutter. In all kinds of logging I see the the script executes fine.
Where normaly on all 5 buttons I see after the scripts executes, logging, something like: (RFXCOM) RFY (Achterdeur)
But with the 6th button, no response from Domoticz.
I looked at the API output from working buttons and the malfunctional, the is NO difference except, name time etc...
I looked in the Domoticz database and see NO difference between the 5 working and the malfunctional buttons.
Normal API command work fine too on all buttons, like in Domoticz self.

I am out of ideas :cry: Does anyone have a suggestion? What kind of command is Domoticz sending to the RFXCOM?
What is dzVents sending to Domoticz?
EddyG
Posts: 1042
Joined: Monday 02 November 2015 5:54
Target OS: -
Domoticz version:

Re: Somfy RTS bug with dzvents 1.1?

Post by EddyG »

FOUND IT!!! :D :D :D
There was an (unused) group with the same name, so I missed that one.
May be there should be a check and warning when creating devices with the same name.
In this case there was type RFY and Group with the same name.
Name change did the trick. :D
dannybloe
Posts: 1355
Joined: Friday 29 August 2014 11:26
Target OS: Raspberry Pi / ODroid
Domoticz version:
Location: Ermelo
Contact:

Re: Somfy RTS bug with dzvents 1.1?

Post by dannybloe »

The problem is that that takes extra cpu cycles and I guess it will give people a lot of warnings as I suspect they all have double names somewhere. But I'll see if I can put in some warning.
Creator dzVents - RPi3, loads of zwave devices, esp8266, evohome.
EddyG
Posts: 1042
Joined: Monday 02 November 2015 5:54
Target OS: -
Domoticz version:

Re: Somfy RTS bug with dzvents 1.1?

Post by EddyG »

In Domoticz double names are no problem, because Type and subtypes are known to the program when you click on something.
In dzVents I assume you work only with names?
dannybloe
Posts: 1355
Joined: Friday 29 August 2014 11:26
Target OS: Raspberry Pi / ODroid
Domoticz version:
Location: Ermelo
Contact:

Re: Somfy RTS bug with dzvents 1.1?

Post by dannybloe »

Names or ids. You can always use the id of the device (domoticz.devices[123]) when you want to keep using double names. However, when issuing commands back to Domoticz you may still have undesired effects as the command often includes the name of the device. So, it's not only dzVents that needs a unique identifier for the device but Domoticz may as well.
Better make sure that your devices are uniquely named withing the device collection (and the same applies for variables, scenes and groups of course).
Creator dzVents - RPi3, loads of zwave devices, esp8266, evohome.
Post Reply

Who is online

Users browsing this forum: Google [Bot] and 1 guest