Indeed, this should be split into separate rules. And's and comma's are not supported. The reason it might have worked is purely coincidental, perhaps due to how dzVents parses the rules.

Awesome!!

Hi folks, After upgrading to 2020.1 and using the EvoHome Web API I'm getting these errors: Error: (Evohome) v1 login failed with message: Request count limitation exceeded, please try again later. I switched to another evohome-account and then it works for a while but in an hour things stop working ...

All these suggestions are far from trivial mostly due to performance issues. Doing a devices={ '*' } is a true performance killer as for each event (can be dozens per event-tick) all device objects get instantiated in dzVents and the execute function gets executed. So I truly don't recommend this at ...

MrHobbes74 wrote: ↑Monday 17 February 2020 10:01 Hi! You can transfer multiple values by providing a json formatted string as the myData parameter (e.g. data=[{“a”:“b”, “c”:“d”}]

Make sure it is url encoded.

I just updated, unfortunately I get this error message: Error: EventSystem: in /home/pi/domoticz/dzVents/runtime/dzVents.lua: /home/pi/domoticz/dzVents/runtime/EventHelpers.lua:462: bad argument #1 to 'for iterator' (table expected, got string) Please report this in the bugs section together with ...

Hi folks, I am proud to announce dzVents 3.0 has been merged in Domoticz v4.11687. Thanks to the hard work of MrHobbes74, waaren and yours truly we have some very interesting new features: System events Many times asked for and now possible is a way to run scripts as soon as Domoticz was started ...

Hi folks,

As you can see I have locked a couple of the huge topics in favor of the new sub channels in this forum. The new channels are:

• Bugs
• Feature requests
• How-tos

Let's try to use those as much as possible. All other discussions can stay in the main channel.

Kind regards,

Danny

Peeps, there is a new sub forum for bug reports. Let's start using that from now on where each report is it's own topic to keep things manageable. Locking this topic for now.

Cheers,

Danny

Peeps, there's a new sub forum for feature request. Let's use that one from now on. This topic will be locked.

Cheers,

Danny

Peeps, this thread is going to be closed as it is too long be useful anymore. Please feel free to post new topics and let's try to stick to the topic and keep them short.

Danny

I am running Domoticz here on a Pi3 using the Hue plugin. So far so good. It polls every 10s for updates. But… regularly (every 1 or 2 days) it suddenly cannot connect anymore to the bridge (Error: Philips Hue: Error getting Light States, (Check IPAddress/Username)). Using curl on the Pi, the bridge ...

I'd say the comment should be something like: -- switch off for 2 minutes after a randomized period of 1-10s has passed.
And the delay is before the actual switching.

I know Ideas and pull-request are always welcome.

Well, it's one line of code. But if that's too complicated then I'd say use the Lua functions. You'll love them :-p

The .compare attribute of the compare() results should give you just that information I believe. I created the Time object and the compare function so you don't have to deal with Lua's horrible date/time support.

Why don't you use dzVents Time object for this. Afaik it can do all of the above. Especially when you use the compare function.

Or you use the date object’s compare function. See the docs.

Best is to see the log from the command-line as the web version of the log (in the GUI) seems to miss entries every now and then.

You can change the rule to and this one: to Much shorter