According to Koenkk (the zigbee2mqtt guy) this part of the "climate" value should be picked up by Domoticz. "action_template": "{% set values = {None:None,'idle':'idle','heat':'heating','cool':'cooling','fan_only':'fan'} %}{{ values[value_json.running_state] }}" See https://github.com/Koenkk ...

I have just created an issue on Github.
https://github.com/domoticz/domoticz/issues/6309

Is zigbee2mqtt publishing a config topic for the missing device? Thanks for the hint. Here's what I see : homeassistant/climate/0xa4c138948f5233eb/climate/config { "action_template": "{% set values = {None:None,'idle':'idle','heat':'heating','cool':'cooling','fan_only':'fan'} %}{{ values[value_json ...

Addendum: I have updated Zigbee2MQTT to 2.2.1 with the associated herdsman updates. (Much fussing about getting pnpm to work due to missing version 10.4.1). This has made no difference at all, as shown by the Domoticz log where running_state is not found by MQTT Auto Discovery after a restart: 2025 ...

Hi, I have just purchased a Tuya ZWT198 wall thermostat. This appears to be well supported by zigbee2MQTT, however one state value does not get picked up in Domoticz. Here are the states as seen in Zigbee2MQTT: { "backlight_mode": "high", "child_lock": "UNLOCK", "current_heating_setpoint": 22.5 ...

I always hide my buttons once created with a $ sign at the beginning of the name, can't see the point in clutering up the dashboard with something you can't press.

You learn something new every day, really useful!

So @clumpton should double click and do a Long click on those switches first to get those added to Domoticz? Aha! That indeed works - bit of a pain because I will have to have search for the 'Action' in the device names in dzvents to separate the clicks but it's workable. Edit: And you still have ...

Ok, you should have mentioned that before that you are using the plugin... If you used the plugin you probably would have named it Zigbee2MQTT. Can you post a screenshot of your MQTT Auto gateway configuration page. What is written in field Type? Oops, sorry. I used to use the plugin, looks like I ...

waltervl wrote: ↑Tuesday 12 December 2023 21:04 The Zigbee2MQTT python plugin only looks at Zigbee2MQTT so has no problem.

That's what I'm using - it didn't use to have a problem, now it has

It's not a Zwave-JS issue but a Zigbee AD issue. These multifunction switches (Sonoff, Xiaomi) are not recognised by the built-in Zigbee AD as they are correctly recognised by the Zigbee Z2M plugin. This is a long standing issue that till today didn't get resolved (too specific devices?). With ...

You are running beta so this can happen. Check the commit list and issue list as I believe there were some changes on MQTT Auto discover with these kind of action devices. https://github.com/domoticz/domoticz/commits/development Thanks waltervl, I've checked and it looks like MQTT is sending a ...

Hi, I have 5 Zigbee push-button switches which control various lights around the house. (SONOFF SNZB-01) These have worked just fine until a recent update. Now I get this error message in the log: Error: MQTT Auto: sending switch commands for switch type 'sensor' is not supported (yet ...

I thought that it might be useful to share a bit of information. I bought a couple of these recently and all worked fine, except that one ran down the batteries very quickly. When I changed the batteries it went into Installation mode. Thereafter it would drop into installation mode randomly. I ...

Any idea if the script could cause the switches to be triggered automatically ? And all three at a time when I press one? I am not sure exactly what you want to do... As far as I can see you can use the script to query the alarm status and switch zones on and off. Any changes made by the script are ...

MikeyMan wrote: ↑Saturday 08 February 2020 17:26 I can control the alarm through the command line. Very cool!

Now for some fiddling with the switches in domoticz.

YAY!

I was wondering the same about the URLS, but they seem to be the same. It's mostly working now, only still get the ./somfy.sh: line 161: CarteAuthentification: bad array subscript error Somehow if i trigger the script to turn on the alarm once, it gets into some kind of loop, which triggers all ...

Access code = 4< Oops missed a character Change CodeAcces="$(echo "${CodeAcces:9:2}")" to CodeAcces="$(echo "${CodeAcces:8:2}")" (twice!) And, yes the script needs an argument, e.g. --Status which should read the alarm state PS These urls might need changing to their english version. You will need ...

My bad!!

Remove the extra " at the end of this line

OK, so it's not picking up the "B1", mainly because it's looking for "Code d'authentification" rather than "Authentication code". So you can replace this bit of code: # Ophalen toegangscode if [ "$Debug" = "True" ]; then echo " Toegangscode ophalen" CodeAcces="$(curl $SrvSomfyIp $UrlLogin | grep ...

Before we give up I have been taking a look at the code. The "CarteAuthentification" variable is a lookup table for passcodes - is this something that is supplied with the alarm? Just before your script fails it tries to contact the somfy server and gets an "Access Code" back (which looks like it ...