virtual device are not set to active by default in Beta V4.11402 V4.11403  [Solved]

Easy to use, 100% Lua-based event scripting framework.

Moderator: leecollings

Post Reply
User avatar
waaren
Posts: 6028
Joined: Tuesday 03 January 2017 14:18
Target OS: Linux
Domoticz version: Beta
Location: Netherlands
Contact:
Contact waaren

virtual device are not set to active by default in Beta V4.11402 V4.11403

Post by waaren »

New created virtual devices are not active by default.

Still testing other differences. Will report back when tests are complete.
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
Top
HFman
Posts: 82
Joined: Thursday 02 March 2017 20:28
Target OS: Linux
Domoticz version: V4.1174
Location: Netherlands
Contact:
Contact HFman

Re: virtual device are not set to active by default in Beta V4.11402 V4.11403

Post by HFman »

aah this explains.. so a easy downgrade button would be still a nice feature....
Raspberry PI 3 - Opentherm Gateway + ESP8826 - EvoHome - ESPEasy CO2 + Fancontrol - RF-Link - zigbee2mqqt -
Top
User avatar
waaren
Posts: 6028
Joined: Tuesday 03 January 2017 14:18
Target OS: Linux
Domoticz version: Beta
Location: Netherlands
Contact:
Contact waaren

Re: virtual device are not set to active by default in Beta V4.11402 V4.11403  [Solved]

Post by waaren »

HFman wrote: Wednesday 23 October 2019 20:12 aah this explains.. so a easy downgrade button would be still a nice feature....
Solved in V4.11409
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
Top
Post Reply

Return to “dzVents”

Who is online

Users browsing this forum: No registered users and 1 guest