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
Bug with Function Switch Selector / Planning Topic is solved
Moderators: leecollings, remb0
Forum rules
Before posting here, make sure you are on the latest Beta or Stable version.
If you have problems related to the web gui, clear your browser cache + appcache first.
Use the following template when posting here:
Version: xxxx
Platform: xxxx
Plugin/Hardware: xxxx
Description:
.....
If you are having problems with scripts/blockly, always post the script (in a spoiler or code tag) or screenshots of your blockly
If you are replying, please do not quote images/code from the first post
Please mark your topic as Solved when the problem is solved.
Before posting here, make sure you are on the latest Beta or Stable version.
If you have problems related to the web gui, clear your browser cache + appcache first.
Use the following template when posting here:
Version: xxxx
Platform: xxxx
Plugin/Hardware: xxxx
Description:
.....
If you are having problems with scripts/blockly, always post the script (in a spoiler or code tag) or screenshots of your blockly
If you are replying, please do not quote images/code from the first post
Please mark your topic as Solved when the problem is solved.
- seby901
- Posts: 5
- Joined: Tuesday 15 March 2022 10:26
- Target OS: NAS (Synology & others)
- Domoticz version: 2024.7
- Location: BELFORT France
- Contact:
Bug with Function Switch Selector / Planning
Last edited by seby901 on Tuesday 12 November 2024 9:38, edited 2 times in total.
- waltervl
- Posts: 5148
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2024.7
- Location: NL
- Contact:
Re: Bug with Function Switch Selector / Planning
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.
Make a new value 30 for FORCE.
With the edit button there is an option to hide the OFF (0) value.
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
- seby901
- Posts: 5
- Joined: Tuesday 15 March 2022 10:26
- Target OS: NAS (Synology & others)
- Domoticz version: 2024.7
- Location: BELFORT France
- Contact:
Re: Bug with Function Switch Selector / Planning
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.
- waltervl
- Posts: 5148
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2024.7
- Location: NL
- Contact:
Re: Bug with Function Switch Selector / Planning
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.
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
- seby901
- Posts: 5
- Joined: Tuesday 15 March 2022 10:26
- Target OS: NAS (Synology & others)
- Domoticz version: 2024.7
- Location: BELFORT France
- Contact:
Re: Bug with Function Switch Selector / Planning
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
Thanks a lot. Problem solved
Who is online
Users browsing this forum: kniazio and 1 guest