Domoticz

Version: 2024.7 build 16326
Platform: Raspberry Pi
Plugin/Hardware: dzVents Version: 3.1.8 Python Version: 3.9.2 (default, Mar 12 2021, 04:06:34) [GCC 10.2.1 20210110]
Description:

I have created a switch selector with 3 functions: off, automatic, forced . If I manually set the selector to OFF/AUTO/FORCE, it works perfectly, but it doesn't work in programming "planning", or I'm missing something.
In this example, I switch to FORCED mode at 9:18 and nothing moves ... Either it's a bug, or I'm the one who doesn't understand anything

Do not rename the default OFF (value 0) to something else.
Make a new value 30 for FORCE.
With the edit button there is an option to hide the OFF (0) value.

waltervl wrote: ↑Monday 11 November 2024 23:21 Do not rename the default OFF (value 0) to something else.
Make a new value 30 for FORCE.
With the edit button there is an option to hide the OFF (0) value.

thank you for this information. I made the change, but it doesn't work any better.

I have modified my initial request in order to better understand my problem. When I use the switch button, it works fine, but it's only the programming "Planning " that doesn't work.

For testing timers always take a time more than 2 minutes in the future to let Domoticz be able to configure the timers correctly. If you are too short on the current time then Domoticz can miss it.

Indeed, I was too short on timing ... I've just redone the test with a 10-minute gap and it's working fine...
Thanks a lot. Problem solved

Hi
I met an other bug with the switch selector planning.
I used to manage my electric heatings with the "smart virtual thermostat plugin".
this plugin create several devices
the one i want to plan is called 'thermostat control' it is a selector switch. when the electricity fare change i need to stop all the devices.
For example the switch is set to "auto" when i want to move it to "stop"
-manually i select the "off" and it works perfectly
-automatically i program the stop a 6 o'clock for example the switch change (-->" off" ) but the devices don't stop
I,tried 2 methods for settings the only one which change the state ot the selector is the second (where command is "off" and niveau "off")
the other one has no,effect

Works just fine for me on my test system (latest beta).

Thank you for this confirmation i have done a new test it is working.
Perhaps something was wrong in my previous experimentation..

I repeated the testing of the "off" command on the selector switch "thermostat control" created by the plugin "smart virtual thermostat" .
The effect of this command when selected manually by clicking the "off" button is to cut off all the "heaters" associated.
When the "off" command is activated by planning the heaters don't cut off.Even if the state of the selector has been changed to "off" by planning.
It is the second time I made this testing and the result is the same.I don't understand why.
Could you help..

the difference between manual action and planned action seems to come from the way of programming.
if the state of the selector is "auto" and you want to select the "off" state you have to program as showed on the picture. and not this one which has no effect or this one which change the state of the selector to "off" but don't cut off the heaters or what you want to command. I have to confirm this but the simulation i proceeded seems working.