Homey Community Forum

Stop 2nd light being triggered by switching on another light switch

Hi

A light in my house “Light 2” has recently started switching itself on when another light “Light 1” is switched on. There isn’t a flow triggering it, so I’m wondering if there is some kind direct paring or grouping that has happened.

It’d appreciate it if somebody could help we work out why, and how to get it stop happening.

These are the settings for is “Light 2”, which is coming on when it shouldn’t:

**Light 2**
Property	Value
ID	44d79d75-3641-406f-9a0b-6bbfd2afc085
Class	light
Driver	homey:app:com.fibaro — FGD-212
Ready	Yes
Available	Yes
Warning	No
Custom icon	Yes

Settings
Key	Value
minimum_brightness	1
maximum_brightness	70
dimming_step_auto	1
time_dimming_step_auto	1
dimming_step_manual	3
time_dimming_step_manual	3
save_state	true
timer_functionality	0
force_auto_calibration	"1"
forced_brightness_level	30
switch_type	"2"
double_click	true
force_no_dim	false
soft_start	"1"
3_way_switch	false
switch_s1_and_s2	false
scene_activation	true
watt_report	10
watt_interval	3600
kwh_report	0.1
self_measurement	false
zw_node_id	"41"
zw_manufacturer_id	"271"
zw_product_type_id	"258"
zw_product_id	"4096"
zw_secure	"✓"
zw_battery	"⨯"
zw_device_class_basic	"BASIC_TYPE_ROUTING_SLAVE"
zw_device_class_generic	"GENERIC_TYPE_SWITCH_MULTILEVEL"
zw_device_class_specific	"SPECIFIC_TYPE_POWER_SWITCH_MULTILEVEL"
zw_firmware_id	"274"
zw_wakeup_interval	0
zw_group_1	"1"
zw_group_2	""
zw_group_3	""
zw_group_4	""
zw_group_5	""
zw_configuration_value	""

Capabilities
Capability	Type	Value	Edit value	Last Updated
onoff	boolean	true	
3 minutes ago
dim	number	0.01	
0
2 minutes ago
measure_power	number	3.3		2 minutes ago
meter_power	number	37.25		10 minutes ago

…and these are the settings for Light 1, which seems to be triggering light 2, when it’s turned on

|Property|Value|
| --- | --- |
|ID|3fe36379-9fb0-4351-a7a3-3463525be254|
|Class|light|
|Driver|homey:app:com.fibaro — FGRGBWM-441|
|Ready|Yes|
|Available|Yes|
|Warning|No|
|Custom icon|Yes|

###### Settings

|Key|Value|
| --- | --- |
|strip_type|"rgbw"|
|rgbw_white_temperature|true|
|white_temperature|"ww"|
|calibrate_white|0|
|white_saturation|10|
|transition_mode|"0"|
|mode1_steps|1|
|mode1_time|10|
|mode2_range|"64"|
|mode2_transition_time|3|
|maximum_brightness|255|
|minimum_brightness|2|
|input_config_1|"1"|
|input_config_2|"1"|
|input_config_3|"1"|
|input_config_4|"1"|
|save_state|true|
|input_threshold|0.5|
|watt_report_interval|30|
|kwh_threshold|0.1|
|color_pallet|"accurate"|
|zw_node_id|"197"|
|zw_manufacturer_id|"271"|
|zw_product_type_id|"2304"|
|zw_product_id|"4096"|
|zw_secure|"⨯"|
|zw_battery|"⨯"|
|zw_device_class_basic|"BASIC_TYPE_ROUTING_SLAVE"|
|zw_device_class_generic|"GENERIC_TYPE_SWITCH_MULTILEVEL"|
|zw_device_class_specific|"SPECIFIC_TYPE_POWER_SWITCH_MULTILEVEL"|
|zw_firmware_id|""|
|zw_wakeup_interval|0|
|zw_group_1|""|
|zw_group_2|""|
|zw_group_3|""|
|zw_group_4|""|
|zw_group_5|""|
|zw_configuration_value|"14,2,0x9999"|

###### Capabilities

|Capability|Type|Value|Edit value|Last Updated|
| --- | --- | --- | --- | --- |
|onoff|boolean|false||12 hours ago|
|dim|number|0.9||12 hours ago|
|light_hue|number|0||12 hours ago|
|light_saturation|number|1||12 hours ago|
|light_temperature|number|null||12 hours ago|
|light_mode|enum|color||7 months ago|
|measure_power|number|39.4||4 days ago|
|meter_power|number|126.12||12 hours ago|
|measure_voltage.input1|number|0||4 days ago|
|measure_voltage.input2|number|0||12 hours ago|
|measure_voltage.input3|number|0||2 weeks ago|
|measure_voltage.input4|number|0||12 hours ago|

Really, nobody knows the answer? Or even how to diagnose?

Have you tried restarting the fibaro app or PTP?

You supply very little context information. Just settings don’t make clear in what situation it happens, nor what the circumstances are. So since the chances that someone else experiences exactly the same are very small, i think it isn’t very strange that no one has a suitable answer yet.
Only thing i can think of is that you have the wrong switch selected in your flow or that you selected something (i think it is called scene activation or something like that) when you added the FGD-212 switch.

@Gas Yes I’ve tried retarting App & Homey

@PetervdK What other context information would be helpful. It happens every time, no special context. One light on makes another light come on - why would that be when they are not in any flow. Scene activation is off for both devices

You say it’s not a flow triggering it, but afaik one light can’t switch on another light without a command. Also, the first light doesn’t switch on spontaneously, does it?
So what does? Manual? Button? Google Home? Lux sensor? Motion sensor?
Do you use zones or groups? Heimdal? All relevant information imho.
But i suppose guessing in the end might offer a solution.

You say it’s not a flow triggering it, but afaik one light can’t switch on another light without a command.

That’s the point. There is no flow, for either. That’s why I’m asking here. I think it might be direct z-wave thing that has become corrupted or something or a bug from an update, as it wasn’t set-up that way and for over a year the behavior wasn’t happening.

You say it’s not a flow triggering it, but afaik one light can’t switch on another light without a command. Also, the first light doesn’t switch on spontaneously, does it?
So what does? Manual? Button?

Button on Light 1 switches on Light 1 and then after about 3/4 of a second Light 2 comes on.

Maybe it helps when you exclude and re-include one or both the devices? Just guessing?

You sure about that, iam just guessing also

Knipselsdf

1 Like

That’s interesting, the settings in the app show it as off

I don’t know anything about scenes and have never set one up. Where would I find where this mystery scene might be?

maybe try to set it ON and there after OFF again?

Ok, that makes more sense.

So if you press the button on switch named “Light 1”, being a Fibaro RGBW controller, it switches on a wired lamp. Then it also triggers a switch called “Light 2”, which is a Fibaro dimmer with a wired lamp behind it. Right so far?
And you say that there is absolutely no flow on Homey that triggers either one of the switches, right?

Then it looks like a dedicated zw_group association between the 2 switches. It seems switch 1 is associated with group 1, but according to the settings all group values for Light 2 are empty.

So it must be something with the “scene” setting or the group values are not displaying correctly or there are flows in place or there is some wire crossover between the switches. Or maybe it is a “hotel” switch situation (1 light on 2 switches)?

I have no experience with direct association or scene modes with Fibaro, so maybe someone else has any ideas left?

So if you press the button on switch named “Light 1”, being a Fibaro RGBW controller, it switches on a wired lamp. Then it also triggers a switch called “Light 2”, which is a Fibaro dimmer with a wired lamp behind it. Right so far?

Right

And you say that there is absolutely no flow on Homey that triggers either one of the switches, right?

Correct. The only flow in which both appear is to turn off all ground floor lights at 1am .

Then it looks like a dedicated zw_group association between the 2 switches. It seems switch 1 is associated with group 1, but according to the settings all group values for Light 2 are empty.

Correct

So it must be something with the “scene” setting or the group values are not displaying correctly or there are flows in place or there is some wire crossover between the switches. Or maybe it is a “hotel” switch situation (1 light on 2 switches)?

Light 2 is physically operated / connected to 3 switches (only one fibaro dimmer), but not the same as Light 1. Light 1 has only one switch.

I have no experience with direct association or scene modes with Fibaro, so maybe someone else has any ideas left?

Nor me - I’ve never knowingly set any.

But did you already try @JPe4619’s proposal?
And maybe take a close look at the settings of both switches via the /device/advanced settings menu in the app, particularly to the values of the scene- and zw_groups…

Well, homey updated to 3.2.0 made it go away. Now the lights work properly without triggering any other light, as they did originally