I hope you don't mind a healthy debate on this, because in my opinion your conclusion might be too conventional. Perhaps it's not much used because the full functions aren't yet in place. Yes there are multiple ways to achieve any automation-purpose in Domoticz, But keeping all possible info tightly ...

I have no knowledge that a motion sensor in Domoticz knows and saves what triggered it. The screenshot you showed is not a Domoticz screenshot. Perhaps zwave? Thats a screenshot of the Domoticz visual-editor's Devices-current-states page. Natively a motion sensor has 1 value On/Off, but any type of ...

While thinking about this, I wonder why dzVents offers item.status and item.sValue like the way it does. In many cases they hold the same value. Okay, "status" serve's a purpose, but then what's the reason for "sValue"? The function setValues(nValue,[ sValue1, sValue2, …]) offers to set multiple s ...

The sValue(s) can be any useful string. In my use-case there are motion sensors holding info about what triggered them. See screenshot. I use these value's in notifications. I might be wrong, but the "status" (On/Off) is something different than the discussed "sValues" right? Schermafbeelding 2021 ...

dzVents is greatly documented, but I am confused when it comes to sValue's. item.sValue returns "On" or "Off", but not the sValue as seen in the visual-editor's Devices-current-states page. By using 'item.dump()' in a script, I found the sValue data with key "1" or "2" etc., so item.rawData[1] gives ...

DewGew wrote: ↑Friday 26 June 2020 21:45 Google dont accept self signed certificate get a let’s encrypt cert https://github.com/DewGew/Domoticz-Goog ... erse-proxy

Hahahha okay :p I'm puzzeled though, you had openSSL instruction in the wiki on github. I see it's edited now
I will give it a go!

It's a selfsigned certificate, so naturally it's not trusted. Furthermore it works as expected, no certificate problems. From the log, (these are just normal lines right?): 2020-06-26 21:16:50 - DEBUG - Starting new HTTPS connection (1): raw.githubusercontent.com:443 2020-06-26 21:16:50 - DEBUG ...

I see having multiple config guides leads to confusion. There is one in domoticz forum, one in dzga, and one on github. Do I add a ClientID and Secret to config.yaml or not? Either way I cant manage to get it working 🤷‍♂️ Github wiki is most rescent to follow. ClintID and Secret is optional you dont ...

I see having multiple config guides leads to confusion.
There is one in domoticz forum, one in dzga, and one on github.

Do I add a ClientID and Secret to config.yaml or not?
Either way I cant manage to get it working

I checked the setting numerous times, and I enabled TEST every time. Just to verify; - Is it possible to run it with “ sampleClientId” and “ sampleClientSecret”, even when I have created an OAuth client ID? - While creating the credentials, the option “other” is not available... Is there any way to d ...

Hi DewGew, It’s hard to admit, but I’m going to need a little help. I have gone trough the (well written and extensive) instructions, but in the home-app I keep getting the message “something went wrong, try again” upon adding the dzga-device. I cannot find any hints in the debug-log, or anywhere els ...

I have exactly same problem on my synology with domoticz latest version from Jadahl on my 916+ Since latest version from Jadahl on my DS216+II Browser is not refreshing anymore automatically. how can that be fixed? Are you using reverse-proxy? If so, you'll have to add WebSocket to your header ...

Who do I need to contact to explain me the process for building the spk's? Once I know the bottleneck, I'm willing to create an automation for it.
Please let me know by sending me a PM.

I was just thinking about the +1 fix.. If it was specifically needed for Hue lights, then wouldnt it make sense if these lights were added to homekit directly from within the Hue-app? Hue is fully homekit supported, so why would one need homebridge for this?

Really great! Thanks a bunch

Ah yes, that would be npm.

Just whenever you get it sorted.

As an extra note; To me it seems more logical to exclude the +1 by default. For whom is experiencing problems with the default functionality could then add the +1 from within config. Perhaps something to consider.

Marci, can you add a flag for it in the config?
I am running homebridge in a docker container, and it reloads all modules on every startup. Its a bit of a hassle to statically make the edit in this setup

Edit: I'm at home now, so I tested by removing the +1 from /usr/local/lib/node_modules/homebridge-edomoticz/lib/domoticz_accessory.js and now the sliders work as they should. The “+1” must be there for a reason. Maybe Marcie can weigh in here? @ksacca - Can you test if you (with your edit) can sti ...

@robbie - subscribe to the MQTT feed with a feed-reader and monitor what’s getting sent. Sounds like something is repeating the message. @Marci; The messages are not repeated. What I can see when inspecting the messages, is that domoticz/in receives the level + 1. Then domoticz/out sends that new l ...

Since I enabled MQTT, virtual dimmers keep increasing the level in HomeKit by 1% per second. This happens when I adjust the level for the dummy device through HomeKit, and stops as soon I close the level-view in HomeKit. I read about a "1%" bug, dated in 2016, but as far as I could find, it has been ...