So your TH1134 is setuped in HA via ZHA? or sinope-zha ? TH1134ZB-HC is not yet supported in ZHA. I just push a PR for this today. Also in sinope-zha I just update to add support for TH1134ZB-HC today. Tell me how your TH1134ZB-HC is setuped in HA exactly
Salut @claudegel
You might want to make a small modification to https://github.com/claudegel/sinope-zha/blob/926d40aefcd2f89709dd9b9286a962c6a0801ba9/switch.py#L245 from: âaccess=ârWpââ to âaccess=ârwpââ my log is showing the following error:
2025-02-08 14:34:08.353 ERROR (SyncWorker_1) [zhaquirks] Unexpected exception importing custom quirk 'switch'
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.13/site-packages/zhaquirks/__init__.py", line 479, in setup
spec.loader.exec_module(module)
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^
File "<frozen importlib._bootstrap_external>", line 1026, in exec_module
File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
File "/home/homeassistant/.homeassistant/config/zhaquirks/switch.py", line 165, in <module>
class SinopeManufacturerCluster(CustomCluster):
...<166 lines>...
cluster_revision: Final = foundation.ZCL_CLUSTER_REVISION_ATTR
File "/home/homeassistant/.homeassistant/config/zhaquirks/switch.py", line 182, in SinopeManufacturerCluster
class AttributeDefs(foundation.BaseAttributeDefs):
...<149 lines>...
cluster_revision: Final = foundation.ZCL_CLUSTER_REVISION_ATTR
File "/home/homeassistant/.homeassistant/config/zhaquirks/switch.py", line 245, in AttributeDefs
water_temp_protection_type: Final = foundation.ZCLAttributeDef(
~~~~~~~~~~~~~~~~~~~~~~~~~~^
id=0x007E, type=t.enum8, access="rWp", is_manufacturer_specific=True
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "<string>", line 10, in __init__
File "/srv/homeassistant/lib/python3.13/site-packages/zigpy/zcl/foundation.py", line 1265, in __post_init__
object.__setattr__(self, "access", ZCLAttributeAccess.from_str(self.access))
~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
File "/srv/homeassistant/lib/python3.13/site-packages/zigpy/zcl/foundation.py", line 1227, in from_str
raise ValueError(f"Invalid access mode: {orig_value!r}")
ValueError: Invalid access mode: 'rWp'
Assuming that ârwpâ is the correct configuration.
Merci
Good catch Iâll make the correction
Thank you
Iâve fixed it directly in the master
Did you try to change that attribute ? Do you have the possible values for it ?
No sorry I do not have that switch. I just noticed the error when I was upgrading HA.
Hello @claudegel, I am having an issue when I attempt to change the configuration backlight_auto_dim_param to bedroom: 2 for a Zigbee thermostat via the Manage Zigbee device configuration window.
2025-03-10 13:52:27.559 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140119952845280] Unexpected exception
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.13/site-packages/homeassistant/components/websocket_api/commands.py", line 245, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<7 lines>...
)
^
File "/srv/homeassistant/lib/python3.13/site-packages/homeassistant/core.py", line 2795, in async_call
response_data = await coro
^^^^^^^^^^
File "/srv/homeassistant/lib/python3.13/site-packages/homeassistant/core.py", line 2838, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/srv/homeassistant/lib/python3.13/site-packages/homeassistant/helpers/service.py", line 1109, in _async_admin_handler
await result
File "/srv/homeassistant/lib/python3.13/site-packages/homeassistant/components/zha/websocket_api.py", line 1333, in set_zigbee_cluster_attributes
response = await zha_device.write_zigbee_attribute(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<6 lines>...
)
^
File "/srv/homeassistant/lib/python3.13/site-packages/zha/zigbee/device.py", line 878, in write_zigbee_attribute
value = convert_zcl_value(value, attr_def.type)
File "/srv/homeassistant/lib/python3.13/site-packages/zha/application/helpers.py", line 156, in convert_zcl_value
field_type[value.replace(" ", "_").split(".", 1)[-1]]
~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/enum.py", line 789, in __getitem__
return cls._member_map_[name]
~~~~~~~~~~~~~~~~^^^^^^
KeyError: '2'
If I use the ZHA Toolkit: Write Attribute capabilities it works fine. It also display correctly the change via the read attribute in the Manage Zigbee device configuration window. It is only having issues changing that specific configuration no issues to write: OnDemand: 0 or Always: 1
Hi @Cognoquest what is your thermostat model ?
Iâve checked on my side with a TH1134ZB-HC in ZHA manage zigbee device. if I write 2 as a value, I get an error but if I put Backlight.Bedroom or just Bedroom as a value it work. Old zigbee thermostat donât have the bedroom option. I think it is only the G2 and TH1134. Iâm presently switching all SinopĂ© quirks to ZHA V2 and the backlight param will be available as a multiple select option directly in the device page. No need to go in manage zigbee device or use zha toolkit. But meanwhile Iâll check why the third option is not available as a number but only as text value.
Thanks @claudegel the changes that you are proposing sounds great.
F.Y.I. I used Backlight.bedroom as described in https://github.com/claudegel/sinope-zha?tab=readme-ov-file instead of Backlight.Bedroom or Bedroom.
Thanks for reporting Iâll fix the readme for Bedroom. Iâve fix the three values.
Hello,
Iâve noticed that the Sinope thermostat integrations in âEnergyâ and âIndividual Devices Total Usageâ appear strangely; sometimes, âEnergy Usageâ is negative. Has this already been observed? It goes from positive to negative. How can this be corrected?
Thank you.
Bonjour,
Je remarque que les intĂ©grations des thermostats Sinope dans âEnergyâ âIndividual devices total usageâ apparaissent bizarrement, il arrive que âEnergy usageâ soit nĂ©gatif. Il passe du positif au nĂ©gatif. Est-ce que un constat dĂ©jĂ fait ? Comment corriger le tout.
Merci
Bonjour @mrochette01 quel sensor tu utilises ? hourly_kwh ou hourly_kwh_count. Jâai remarquĂ© que lors du changement dâheure oĂč on a reculĂ© lâheure plusieurs choses se sont passĂ©es donât Neviweb mâa dĂ©branchĂ© car mon scan_interval avait dĂ©passĂ© 10 minutes. Mais depuis tout est rentrĂ© dans lâordre.
@claudegel or others, I have some additional information regarding the thermostats backlight option that might be of interest.
If you attempt to change the TH1300ZB or TH1400ZB Backlight option to âBedroomâ . The request even if accepted does not change the configuration of these thermostats. It is ignored by both units.
Itâs just because this option, Bedroom, does not exist for TH1300ZB and TH1400ZB. Is is only for G2 and wifi thermostats. This will be fixed in next update of neviweb130 I hope.
You can still fix it with and automation that set backlight to Always during the day and on_demand during night. This way the backlight will be off during night
@claudegel, thanks for the reply. I apologies for not conveying properly my setup for you to provide input. I am one of those that prefers having complete control of its IOT devices for my HA infrastructure. Hence why I selected Sinope Zigbee devices but without the use of its gateway. Though I did not know that neviweb130 was deficient for this. I do not believe neviweb130 will be a solution in my particular case.
You are correct in saying that for this particular case it will be for me to make requests that my devices can acknowledge. I think it might be the devices firmware that is deficient and should reject this invalid call. I included you because I was not sure if there is anything you can do on the HA side to mitigate the situation? So that users are not dupped in believing that this an option for the TH1300ZB and TH1400ZB since no errors are provided as a response to the command. If not maybe this worth mentioning in https://github.com/claudegel/sinope-zha?tab=readme-ov-file Your call⊠as usual great work.
Effectively the device firmware is lacking the third possibility. But also the device is lacking a light sensor to know when it is dark in the room. This is the same in ZHA. Iâm working on porting the SinopĂ© quirks to ZHA quirks V2 and it will be possible to make the difference between both device type with a select menu to choose the value we need for Bakclight according with what devices are supporting. This will appear directly in the device page.