Are there specials things to thing about when using openURL in a DzVents script, when using domoticz in Docker? It keeps giving the error: Error: Error opening url: DzVents is enabled, it is running more scripts without issues. In the trusted network part there is 127.0.0.* played also with this ...

Do you need to have those devices as a trigger? What i often see when people start using dzvents, that they out the devices In the trigger list, because they think this is necessary to use the data in the script. This is not the case. Maybe you van post the complete script, that we can look if that ...

Info about this option in dzvents wiki
https://www.domoticz.com/wiki/DzVents:_ ... d_handling

Do the dz.openUrl with a afterSec() added, that will work as a delay

What you can do is make a dz.openUrl with a callback function. This dz.OpenUrl is then fired after X seconds. In your case the 120 seconds. With the callback you can retrigger your script to do the thing it then has to do. As far as i known. There is now real delay option in dzvents. Because a delay ...

What is in the log file?
Maybe there is more info, what the problem is

Focus on automation so you do not need to 'interact' with domoticz all the time. And stability, you don't want to sit in the dark because ... Nice written, that is the purpose of home automation. When you always need the UI to control things. Then you only made you hardware switch into a software ...

I have two airconditioning LG units (multisplit) and therefor I have 2 LG hardware items within Domoticz. When I disable and re-enable the other one als it works. Any idea what can cause this behavior and what could be the fix. I only have 1 LG unit. But you have 2, on hardware tab you made 2 rows ...

Did your search in the log files if there is an error?

By restarting domoticz, i think you also restart the plugin.
How is everything responding when you disable the plugin and enable it again?

For now i have the same problem with the user/passwords in it. Made a quick work-around in node-red. On the end of this message, the flow i made. Instructions for this flow: The ip-address + port needs to be filled in with your nodered ip-address + port What to change in flow: - Change node "Set ...

Just a question.

Do you use nodered?
Maybe then there are options to get it quickly working again.
In nodered it is possible to capture the GET url and convert it to something domoticz can work with.

It looks it doesn't have anything to do with version 2023.1 Because efarmer1 reports the same on 19 june 2022, with version 2022.1 If i have it correct. The VD1 doens't do a POST with these URL's, but it does a GET. Don't know why it does a GET, because what does it want to do with the information ...

To get rid of: 3/14/2023, 7:57:42 PMnode: Tuya devices function : (error) "TypeError: Cannot read properties of undefined (reading 'type')" I Modified the 'Tuya Devices' function to: /* if (msg.payload.ZbReceived) { if (msg.payload.ZbReceived.type === "Remote (TS0044)") { return [msg, null]; }else ...

The Powerplug is responding to my On / Off Virtual Sensor in Domoticz I also see this in NodeRed 3/14/2023, 7:57:42 PMnode: Tuya devices function : (error) "TypeError: Cannot read properties of undefined (reading 'type')" Can you try to remove this part in the node "Tuya devices"? Yes remove, you ...

Would this be like: - Copy the new json - Re-import in Nodered - Adjust the MQTT servers to point to my MQTT machines - Enjoy the new functionalities ? This are the steps i would do - Disable the flow you have running - Import the json file (ctrl+i), in the pop-up there is an option "select a file ...

Already tried to add the tuya powerplug, this is the easier part of the devices you want to add. It is not tested. I give the release a beta state. Please test it. The lights need more work because of ON/OFF/DIM (maybe rgb). I need the tasmota messages for that. The node-red flow will check once a ...

So for the documentation ;-) and the rest of the people that modified the TASMOTA ZIGBEE SETTINGS ;-) I mentioned it. I added on top of the UI page, that those 2 settings also have to be set at 0, just like the SetOption83 which is written. - Do I really need a separate IDX for battery ? You can ...

This is how the messages from the bridge have to look like (tasmota messages).
If they don't look like this, then the flow doesn't work.

Sorry, default zigbee settings are not mentioned how to set them.

but do i get it right, it now works?
This after changing options 100 and 119 set to 0

This one doesn't work for you?

viewtopic.php?t=6507

These palette options are used:

- node-red-contrib-flogger
- node-red-contrib-simple-gate
- node-red-dashboard
- node-red-node-ui-table
- node-red-contrib-schedex