Hello everyone, I've got a problem with edomoticz when I update to V2 1 45-46 or 47. Homebridge can't load my accessoires, but if I go back to V2 1 40 everything work With v2 1 45+ [14/11/2023, 19:03:24] Homebridge v1.5.0 (HAP v0.10.2) (Homebridge DCF1) is running on port 51726. [14/11/2023, 19:03 ...

I've managed to cause this sometimes by requesting to switch on a device but with a little bit incorrect name, still recognizeable though (or maybe similar to a room name). Not sure if this is a plugin or Homekit (/Homebridge) "feature". Luckily it hasn't happened for a long time.

Hopefully not an issue anymore but you have to restart domoticz and the go to create new hardware. Whatever plugin you installed, it should have created a new entry to the available hardware list for you to select.

Hi, thaks for the excellent work with this plugin. I tested it and was able to get it running after initial problems, maybe some incompatibility with other Tuya plugins I had running. It discovered all devices, but Moes BHT-002 thermostat was inoperable as it set the setpoint to 35C always. Maybe ...

philchillbill wrote: ↑Sunday 05 March 2023 22:32 Yes, you misunderstood.

That happens quite often…

For anyone interested, here’s a python example of similar functionality that includes unsync-resync. This part seems to work well but there are a couple of other missing features…
https://github.com/floris-b/lms_tts_notify

Took a while to get around to testing this. Did I misundersand the "sync" side of things as I though this would allow me to unsync a player temporarily, play the alert, and then re-sync? Now it seems that a synced player is taken out of the sync group and not returned there?

Thanks a lot. I was able to add a couple atc1441 flashed Xiaomi BLE sensors with these rules to Domoticz. It says that ESP32 supports up to 9 connected BLE devices. If I interpret right, the ruleset used here takes over 50% of the space allocated to Rule and there are slots for three rules. So, with ...

@waaren unfortunately passed away already more then a year ago so this will not be followed up. Oh, sorry to hear :( It seems @eserero found the same solution. Maybe s/he can elaborate. I understand one would need to trigger the setColor twice hence the additional switchOn(). But then if I set it ...

I have the same problem as @Haubke, the color temperature seems to be updating only the second time. anyone know how to resolve that? You could try to add an extra switchOn.afterSec(0.3) Sorry, I don't get it. An extra switchOn where? I tried adding it to the function but cannot see any change ...

Sure - will then setup Domoticz in the "old-fashioned" way which luckily is very easy as well

Did some testing now and indeed it looks a bit worrying for the future. I first tested with some simple os.execute('curl...) in lua and that worked fine. Then I wanted to try a bash script that uses wget to store a snapshot of security camera and send it via telegram (curl). With this I was already ...

Yeah, have been using docker for a while now, e.g. zwajejs2mqtt, vscode, ftp-server, homeassistant etc. but with these it is sort of more clear what is containeraized. In Domoticz, if I for example call script from a switch with script:///path and this script is then using some library that is ...

I installed the plugins on the host in the Domoticz folder. Some used a shell script others use pip(3). All working as expected. The docker-compose.yml on my machine is located in ~/containers/domoticz. I create a persistent volume data in that folder to store the data for the container. version ...

Sounds good - please do share your docker-compose.yml if not too much trouble. Yes, the volumes should be easy to link to local home, but what I fear is the trickier is the custom scripts that Domoticz should call. They depend on different packages (installed with apt, pip...) which are not probably ...

At the moment I'm running Domoticz in RPi3, no problems. Currently on the same Pi I have zigbee2mqtt, zwavejs2mqtt, mosquitto, lot's of custom python scripts (and python plugins under Domoticz) etc. Also, with the amount of devices growing, size of the Domoticz db growing (been running it from 2015 ...

Thanks, will definitely check this option. I guess MQTTlink.py needs to be made run as a service (or enough to run once to create the needed mqtt topics)? In case you or anyone else is interested, there are more details now available for the alternative method of integrating HA & Domoticz through ...

As a feature request, it would be great if the resolution could be set in device parameters. As for some thermostats the resolution is 0.1, for some 0.5 and for some even 1.0. As a configurable value, everyone could set it to whatever the actual thermostat device follows...

Hi, after migrating to zwavejs2mqtt I started seeing strange devices, e.g. fibaro plug offers: switch_switch sensor_water_tank_capacity sensor_temperature_air sensor_illuminance sensor_electricity_power sensor_electric_w_value sensor_electric_kwh_value Fibaro PIR offers: binary_sensor_any sensor ...

Yes - but this is the ”autodiscovery” option as can be seen on the hardware name. It is the built-in (native) way to integrate zigbee devices through zigbee2mqtt to Domoticz. I have used the python plugin in 2 versions (latest stable and the beta), and also the AutoDiscovery version. Is this "ha ...

I think the ”hardcore” (or hardcoded maybe, native would be even better I guess) version here refers to the ”autodiscovery” which you mentioned you are already running in parallel with this python plugin? So no, there is no third option (well, there is this: https://github.com/zigbeefordomoticz/Domot ...