ZHA Skyconnect Hama Thermostat TS0601 by _TZE200_h4cgnbzg
The problem
I bought Hama Thermostats which I integrated into Home Assistant with Skyconnect and ZHA. Connecting it to Home Assistant was no issue. Trying to change the temperature on the thermostat, does not work though. When changing the temperature on the thermostat manually, Home Assistant dectects the change almost instantly. I read a lot about different quirks for the device but I did not understand, how to deploy those.
Device info
TS0601 by _TZE200_h4cgnbzg
Quirk: zhaquirks.tuya.ts0601_trv_sas.Thermostat_TZE200_c88teujp

What version of Home Assistant Core has the issue?
Home Assistant 2023.2.1
What was the last working version of Home Assistant Core?
Never worked.
What type of installation are you running?
Home Assistant OS
Integration causing the issue
ZHA (Zigbee Home Assistant)
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
`2023-02-04 16:37:16.955 DEBUG (MainThread) [homeassistant.components.zha.core.device] 0x7147: Device seen - marking the device available and resetting counter
2023-02-04 16:37:16.956 DEBUG (MainThread) [homeassistant.components.zha.core.device] 0x7147: Update device availability - device available: True - new availability: True - changed: False
2023-02-04 16:37:16.963 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received getValue: [<EzspStatus.SUCCESS: 0>, b'\xf1']
2023-02-04 16:37:16.965 DEBUG (MainThread) [bellows.zigbee.application] Free buffers status EzspStatus.SUCCESS, value: 241
2023-02-04 16:37:16.965 DEBUG (MainThread) [bellows.zigbee.application] ezsp_counters: [MAC_RX_BROADCAST = 1102, MAC_TX_BROADCAST = 3903, MAC_RX_UNICAST = 42263, MAC_TX_UNICAST_SUCCESS = 1194, MAC_TX_UNICAST_RETRY = 517, MAC_TX_UNICAST_FAILED = 61, APS_DATA_RX_BROADCAST = 34, APS_DATA_TX_BROADCAST = 34, APS_DATA_RX_UNICAST = 677, APS_DATA_TX_UNICAST_SUCCESS = 605, APS_DATA_TX_UNICAST_RETRY = 0, APS_DATA_TX_UNICAST_FAILED = 205, ROUTE_DISCOVERY_INITIATED = 87, NEIGHBOR_ADDED = 18, NEIGHBOR_REMOVED = 15, NEIGHBOR_STALE = 27, JOIN_INDICATION = 20, CHILD_REMOVED = 5, ASH_OVERFLOW_ERROR = 0, ASH_FRAMING_ERROR = 0, ASH_OVERRUN_ERROR = 0, NWK_FRAME_COUNTER_FAILURE = 0, APS_FRAME_COUNTER_FAILURE = 0, UTILITY = 0, APS_LINK_KEY_NOT_AUTHORIZED = 0, NWK_DECRYPTION_FAILURE = 0, APS_DECRYPTION_FAILURE = 0, ALLOCATE_PACKET_BUFFER_FAILURE = 0, RELAYED_UNICAST = 0, PHY_TO_MAC_QUEUE_LIMIT_REACHED = 0, PACKET_VALIDATE_LIBRARY_DROPPED_COUNT = 0, TYPE_NWK_RETRY_OVERFLOW = 0, PHY_CCA_FAIL_COUNT = 16, BROADCAST_TABLE_FULL = 0, PTA_LO_PRI_REQUESTED = 0, PTA_HI_PRI_REQUESTED = 0, PTA_LO_PRI_DENIED = 0, PTA_HI_PRI_DENIED = 0, PTA_LO_PRI_TX_ABORTED = 0, PTA_HI_PRI_TX_ABORTED = 0, ADDRESS_CONFLICT_SENT = 0, EZSP_FREE_BUFFERS = 241]`
Additional information
No response
Hey there @dmulcahey, @adminiuga, @puddly, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of zha can trigger bot actions by commenting:
-
@home-assistant closeCloses the issue. -
@home-assistant rename Awesome new titleChange the title of the issue. -
@home-assistant reopenReopen the issue. -
@home-assistant unassign zhaRemoves the current integration label and assignees on the issue, add the integration domain after the command.
(message by CodeOwnersMention)
zha documentation zha source (message by IssueLinks)
Hi,
I experience the exact same issue with this device. I can control every aspect of the device using the same Zigbee antenna and zigbee2mqtt so the device and communication work.
Hi,
I experience the exact same issue with this device. I can control every aspect of the device using the same Zigbee antenna and zigbee2mqtt so the device and communication work.
I bought a Sonoff Zigbee stick and used zigbee2mqtt. Worked right out of the box. Thinking about transfering all of my ZIgbee devices to zigbee2mqtt.
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 Home Assistant 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.