Page 1 of 1
best way to input number 1..24 with Dashticz?
Posted: Saturday 25 January 2025 13:19
by renerene
Request for Improved Timer and Delay Controls in Dashticz
I'm currently looking for a better way to set hourly delays and timers for charging and heat control in Dashticz. At the moment, I'm misusing thermostats for this purpose, which isn't ideal. It would be great if there was a dedicated feature that allowed us to set integer values.
Does anyone know if there's a more appropriate method for achieving this functionality? Or perhaps this could be considered as a feature request for future Dashticz updates?
Maybe there is an option using variabelels, but I prefer dummy devices.
Any insights or suggestions would be much appreciated. Thanks in advance!
Re: best way to input number 1..24 with Dashticz?
Posted: Saturday 25 January 2025 15:34
by Lokonli
Currently you can use a slider, dial or selector switch.
What would you like to have? Any example?
Re: best way to input number 1..24 with Dashticz?
Posted: Saturday 25 January 2025 17:35
by renerene
These are not so accurate if i remember. Also a dimmer chops the 100 scale in big chunks, you cannot increase with value 1. A thermostat is relative slow, takes a lot of patience and clicking om my old tablet.
I would like to be able to set my variable to 5 or 16.
Re: best way to input number 1..24 with Dashticz?
Posted: Monday 27 January 2025 9:14
by lost
Would be useful, even out of dashticz. A slider/rotating knob widget with tunable range/step/unit would be really useful. For now I use virtual selector switches than call some scripts with selector level setup parameter given to script but that's not so handy to setup.
My use case is disabling some timer plans for a few hours: If I needed a 1h/24h range for a full day (hopefully, not!), this would mean 24 lines in the selector!
Re: best way to input number 1..24 with Dashticz?
Posted: Monday 27 January 2025 9:20
by waltervl
In Domoticz the setpoint (thermostat) device is now configurable in min/max, step size and Unit of Measure.
Re: best way to input number 1..24 with Dashticz?
Posted: Monday 27 January 2025 9:38
by renerene
lost wrote: Monday 27 January 2025 9:14
Would be useful, even out of dashticz. A slider/rotating knob widget with tunable range/step/unit would be really useful. For now I use virtual selector switches than call some scripts with selector level setup parameter given to script but that's not so handy to setup.
My use case is disabling some timer plans for a few hours: If I needed a 1h/24h range for a full day (hopefully, not!), this would mean 24 lines in the selector!
yes, that is a good one. Use selector for now, that is better than thermostat. Thx.
Hopefully someone will pick up your idea.
Re: best way to input number 1..24 with Dashticz?
Posted: Monday 27 January 2025 9:57
by waltervl
Is a Dial in Dashticz not a rotating knob for Dimmers and Thermostats/Setpoints? Setting a Domoticz dummy Setpoint device to min 1 and max 24, step 1, UOM hours should give you a rotating knob in Dashticz with 1-24 (and do not use subtype "updown" in Dasticz block).
https://dashticz.readthedocs.io/en/beta ... /dial.html#
Re: best way to input number 1..24 with Dashticz?
Posted: Monday 27 January 2025 10:42
by lost
waltervl wrote: Monday 27 January 2025 9:20
In Domoticz the setpoint (thermostat) device is now configurable in min/max, step size and Unit of Measure.
Hello, did not know about this addition, I'll give it a try, thanks!
Re: best way to input number 1..24 with Dashticz?
Posted: Monday 27 January 2025 19:48
by renerene
attempt 1
Code: Select all
blocks['chargeHours'] = {
idx: 2628, //The Domoticz device id
title: 'chargeHrs', //The title of the block as shown in the dial.
width: 3, //The width of the block relative to the column width
type: 'dial', //Display as dial
subtype: 'updown',
hide_data: true,
//icon: 'fas temperature-high',
}
result:
10% steps
attempt 2
Code: Select all
blocks['chargeHours'] = {
idx: 2628, //The Domoticz device id
title: 'chargeHrs', //The title of the block as shown in the dial.
width: 3, //The width of the block relative to the column width
type: 'dial', //Display as dial
min: 2,
max: 16,
subtype: 'updown',
hide_data: true,
//icon: 'fas temperature-high',
}
:
a) starts wit 21 degree, as soon as you get below 16 it does not go up
b) 0
.5 incremental = not wanted
attempt 3 = success
Code: Select all
blocks['chargeHours'] = {
idx: 2628, //The Domoticz device id
title: 'chargeHrs', //The title of the block as shown in the dial.
width: 3, //The width of the block relative to the column width
type: 'dial', //Display as dial
min: 2,
max: 16,
steps: 2,
subtype: 'updown',
hide_data: true,
unit: 'h',
decimals: 0,
//icon: 'fas temperature-high',
}
PLEASE NOTE
sensor type 'dimmer' does not work (not sensitive to "steps"), use Dummy -> Setpoint
2628 = ok / 2044 = nok
--> thx Walter
Re: best way to input number 1..24 with Dashticz?
Posted: Monday 27 January 2025 19:54
by waltervl
Indeed as expected... Why not use a setpoint device as I proposed here earlier? Then also in a normal Domoticz Gui this will work.
https://wiki.domoticz.com/Dummy_for_vir ... t_Setpoint
Re: best way to input number 1..24 with Dashticz?
Posted: Thursday 30 January 2025 9:08
by lost
waltervl wrote: Monday 27 January 2025 19:54
Why not use a setpoint device as I proposed here earlier?
Can confirm this may be a good option. Tried this but did not changed my selector for now because widget does not allow to call some scripts directly with the setpoint value, as you can do in selector levels (setpoint changes needs to be handled from a device script for this kind of use). So this'll need a bit of rework as this was for now using a shell script (just doing some parameter formatting) calling another python one (as you cannot invalidate all timers associated with a device easily, unfortunately, this needs parsing whole 'getschedules' HTTP/JSON API returns to filter on device names and then use 'enabledisabletimer' on all those setup for the device).