-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Very slow #246
Comments
Check your MQTT setup. Not seeing any such issues here… |
Same here. Since 2 weeks the commands from edomoticz to domoticz are very slow. It takes about 30 seconds to flip a switch. MQTT is working fine for me. Any other suggestions? |
MQTT can’t be working fine if s’taking over 30s for Domoticz to respond to an MQTT command. Have you subscribed to the MQTT feed in a standalone client to check how quickly MQTT despatches message after making a change via HomeKit, and then cross referenced this with Domoticz’ own log for the command being received? Basically, once command leaves HomeKit, the issue isn’t with the plug-in. It’s with either your MQTT or Domoticz config. |
(Nothing has changed in the plug-in for months, so what actually changed 2 weeks ago? Start there) |
Thanks for your response. I'll trace back from there. |
For me, My MQTT has no problem, very fast... But somme switch from Domoticz are slow. Since the last update of Domoticz. The switch who are slow, are dummy Switch, and if i turn on or turn off from Domitcz, it's OK (Fast), but if i use the HTTP Command, it's very Slow... It was working fine before the Update. Sorry for my english, it's not my native language. |
If you’ve got MQTT setup, the HTTP command is hardly ever used by the plug-in. Usually only gets used by dimmers and sliders to prevent looping conditions.
All regular switch commands should be going by MQTT.
…Sent from my iPhone
On 17 May 2022, at 11:10, TheReiner ***@***.***> wrote:
For me, My MQTT has no problem, very fast... But somme switch from Domoticz are slow. Since the last update of Domoticz.
The switch who are slow, are dummy Switch, and if i turn on or turn off from Domitcz, it's OK (Fast), but if i use the HTTP Command, it's very Slow... It was working fine before the Update.
Sorry for my english, it's not my native language.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
i use HTTP Command from Domoticz, not from the plug-in. |
Not sure what you mean by http command from Domoticz…? If MQTT is set up then all comms either direction between homebridge-edomoticz and Domoticz happen by MQTT. |
What is the destination of the http command for the virtual switch? |
Ie: is the issue between homebridge and Domoticz, or between Domoticz and something else? Speed of http commands from Domoticz to something else aren’t anything handled by this plug-in. This plug-in tells Domoticz, via MQTT, to flip a switch. You should be able to see these events in Domoticz log. Anything beyond that isn’t this plug-in. If you see Domoticz log receiving the MQTT command, this plug-in has done it’s job. If you can’t see the event hitting Domoticz, you need to check your MQTT server’s logging and addresses etc to see where the event is going if not to Domoticz’ incoming MQTT address. |
Everything works fine... Domoticz, homeBridge, Mqtt. Except since the last update of Domoticz (not edomoticz) some dummy Switch from Domoticz. In Domoticz all Dummy Switch works Well, but if use Http Command into Domoticz (not edomoticz), in homeBridge (with Edomoticz) i can wait 10s maybe 1 hour... If i use the DashBoard of Domoticz, it's fast... if for same Switch i use Curl Http Command to power ON for exemple... It's ON on Domoticz but not fast in homeBridge. (Edomoticz). Very sorry for English. |
Sounds like using http command into Domoticz doesn’t trigger Domoticz to transmit MQTT to say a value or status has changed. If you subscribe to Domoticz’ MQTT out channel with a desktop client, and then issue your http command, do you see the state change reflected out over MQTT?
… On 19 May 2022, at 21:49, TheReiner ***@***.***> wrote:
Everything works fine... Domoticz, homeBridge, Mqtt. Except since the last update of Domoticz (not edomoticz) some dummy Switch from Domoticz. In Domoticz all Dummy Switch works Well, but if use Http Command into Domoticz (not edomoticz), in homeBridge (with Edomoticz) i can wait 10s maybe 1 hour... If i use the DashBoard of Domoticz, it's fast... if for same Switch i use Curl Http Command to power ON for exemple... It's ON on Domoticz but not fast in homeBridge. (Edomoticz). Very sorry for English.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
Hi,
Since the last update Domoticz
Version: 2022.1
Build Hash: c9526851b
Compile Date: 2022-01-31 09:34:32
dzVents Version: 3.1.8
Python Version: 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110]
I have slowness on sensors, such as motion sensors... And those since the Domoticz update.
I even have lags on the notifications. Example is Off on the Domoticz side and On on the HomeKit side.
Suggestions for solving the problem?
The text was updated successfully, but these errors were encountered: