Closed rahulpdev closed 2 months ago
Strangely enough i have a HK-DIM-A Candeo device that is behaving in the exact same way as your Samotech device.
Through messing about i have found the "correct" codes to turn the device on and off and it reflect in HA those being
Clusters OnOff (Endpoint id: 1, Id: 0x0006, Type: in)
Commands of the selected cluster on (id: 0x0001) for on
and
Commands of the selected cluster off (id: 0x0000) for off.
These work perfectly in HA when issued manually however rewriting the code is a little beyond me.
I am therefore wondering if these switching are using different Zcl versions meaning some work and some don't
Are you able to check the Zcl version of your working and non working versions?
Strangely enough i have a HK-DIM-A Candeo device that is behaving in the exact same way as your Samotech device.
Through messing about i have found the "correct" codes to turn the device on and off and it reflect in HA those being
Clusters OnOff (Endpoint id: 1, Id: 0x0006, Type: in)
Commands of the selected cluster on (id: 0x0001) for on
and
Commands of the selected cluster off (id: 0x0000) for off.
These work perfectly in HA when issued manually however rewriting the code is a little beyond me.
I am therefore wondering if these switching are using different Zcl versions meaning some work and some don't
Are you able to check the Zcl version of your working and non working versions?
I'm still fairly new to Home Assistant, what specifically do you mean by Zcl version? Thanks!
If you go into the device in ZHA and click on the 3 dots next to reconfigure it will show you the clusters and under the attributes drop down menu there is a zcl version you should be able to click read on and will give you a value.
If you go into the device in ZHA and click on the 3 dots next to reconfigure it will show you the clusters and under the attributes drop down menu there is a zcl version you should be able to click read on and will give you a value.
Ah, thanks. The Samotech reports a value of 8 and Candeo reports a value of 3.
If you go into the device in ZHA and click on the 3 dots next to reconfigure it will show you the clusters and under the attributes drop down menu there is a zcl version you should be able to click read on and will give you a value.
Ah, thanks. The Samotech reports a value of 8 and Candeo reports a value of 3.
Hmmm intresting, my new Candeo reports a value of 8 and has the exact same behaviour as your Samotech device. It seems at some point the HK-DIM-A devices have changed and thats broken the ZHA intergration? However if this was updated all the devices with 3 would maybe stop working. Might be fixed with a blue print or script but sadly that's getting outside my level of experience.
For completeness here is a comp of the Basic cluster:
So after messing about with this i found a workaround but it's far from ideal. It does seem that the device itself does inform HA that it's status has changed but this takes about 15mins after which the toggle in HA goes to the correct position which is just silly.
The work around for now is i have created an automation using the ZHA tool kit that polls the device for its status after the device is triggered this seems to require a 7 second delay to function.
So after messing about with this i found a workaround but it's far from ideal. It does seem that the device itself does inform HA that it's status has changed but this takes about 15mins after which the toggle in HA goes to the correct position which is just silly.
The work around for now is i have created an automation using the ZHA tool kit that polls the device for its status after the device is triggered this seems to require a 7 second delay to function.
Oh great! Could you share the yaml and I'll see if it works on the Samotech?
If you have zha-toolkit, you could try to call something like this to poll on/off:
service: zha_toolkit.attr_read
data:
ieee: light.your_light
endpoint: 1
cluster: 6
attribute: 0
Also, can you start a reconfiguration of the device and send a screenshot of what the reconfiguration dialog looks like?
@JohnHL12 Could you also start a reconfiguration of the device and send a screenshot of the reconfiguration dialog? (Settings -> Integrations -> ZHA: Configure -> Devices -> select your device -> Reconfigure button) (Also see if the issue changes after that)
Also, next to the reconfiguration button, there are three dots. Can you click that and then "Manage Zigbee device" -> Bindings tab -> select your Zigbee coordinator in the first drop-down and click "Bind". (See if the issue changes) And maybe try "unbind", wait 10 seconds, and then "bind" again and see if the issue changes.
(EDIT: Looks like your comment is gone -- not sure what happened.)
Also, you could also try to enable debug logs (can be done through the integrations page -> little bug symbol). Then reproduce the issue, stop debug logs (will prompt you to download a file) and then send them to me at: julian.tjj@proton.me
Oh great! Could you share the yaml and I'll see if it works on the Samotech?
@rahulpdev Just as @TheJulianJES said with the trigger just for ease of use, you need to add the took kit linked above first.
There will still be some flapping of the toggle as couldn't get it to work with a delay less than the 7 seconds but least it will settle in the correct place once the automation fires.
(@TheJulianJES Deleted my previous comment to add this in the correct format to enable copying )
alias: Dimmer testing
description: ""
trigger:
- platform: event
event_type: call_service
condition: []
action:
- delay:
hours: 0
minutes: 0
seconds: 7
milliseconds: 0
enabled: true
- service: zha_toolkit.attr_read
data:
ieee: light.shyugj_hk_dim_a_light
cluster: 6
attribute: 0
mode: single
@TheJulianJES have done the reconfigure before and doesn't make a difference to the way to device acts. Have also now tried unbinding and rebinding didn't do anything even after another reconfigure.
I'll run the debug logs and send them across
@TheJulianJES
I've sent the logs of attempting to turn the device on and then off.
I maybe wrong but the line
2023-03-05 09:00:32.094 DEBUG (MainThread) [zigpy.zcl] [0x499C:1:0x0006] Decoded ZCL frame: OnOff:Default_Response(command_id=1, status=<Status.UNSUP_CLUSTER_COMMAND: 129>)
does seem to me like there is an issue with the response from the device?
I seems that 0x499C
device doesn't accept the HA commands.
Are you sure that this is the same device?
You can check it from the Nwk
value, device view --> "Zigbee info"
@TheJulianJES I reconfigfured my Samotech device and returned the same results as @JohnHL12
I've got the same Samotech 323, and trying any of the OnOff commands in 'manage ZigBee device' I also get <Status.UNSUP_CLUSTER_COMMAND: 129>
@rahulpdev @JohnHL12 Can you please both advise the "#" number on the back of your Candeo modules? It appears that different "#" batches are performing differently with ZHA.
Just had a response from Samotech on this issue this morning.
Hello,
Yes, the issues are now fixed in the latest firmware that will be available next month. Please get back in touch by the end of next month.
Kind regards,
SAMOTECH
I unfortunately returned mine so can't supply anymore details
Hi guys - Eagerly following this... I currently have a candeo dimmer which was bought about a week ago... I'm looking at buying the samotechs as there cheaper and as mentioned above, samotech seem to be releasing a new firmware. Do we know if the candeo dimmers already have this firmware and whether samotech are playing catchup? Or is this a new firmware that neither candeo or samotech have had previously? It would be good to know the date stamp of this new samotech firmware as the newest up to now shows as (20220531) from the post above.
Heads up! I just got my dimmers back from samotech after a firmware upgrade, and now they're all working like a charm in ZHA. Hands down that's the best customer service around!
Before firmware upgrade:
After firmware upgrade:
@leomarkt that's frustrating as mine came back from Samotech a few weeks ago and still had the same problem. I ended up returning the devices that Samotech was good enough to give me a refund.
I've just had my reflashed by Samotech and they are spot on now. Very good customer service.
I originally had 2 problems.
Problem 1: dimmers worked fine from HA but if turned on physically from the switch, the ON state did not get recognised by HA unless you then turned the dimmer.
Problem 2: physically the dimmers worked fine but if operating from HA the states would toggle back. For example, light is on and you turn off on HA. Light switches off but state in HA toggles back on.
Both these issues are resolved with firmware 0x00000002
Here is some info showing what SW has what issues
My unit has the date_code
20220531 and I'm also experiencing Problem 2 so it seems there is no permanent fix for this device.
My unit has the
date_code
20220531 and I'm also experiencing Problem 2 so it seems there is no permanent fix for this device.
The fix is to get it reflashed with the latest firmware from Samotech.
is there no way to flash these devices at home? I am only in the UK for a few more days and would like to close this loop
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.
My issue is still happening on the latested version of HA and Z2M.
My issue is still happening on the latested version of HA and Z2M.
and what's your issue?
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.
Is your feature request related to a problem? Please describe. Samotech SM323 is recognised by ZHA but is not performing some basic functions correctly in Home Assistant.
When toggling the state of the light from Home Assistant, if the state is turned On the device turns On but the state reported in Home Assistant toggles itself back to Off. Home Assistant now considers the state of the device to be Off and so the device can't be turned Off by the control in Home Assistant.
The same thing happens the other way around, if the state is turned Off the device turns Off but the state reported in Home Assistant toggles itself back to On. Home Assistant now considers the state of the device to be On and so the device can't be turned On by the control in Home Assistant.
The physical device otherwise performs as normal, and the brightness control in Home Assistant also performs as normal.
Describe the solution you'd like Toggling the light control in Home Assistant results in the correct state persisting in Home Assistant.
Device signature
```yaml { "node_descriptor": "NodeDescriptor(logical_type=Diagnostic information
```yaml { "home_assistant": { "installation_type": "Home Assistant OS", "version": "2023.2.0", "dev": false, "hassio": true, "virtualenv": false, "python_version": "3.10.7", "docker": true, "arch": "aarch64", "timezone": "Europe/London", "os_name": "Linux", "os_version": "5.15.61-v8", "supervisor": "2023.01.1", "host_os": "Home Assistant OS 9.3", "docker_version": "20.10.18", "chassis": "embedded", "run_as_root": true }, "custom_components": { "hacs": { "version": "1.29.0", "requirements": [ "aiogithubapi>=22.10.1" ] }, "circadian_lighting": { "version": "2.1.3", "requirements": [] }, "watchman": { "version": "0.5.1", "requirements": [ "prettytable==3.0.0" ] }, "scheduler": { "version": "v0.0.0", "requirements": [] }, "better_thermostat": { "version": "1.0.1", "requirements": [] }, "deebot": { "version": "1.5.0", "requirements": [ "deebot-client==1.6.0", "numpy>=1.21.2" ] }, "alarmo": { "version": "v1.9.7", "requirements": [] }, "smartthinq_sensors": { "version": "0.26.1", "requirements": [ "pycountry>=20.7.3", "xmltodict>=0.12.0", "cchardet>=2.1.7" ] }, "kia_uvo": { "version": "2.6.0", "requirements": [ "hyundai_kia_connect_api==3.1.0" ] }, "octopus_energy": { "version": "5.4.0", "requirements": [] }, "spotcast": { "version": "v3.6.30", "requirements": [] }, "presence_simulation": { "version": "2.4", "requirements": [] }, "govee": { "version": "0.2.2", "requirements": [ "govee-api-laggat==0.2.2", "dacite==1.6.0" ] } }, "integration_manifest": { "domain": "zha", "name": "Zigbee Home Automation", "config_flow": true, "documentation": "https://www.home-assistant.io/integrations/zha", "requirements": [ "bellows==0.34.7", "pyserial==3.5", "pyserial-asyncio==0.6", "zha-quirks==0.0.92", "zigpy-deconz==0.19.2", "zigpy==0.53.0", "zigpy-xbee==0.16.2", "zigpy-zigate==0.10.3", "zigpy-znp==0.9.2" ], "usb": [ { "vid": "10C4", "pid": "EA60", "description": "*2652*", "known_devices": [ "slae.sh cc2652rb stick" ] }, { "vid": "1A86", "pid": "55D4", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus v2" ] }, { "vid": "10C4", "pid": "EA60", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus" ] }, { "vid": "10C4", "pid": "EA60", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*zigstar*", "known_devices": [ "ZigStar Coordinators" ] }, { "vid": "1CF1", "pid": "0030", "description": "*conbee*", "known_devices": [ "Conbee II" ] }, { "vid": "10C4", "pid": "8A2A", "description": "*zigbee*", "known_devices": [ "Nortek HUSBZB-1" ] }, { "vid": "0403", "pid": "6015", "description": "*zigate*", "known_devices": [ "ZiGate+" ] }, { "vid": "10C4", "pid": "EA60", "description": "*zigate*", "known_devices": [ "ZiGate" ] }, { "vid": "10C4", "pid": "8B34", "description": "*bv 2010/10*", "known_devices": [ "Bitron Video AV2010/10" ] } ], "codeowners": [ "@dmulcahey", "@adminiuga", "@puddly" ], "zeroconf": [ { "type": "_esphomelib._tcp.local.", "name": "tube*" }, { "type": "_zigate-zigbee-gateway._tcp.local.", "name": "*zigate*" }, { "type": "_zigstar_gw._tcp.local.", "name": "*zigstar*" }, { "type": "_slzb-06._tcp.local.", "name": "slzb-06*" } ], "dependencies": [ "file_upload" ], "after_dependencies": [ "onboarding", "usb", "zeroconf" ], "iot_class": "local_polling", "loggers": [ "aiosqlite", "bellows", "crccheck", "pure_pcapy3", "zhaquirks", "zigpy", "zigpy_deconz", "zigpy_xbee", "zigpy_zigate", "zigpy_znp" ], "is_built_in": true }, "data": { "ieee": "**REDACTED**", "nwk": 24633, "manufacturer": "Samotech", "model": "HK_DIM_A", "name": "Samotech HK_DIM_A", "quirk_applied": false, "quirk_class": "zigpy.device.Device", "manufacturer_code": 4107, "power_source": "Mains", "lqi": 144, "rssi": -64, "last_seen": "2023-02-27T20:34:42", "available": true, "device_type": "Router", "signature": { "node_descriptor": "NodeDescriptor(logical_type=Additional logs
``` Paste any additional debug logs here. Don't remove the extra line breaks outside the ``` marks. ```Additional context Add any other context or screenshots about the feature request here.
The device displays in Home Assistant as HK_DIM_A by Samotech. I also have installed in Home Assistant a HK_DIM_A by Candeo that is a physically identical device and that works perfectly.