Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Device Support Request] Salus SQ610 #571

Closed
benkuly opened this issue Nov 8, 2020 · 4 comments
Closed

[Device Support Request] Salus SQ610 #571

benkuly opened this issue Nov 8, 2020 · 4 comments
Labels
stale Issue is inactivate and might get closed soon

Comments

@benkuly
Copy link

benkuly commented Nov 8, 2020

Is your feature request related to a problem? Please describe.
The Salus SQ610 seems to stuck in connection-mode, when trying to connect to my zigbee network (ConBee II). I already contacted Salus and they said, that they use some proprietary protocol.
Home assistant does detect the cluster correctly and adds it to the device list, but because the SQ610 stays in connection mode it can't be used.

Describe the solution you'd like
Device support for Salus SQ610

Device signature - this can be acquired by removing the device from ZHA and pairing it again from the add devices screen. Be sure to add the entire content of the log panel after pairing the device to a code block below this line.

{
  "node_descriptor": "NodeDescriptor(byte1=1, byte2=64, mac_capability_flags=142, manufacturer_code=4216, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=0)",
  "endpoints": {
    "9": {
      "profile_id": 260,
      "device_type": "0x0301",
      "in_clusters": [
        "0x0000",
        "0x0003",
        "0x000a",
        "0x0201",
        "0x0b05",
        "0xfc00",
        "0xfc09"
      ],
      "out_clusters": [
        "0x0003",
        "0x0019",
        "0xfc00"
      ]
    }
  },
  "manufacturer": "SALUS",
  "model": "SQ610",
  "class": "zigpy.device.Device"
}

Additional context
In the update package of their gateway I found a config file with the following content:

{
	"zigbee_config_version": "190629",
	"zigbee_config": [
    {
		"model_identifier": "SQ610",
		"sleep_mode": "0",
	    "ota_timeout": "80",
	    "send_command_repeat_interval": "15",
	    "send_command_repeat_count": "3",
        "additional_support_templates_clusters":
        [
            {
                "endpoint": "9",
                "clusters":  "0xFC09"
            }
        ],		
		"targer_action": 
		[
			{
				"targer_name": "join_network",
				"command_single": 
				[
					{
						"interval_time": "8",
						"repeat_count": "5",
						"command": "00 00 00 00 09 00 41 7E E8 00 03 00 05 00",
						"receive": "00 00 00 00 09 00 02 7E 03 00"
					}   
				]
			},
			{
				"targer_name": "check_device_keep_alive",
				"timeout": "900",
				"command_single": 
				[
					{              
						"interval_time": "8",
						"repeat_count": "50",
						"command": "00 00 00 00 09 00 01 7E 05 00",
						"receive": "00 00 00 00 09 00 02 7E 05 00"
					}
				]
			}
		]
    }
  ] 
}   

Maybe this also can help to support more Salus devices. Otherwise we should warn users, that Salus uses a proprietary protocol and therefore can't be used.

@benkuly
Copy link
Author

benkuly commented Nov 8, 2020

This issue also approaches the problem: Koenkk/zigbee-herdsman-converters#1524

@benkuly
Copy link
Author

benkuly commented Nov 13, 2020

Is it possible with ZHA to send messages to the device directly after it connects? Mybe then I could expermient if the command above works to force the thermostat to stay connected.

@benkuly
Copy link
Author

benkuly commented Feb 12, 2021

Any help?

@github-actions
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale Issue is inactivate and might get closed soon label Aug 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issue is inactivate and might get closed soon
Projects
None yet
Development

No branches or pull requests

1 participant