[Reactor] Bug when sending MQTT boolean payloads

[therealdb]

Hi @toggledbits,

I'm not sure if it's a bug or something, but I have a lot of Fibaro Double Switch (FGS223) as follows.

In the example, it's zwavejs>65-2:

energy_sensor.units="kWh"
energy_sensor.value=0.21
power_sensor.units="W"
power_sensor.value=0
power_switch.state=false
x_debug.dt={"entity_class":"Switch","match":"deviceClass.generic.key=16","capabilities":["power_switch","toggle"],"primary_attribute":"power_switch.state"}
x_zwave_values.Binary_Switch_currentValue=false
x_zwave_values.Binary_Switch_targetValue=false
x_zwave_values.Meter_reset=null
x_zwave_values.Meter_value_65537=0.21
x_zwave_values.Meter_value_66049=0
zwave_device.capabilities=[37,50]
zwave_device.endpoint=2
zwave_device.failed=null
zwave_device.impl_sig="23326:1:22315:1"
zwave_device.manufacturer_info=null
zwave_device.node_id=65
zwave_device.version_info=null

When operating endpoint 2, it's triggered endpoint 1. Endpoint 1 is fine. This is causing a lot of troubles, as you may imagine.

Also, endpoint 0 is not really a switch, and the associated actions are not doing anything at all. Maybe these could be removed. Also, I see battery_maintenance and power_source capabilities, all with null values.

battery_maintenance.charging=null
battery_maintenance.rechargeable=false
battery_maintenance.replace=false
battery_maintenance.state=null
heat_detector.state=false
power_source.source=null
power_switch.state=null
x_debug.dt={"entity_class":"Switch","match":"deviceClass.generic.key=16","capabilities":["power_switch","toggle"],"primary_attribute":"power_switch.state","description":"Double Switch 2","model":"FGS223","default_name":"Double Switch 2","manufacturerId":271,"productType":515,"productId":4096}
x_zwave_values.Central_Scene_scene_001=null
x_zwave_values.Central_Scene_scene_002=null
x_zwave_values.Central_Scene_slowRefresh=null
x_zwave_values.Configuration_First_Channel_Energy_Reports_Threshold=100
x_zwave_values.Configuration_First_Channel_Operating_Mode=0
x_zwave_values.Configuration_First_Channel_Power_Reports_Minimum_Time_Between_Reports=10
x_zwave_values.Configuration_First_Channel_Power_Reports_Threshold=20
x_zwave_values.Configuration_First_Channel_Pulse_Time_for_Blink_Mode=5
x_zwave_values.Configuration_First_Channel_Reaction_to_Key_S1_for_Delay_Auto_ON_OFF_Modes=0
x_zwave_values.Configuration_First_Channel_Time_Parameter_for_Delay_Auto_ON_OFF_Modes=50
x_zwave_values.Configuration_General_Purpose_Alarm_Response=3
x_zwave_values.Configuration_Include_Consumption_By_Device_Itself_in_Reports=0
x_zwave_values.Configuration_Input_Button_Switch_Configuration=2
x_zwave_values.Configuration_Key_S1_Associations_Double_Click_Value_Sent=99
x_zwave_values.Configuration_Key_S1_Associations_Send_OFF_With_Single_Click_2=0
x_zwave_values.Configuration_Key_S1_Associations_Send_ON_With_Single_Click_1=0
x_zwave_values.Configuration_Key_S1_Associations_Send_When_Double_Clicking_8=0
x_zwave_values.Configuration_Key_S1_Associations_Send_When_Holding_and_Releasing_4=0
x_zwave_values.Configuration_Key_S1_Associations_Switch_OFF_Value_Sent=0
x_zwave_values.Configuration_Key_S1_Associations_Switch_ON_Value_Sent=255
x_zwave_values.Configuration_Key_S1_Send_Scenes_When_Held_Down_and_Released_8=1
x_zwave_values.Configuration_Key_S1_Send_Scenes_When_Pressed_1_Time_1=1
x_zwave_values.Configuration_Key_S1_Send_Scenes_When_Pressed_2_Times_2=1
x_zwave_values.Configuration_Key_S1_Send_Scenes_When_Pressed_3_Times_4=1
x_zwave_values.Configuration_Key_S2_Associations_Double_Click_Value_Sent=99
x_zwave_values.Configuration_Key_S2_Associations_Send_OFF_With_Single_Click_2=0
x_zwave_values.Configuration_Key_S2_Associations_Send_ON_With_Single_Click_1=0
x_zwave_values.Configuration_Key_S2_Associations_Send_When_Double_Clicking_8=0
x_zwave_values.Configuration_Key_S2_Associations_Send_When_Holding_and_Releasing_4=0
x_zwave_values.Configuration_Key_S2_Associations_Switch_OFF_Value_Sent=0
x_zwave_values.Configuration_Key_S2_Associations_Switch_ON_Value_Sent=255
x_zwave_values.Configuration_Key_S2_Send_Scenes_When_Held_Down_and_Released_8=1
x_zwave_values.Configuration_Key_S2_Send_Scenes_When_Pressed_1_Time_1=1
x_zwave_values.Configuration_Key_S2_Send_Scenes_When_Pressed_2_Times_2=1
x_zwave_values.Configuration_Key_S2_Send_Scenes_When_Pressed_3_Times_4=1
x_zwave_values.Configuration_Periodic_Active_Power_Reports=3600
x_zwave_values.Configuration_Periodic_Energy_Reports=3600
x_zwave_values.Configuration_Report_During_Blink_Mode=0
x_zwave_values.Configuration_Second_Channel_Energy_Reports_Threshold=100
x_zwave_values.Configuration_Second_Channel_Operating_Mode=0
x_zwave_values.Configuration_Second_Channel_Power_Reports_Minimum_Time_Between_Reports=10
x_zwave_values.Configuration_Second_Channel_Power_Reports_Threshold=20
x_zwave_values.Configuration_Second_Channel_Pulse_Time_for_Blink_Mode=5
x_zwave_values.Configuration_Second_Channel_Reaction_to_Key_S2_for_Delay_Auto_ON_OFF_Modes=0
x_zwave_values.Configuration_Second_Channel_Time_Parameter_for_Delay_Auto_ON_OFF_Modes=50
x_zwave_values.Configuration_Send_Secure_Commands_to_2nd_Association_Group_1=1
x_zwave_values.Configuration_Send_Secure_Commands_to_3rd_Association_Group_2=1
x_zwave_values.Configuration_Send_Secure_Commands_to_4th_Association_Group_4=1
x_zwave_values.Configuration_Send_Secure_Commands_to_5th_Association_Group_8=1
x_zwave_values.Configuration_Smoke_CO_or_CO2_Alarm_Response=3
x_zwave_values.Configuration_State_After_Power_Failure=1
x_zwave_values.Configuration_Temperature_Alarm_Response=1
x_zwave_values.Configuration_Time_of_Alarm_State=600
x_zwave_values.Configuration_Water_Flood_Alarm_Response=2
x_zwave_values.Manufacturer_Specific_manufacturerId=271
x_zwave_values.Manufacturer_Specific_productId=4096
x_zwave_values.Manufacturer_Specific_productType=515
x_zwave_values.Notification_Heat_Alarm_Heat_sensor_status=0
x_zwave_values.Notification_Power_Management_Over_current_status=0
x_zwave_values.Notification_alarmLevel=null
x_zwave_values.Notification_alarmType=null
x_zwave_values.Protection_exclusiveControlNodeId=null
x_zwave_values.Protection_local=0
x_zwave_values.Protection_rf=0
x_zwave_values.Protection_timeout=null
x_zwave_values.Version_firmwareVersions=["3.2"]
x_zwave_values.Version_hardwareVersion=3
x_zwave_values.Version_libraryType=3
x_zwave_values.Version_protocolVersion="4.5"
zwave_device.capabilities=[91,112,113,114,117,134]
zwave_device.endpoint=0
zwave_device.failed=false
zwave_device.generic_class="Binary Switch"
zwave_device.impl_sig="23326:1:22315:1"
zwave_device.is_beaming=false
zwave_device.is_listening=true
zwave_device.is_routing=true
zwave_device.is_secure=false
zwave_device.manufacturer_info=[271,515,4096]
zwave_device.max_data_rate=null
zwave_device.node_id=65
zwave_device.specific_class="Binary Power Switch"
zwave_device.status=4
zwave_device.status_text="alive"
zwave_device.version_info=[null,"3.2"]

Thanks.

[toggledbits]

There's another device (Zooz) with a similar report. I'm looking into this now that I'm back from my trip.

[tamorgen]

@toggledbits said in [ZwaveJS] Problems with endpoints and Fibaro Double Switch 2 (FGS223):

There's another device (Zooz) with a similar report. I'm looking into this now that I'm back from my trip.

@toggledbits
Thanks for the reminder. I haven't gotten you the correct ZWaveJS logs. I got sidetracked. Let me see if I can get those for you on that thread.

[therealdb]

@toggledbits thanks! I've found other quirks, let me know if you want a separate report. Minor things, but differing from Vera's. The most annoying one is position not working and me having to rewrite 100+ rules to use dimming for roller shutters.

[toggledbits]

Each issue has to be case by case. Let's hit them one at a time. I just pushed 24232 of ZWaveJSController as an interim build; I'll do an announced build after we've worked through everything. Check 24232 and see if it improves your double-switch behavior first. Let me know here. New thread for the shades, please.

[therealdb]

yup, I'll post a new one. This build seems to be OK with this particular problem, thanks!

[therealdb]

I don't know if it's related to this, because I'm running the controller since 12 hours, but after the update my Fibaro Door Window Sensor 2 (FGDW002) is always reporting as open, even if

x_zwave_values.Notification_Access_Control_Door_state=23
x_zwave_values.Notification_Access_Control_Door_state_simple=23

which means that the door is closed. It was working before and I could downgrade to test, if necessary.

[toggledbits]

Yeah, that's related to recent changes Z-Wave JS made for similar devices. They are now supporting a command class they didn't before. Start a new thread for it, and I'll run it down.