Domoticz

Sorry. I think I misunderstood your question. What kind of Homekit device do you want to add?

My home automation runs on Domoticz, but I have a Tuya plug and a Homekit bulb connected to Homebridge/Homekit. And I am looking for a way to control these from Domoticz too.

It's my question too. I have a real homekit switch which works in homekit, lets call it switch_homekit. I can create a dummy-switch in Domoticz, lets call it swich_domoticz and share it with homekit via homebridge. So in homekit I have the real switch switch_homekit and the dummy switch switch_domoticz. To transform action between the 2 switches, I have to perform 4 automations in homekit. If switch_domoticz is activated, avtivate switch_homekit. If switch_homekit ist aktivated, activate switch_domoticz. And the same for deactive. In normal homebridge I have a fixed connection beween the domoticz and the homebridge / homekit switch. Would it not be possible to define a connection between a real homekit-switch and a domoticz / homebrdige switch. Perhaps in the config.json?

I set up everything as per the wiki. Everything seems fine. Except that the first time I use home bridge, all the devices in Domoticz show up in the home bridge accessories page. But after that any devices I add don’t show up. How do I perform a new fetch ?

Recently, I have setup Homebridge in order to connect my Domoticz to Google Home. However, every now and then almost all of my Domoticz devices are moved to the default room again in Google Home and the swtiches cannot be controlled anymore.

Basically this means that I cannot create reliable routines interacting with Domoticz. Is there anything I can do about this?

JonyBCN wrote: ↑Thursday 17 September 2020 9:05 I think that should be done by the domoticz itself, rather than a plugin that "pulls" information from it.
Homebridge should be included in the Hardware tab, either native or via a python plugin.

Yes, that would be marvellous, a plugin for Homekit or Homebridge, so you can add all kind of Homekit-accessories.

pvdgulik wrote: ↑Tuesday 29 June 2021 23:40

JonyBCN wrote: ↑Thursday 17 September 2020 9:05 I think that should be done by the domoticz itself, rather than a plugin that "pulls" information from it.
Homebridge should be included in the Hardware tab, either native or via a python plugin.

Yes, that would be marvellous, a plugin for Homekit or Homebridge, so you can add all kind of Homekit-accessories.

You can check my plugin :
https://github.com/macjl/Domoticz-HomekitInsecureClient

Thanks!! I installed it but got errors...
Wrong python version?

Thanks

You can also tap up the Homebridge-config-ui-x Swagger API... swift bit of Node-Red to translate from the API to MQTT or to poll and trigger HTTP updates of Domoticz. https://github.com/oznu/homebridge-conf ... -Reference

MacJL wrote: ↑Wednesday 30 June 2021 0:31

pvdgulik wrote: ↑Tuesday 29 June 2021 23:40

JonyBCN wrote: ↑Thursday 17 September 2020 9:05 I think that should be done by the domoticz itself, rather than a plugin that "pulls" information from it.
Homebridge should be included in the Hardware tab, either native or via a python plugin.

Yes, that would be marvellous, a plugin for Homekit or Homebridge, so you can add all kind of Homekit-accessories.

You can check my plugin :
https://github.com/macjl/Domoticz-HomekitInsecureClient

I Installed this plugin. And it connects to a plug on Homebridge, but then it disconnects again, showing errors in the log:



show full size

What is wrong?

Pupz wrote: ↑Friday 22 October 2021 22:04 I Installed this plugin. And it connects to a plug on Homebridge, but then it disconnects again, showing errors in the log:

Hello Pupz

I've published a new realease with more logs, when in debug mode. Can you update and select 'Plugin Debug' in the debug conf. Then send the new logs.

And can we continue this discussion in the thread related to my plugin, because this is not related to homebridge-edomoticz ?

=> viewtopic.php?f=65&t=36148

OK, done.

Is there a way to make to users? So not every user can switch every Light.
Just like in domoticz.

Thanks,
Mark

Hi,

I've updated my Domoticz running in docker and it is now accessible on 10.x.x.x/domoticz/:8080
it was 10.x.x.x:8080 before.

how do I set up homebridge E-domoticz plugin to look in /domoticz/ folder?

regards

uermend wrote: ↑Tuesday 08 February 2022 16:07 Hi,

I've updated my Domoticz running in docker and it is now accessible on 10.x.x.x/domoticz/:8080
it was 10.x.x.x:8080 before.

how do I set up homebridge E-domoticz plugin to look in /domoticz/ folder?

regards

eDomoticz must not be in the Domoticz folder. It is a Homebridge plugin, you install it in it and point to the Domoticz address in its configuration.

any idea why homebridge and google voice doenst work any more? i has been working without any problems for years now, but suddenly google syas that it couldnt connect to homebrigde, ehat could be wrong?

I have a Pi3 with domoticz, homebridge and homebrdige-edomaticz running since many years, actually at the newest beta. Now I installed a new pi4 with the same status domoticz but the newest homebridge and homebridge-edomatics. I changed the settings in the new config to the old ones, shutdown the old pi and bootet the new. I would have hoped, that all works immedeatly. But in IOS home, I see only actualising. I could scan the new code (which is the same as the old one ), but I have a lot of shortcuts with homekit equipment and I don't want to loose this. Would it run, if I would change the ip-adress of the new pi to the old one, or how does homekit identify the devices. Rebooting the old pi, all works. Thanks a lot for an advice.

I love this plugin apart from the fact it spams my logs every few minutes with :

2022-04-23 21:47:34.732 Status: Incoming connection from: 192.168.2.9
2022-04-23 21:47:34.740 Status: Incoming connection from: 192.168.2.9
2022-04-23 21:47:34.747 Status: Incoming connection from: 192.168.2.9
2022-04-23 21:47:34.754 Status: Incoming connection from: 192.168.2.9
2022-04-23 21:47:34.761 Status: Incoming connection from: 192.168.2.9
2022-04-23 21:47:34.769 Status: Incoming connection from: 192.168.2.9
2022-04-23 21:47:34.777 Status: Incoming connection from: 192.168.2.9
2022-04-23 21:47:34.784 Status: Incoming connection from: 192.168.2.9
2022-04-23 21:47:34.792 Status: Incoming connection from: 192.168.2.9
2022-04-23 21:47:34.799 Status: Incoming connection from: 192.168.2.9
2022-04-23 21:47:34.806 Status: Incoming connection from: 192.168.2.9
2022-04-23 21:47:34.813 Status: Incoming connection from: 192.168.2.9
2022-04-23 21:47:34.820 Status: Incoming connection from: 192.168.2.9
2022-04-23 21:47:34.827 Status: Incoming connection from: 192.168.2.9
2022-04-23 21:47:34.834 Status: Incoming connection from: 192.168.2.9
2022-04-23 21:47:34.841 Status: Incoming connection from: 192.168.2.9
2022-04-23 21:47:34.848 Status: Incoming connection from: 192.168.2.9
2022-04-23 21:47:34.855 Status: Incoming connection from: 192.168.2.9
2022-04-23 21:47:34.862 Status: Incoming connection from: 192.168.2.9
2022-04-23 21:47:34.870 Status: Incoming connection from: 192.168.2.9
2022-04-23 21:47:34.877 Status: Incoming connection from: 192.168.2.9

@solarboy,
I have the same behaviour and I don't know how to remove it.
Juste surprised that no one is concerned by this?

Perhaps in a future update our concerns will be silently resolved...