I installed the latest on docker and I get this in the log when I try to add a dummy switch: 2024-01-13 14:34:23.038 Status: Domoticz V2024.1 (build 15838) (c)2012-2024 GizMoCuz 2024-01-13 14:34:23.038 Status: Build Hash: b97eb6256, Date: 2024-01-13 11:19:22 2024-01-13 14:34:23.038 Status: Startup ...

I haven't pursued this... life events got in the way. Would be nice to see Domoticz with an AWS IoT Core connector.

I too would find this option useful for switch objects. I created a notification to monitor when a particular switch goes off (triggered by a temp sensor) I get multiple notifications that the switch went off every time the temp was read. This isn't useful and creates a lot of noise. It would be ...

I know Domoticz ships with an MQTT broker but I wanted to connect Domoticz to an AWS IoT core "thing" (which is an instance of TLS MQTT). The obvious benefits are: 1) I can learn how to leverage AWS IoT Core into my home automation plan 2) I don't have to punch holes through my firewall to receive ...

*bump* we need a fix, or at least someone to point out the script object to modify to allow Domoticz to call this API over HTTPS... please help.

I think this is because Domoticz makes a call to the API over port 80 (HTTP) and not port 443 (HTTPS). When I curled: curl http://api.darksky.net/forecast/api.key/41.9884,-71.3329 {"code":400,"error":"this call requires HTTPS"} Where do we change the API call from HTTP to HTTPS? It seems Darksky ...