new version 0.9.3
-
New Plugin - ChronoTherm (ex CronoAccesoSpento)
-
@Anduril said in New Plugin - CronoAccesoSpento:
looks realy interesting. ONe thing I don’t know is how to use it with a real device, do I have to create a rule to set my thermostat device to the temp your device has as setpoint?
Yes you have to compare the variable $ID.result to your temperature sensor
If “TemperatureSensor < $ID.result” enable somethink that increase temperature
else STOPAnd when you set temp manually (via gui or even hardware at thermostat) does it stays in auto modus and change temp to schedule at next time (as it is with max-cube)?
I have never tried max-cube but i have add a function in this version to return to automatic after a certain minutes, if that is what you mean
-
Hi,
In your device you have"cas1Ref": "$di1", "cas2Ref": "$di2", "cas3Ref": "$di3", "cas4Ref": "$di3", "cas5Ref": "$di3", "cas6Ref": "$di3", "cas7Ref": "$di3",
(5x $di3 ?)
I suppose this should be:"cas1Ref": "$di1", "cas2Ref": "$di2", "cas3Ref": "$di3", "cas4Ref": "$di4", "cas5Ref": "$di5", "cas6Ref": "$di6", "cas7Ref": "$di7",
What’s more: I first thought these were the 7 weekdays, but I assume these are the thermostat “heating program options”?
You can assign a program to $di1 for multiple days, and to $di2 as well.
like$di=12345,0,15,6.30,19,08.00,15,17.00,21,22.30,15
Monday to Friday starting midnight at 15°, at 06.30 to 19°, at 08:00 back to 15°, at 17.00 to 21° and at 22.30 back to 15°
combined with$di2=3,0,15,6.30,19,08.00,15,12.00,21,22.30,15
meaning: on Wednesday starting midnight at 15°, at 06.30 to 19°, at 08:00 back to 15°, at 12.00 to 21° and at 22.30 back to 15°
So Monday till Friday: 15° between 08:00 and 17:00, but on Wednesday afternoon from 12:00 also to 21°.Is this correct? Can that combination be made?
-
@Harry-van-der-Wolf
Thanks
After i have realize my error i found your postI corrected the mistakes and added examples
For your question…no, the combination is not correct
only you can create your schedule with…
hour,temperature,hour,temperature,hour,temperature…
and assign it to a day writing the number of the day of the week in the first value…
number(s) of the day of the week,hour,temperature,hour,temperature…Sorry i have problems with english
if you did not understand I try to explain better without problem -
I understood.
They are indeed heating scheduling programs, being 7 in total. Just by coincidence the same as number of days in the week.So my variables must be:
Mon, Tue, Thu, Fri:$di=1245,0,15,6.30,19,08.00,15,17.00,21,22.30,15
Wed:$di2=3,0,15,6.30,19,08.00,15,12.00,21,22.30,15
and unused programs simply get a value of 0.Of course you can create 7 programs and simply use one per day.
Thank you
-
@Harry-van-der-Wolf said in New Plugin - CronoAccesoSpento:
I understood.
They are indeed heating scheduling programs, being 7 in total. Just by coincidence the same as number of days in the week.So my variables must be:
Mon, Tue, Thu, Fri:$di=1245,0,15,6.30,19,08.00,15,17.00,21,22.30,15
Wed:$di2=3,0,15,6.30,19,08.00,15,12.00,21,22.30,15
and unused programs simply get a value of 0.Of course you can create 7 programs and simply use one per day.
Thank you
Ok but every days of the week must be present in a variable
In your scheduling you havo not put Saturday(6) and Sunday(7)
Example:
If you want 15° for the weekend you can create:
$di3=67,0,15 (Saturday and Sunday from midnight to 11.59pm the temperature is 15°) -
Just installed the plugin and started fiddling with it. Looks very nice
some requests/issues:- A small vertical bar/line on the program to display where we are in time
- Optional boost button
- I’m able to change the mode of the thermostat through a rule, but not the desired temperature?
I can ASK the manuTemp:
WHEN manuTemp of thermostaat-test is equal to xx
but can’t SET:set manuTemp of thermostaat-test to xx
Bug : When something is not correct in a variable, the plugin will stop updating (even if everything is corrected) until a restart of pimatic.
Like my projects and help? Consider donating electroneum etnjwAKGPqF6omQWRmpp9u2BPyVDG9VuyRQjNJ1S8yfBdfR9qeUQ46kRy8KS2CNqbpNLRrsgmNW6F2TMzxmZgPrh6KctrkrYbm
-
@koffienl said in New Plugin - CronoAccesoSpento:
Just installed the plugin and started fiddling with it. Looks very nice
some requests/issues:- A small vertical bar/line on the program to display where we are in time
As soon as I have some time
- Optional boost button
As soon as I have some time
- I’m able to change the mode of the thermostat through a rule, but not the desired temperature?
I can ASK the manuTemp:
WHEN manuTemp of thermostaat-test is equal to xx
but can’t SET:set manuTemp of thermostaat-test to xx
I’m working on it
Bug : When something is not correct in a variable, the plugin will stop updating (even if everything is corrected) until a restart of pimatic.
I’m working on it
many thanks for notifications
-
@zacca can you release the plugin to npm pls, so it will automatically be integrated into the pimatic plugin directory.
is it possible to rename the repository? since the plugin would be named as
pimatic-plugin-cronoaccesospento
the-plugin
is too much. would also be good to have an english name for the plugin if this is possiblepimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
@leader21 said in New Plugin - CronoAccesoSpento:
@zacca can you release the plugin to npm pls, so it will automatically be integrated into the pimatic plugin directory.
After add some change i will register to npm
is it possible to rename the repository? since the plugin would be named as
pimatic-plugin-cronoaccesospento
Just renamed in pimatic-cronoaccesospento
the
-plugin
is too much. would also be good to have an english name for the plugin if this is possibleUhmmm i’m not a developer, i started this project to make a small plug-in just for me, but the project has increased in size and I have made public with the same name
-
Update to 0.9.4
Change the name to ChronoTherm
Add control filters for the wrong variables
Add ability to change manutemp from rulesif anyone can try and tell me how it goes, then I will release on npm
-
@Zacca said in New Plugin - ChronoTherm (ex CronoAccesoSpento):
Update to 0.9.4
Change the name to ChronoTherm
Add control filters for the wrong variables
Add ability to change manutemp from rulesif anyone can try and tell me how it goes, then I will release on npm
I have installed the new version, but now I get "ERROR - You have entered a wrong variable/s"
What variables could be wrong?{ "cas1Ref": "$ThermoWerkdag", "cas2Ref": "$ThermoThuis", "cas3Ref": "$ThermoWeekend", "cas4Ref": "$Thermo4", "cas5Ref": "$Thermo5", "cas6Ref": "$Thermo6", "cas7Ref": "$Thermo7", "realtemperature": "$WoonkamerTemperatuur", "interval": 30, "turnauto": 0, "offtemperature": 17, "xAttributeOptions": [], "id": "thermostaat-test", "name": "thermostaat-test", "class": "ChronoThermDevice" }
All the vars exist and contain programs from the previous version.
Like my projects and help? Consider donating electroneum etnjwAKGPqF6omQWRmpp9u2BPyVDG9VuyRQjNJ1S8yfBdfR9qeUQ46kRy8KS2CNqbpNLRrsgmNW6F2TMzxmZgPrh6KctrkrYbm
-
@koffienl said in New Plugin - ChronoTherm (ex CronoAccesoSpento):
@Zacca said in New Plugin - ChronoTherm (ex CronoAccesoSpento):
Update to 0.9.4
Change the name to ChronoTherm
Add control filters for the wrong variables
Add ability to change manutemp from rulesif anyone can try and tell me how it goes, then I will release on npm
I have installed the new version, but now I get "ERROR - You have entered a wrong variable/s"
What variables could be wrong?{ "cas1Ref": "$ThermoWerkdag", "cas2Ref": "$ThermoThuis", "cas3Ref": "$ThermoWeekend", "cas4Ref": "$Thermo4", "cas5Ref": "$Thermo5", "cas6Ref": "$Thermo6", "cas7Ref": "$Thermo7", "realtemperature": "$WoonkamerTemperatuur", "interval": 30, "turnauto": 0, "offtemperature": 17, "xAttributeOptions": [], "id": "thermostaat-test", "name": "thermostaat-test", "class": "ChronoThermDevice" }
All the vars exist and contain programs from the previous version.
Can you tell me the values of the variables please ?
-
@Zacca said in New Plugin - ChronoTherm (ex CronoAccesoSpento):
@koffienl said in New Plugin - ChronoTherm (ex CronoAccesoSpento):
@Zacca said in New Plugin - ChronoTherm (ex CronoAccesoSpento):
Update to 0.9.4
Change the name to ChronoTherm
Add control filters for the wrong variables
Add ability to change manutemp from rulesif anyone can try and tell me how it goes, then I will release on npm
I have installed the new version, but now I get "ERROR - You have entered a wrong variable/s"
What variables could be wrong?{ "cas1Ref": "$ThermoWerkdag", "cas2Ref": "$ThermoThuis", "cas3Ref": "$ThermoWeekend", "cas4Ref": "$Thermo4", "cas5Ref": "$Thermo5", "cas6Ref": "$Thermo6", "cas7Ref": "$Thermo7", "realtemperature": "$WoonkamerTemperatuur", "interval": 30, "turnauto": 0, "offtemperature": 17, "xAttributeOptions": [], "id": "thermostaat-test", "name": "thermostaat-test", "class": "ChronoThermDevice" }
All the vars exist and contain programs from the previous version.
Can you tell me the values of the variables please ?
$ThermoWerkdag
1245,00.00,17.5,05.30,19.5,07.30,18,13.30,20,22.00,17.5$ThermoThuis
3,00.00,17.5,05.30,19.5,07.30,20,22.00,17.5$ThermoWeekend
67,00.00,18,07.00,20,22.00,18All the other variables where empty, but also I copied the contents of $ThermoWeekend to $thermo4 , $Thermo5, $Thermo6 and $Thermo7
Like my projects and help? Consider donating electroneum etnjwAKGPqF6omQWRmpp9u2BPyVDG9VuyRQjNJ1S8yfBdfR9qeUQ46kRy8KS2CNqbpNLRrsgmNW6F2TMzxmZgPrh6KctrkrYbm
-
@koffienl said in New Plugin - ChronoTherm (ex CronoAccesoSpento):
@Zacca said in New Plugin - ChronoTherm (ex CronoAccesoSpento):
@koffienl said in New Plugin - ChronoTherm (ex CronoAccesoSpento):
@Zacca said in New Plugin - ChronoTherm (ex CronoAccesoSpento):
Update to 0.9.4
Change the name to ChronoTherm
Add control filters for the wrong variables
Add ability to change manutemp from rulesif anyone can try and tell me how it goes, then I will release on npm
I have installed the new version, but now I get "ERROR - You have entered a wrong variable/s"
What variables could be wrong?{ "cas1Ref": "$ThermoWerkdag", "cas2Ref": "$ThermoThuis", "cas3Ref": "$ThermoWeekend", "cas4Ref": "$Thermo4", "cas5Ref": "$Thermo5", "cas6Ref": "$Thermo6", "cas7Ref": "$Thermo7", "realtemperature": "$WoonkamerTemperatuur", "interval": 30, "turnauto": 0, "offtemperature": 17, "xAttributeOptions": [], "id": "thermostaat-test", "name": "thermostaat-test", "class": "ChronoThermDevice" }
All the vars exist and contain programs from the previous version.
Can you tell me the values of the variables please ?
$ThermoWerkdag
1245,00.00,17.5,05.30,19.5,07.30,18,13.30,20,22.00,17.5$ThermoThuis
3,00.00,17.5,05.30,19.5,07.30,20,22.00,17.5$ThermoWeekend
67,00.00,18,07.00,20,22.00,18All the other variables where empty, but also I copied the contents of $ThermoWeekend to $thermo4 , $Thermo5, $Thermo6 and $Thermo7
Thanks
I fixed the bug
The fix will be released in the next updateFor now change the first 00.00 to 0
$ThermoWerkdag 1245,0,17.5,05.30,19.5,07.30,18,13.30,20,22.00,17.5
$ThermoThuis 3,0,17.5,05.30,19.5,07.30,20,22.00,17.5
$ThermoWeekend 67,0,18,07.00,20,22.00,18 -
Thanks, it’s working.
Problem : you also fixed a ‘bug’ in the previous version I was abusingI have a button called “today as sunday”. When this button is switched to ON I do the following: take the contents of
$AtHome
(this vart is not used by the plugin) and take the daynumber of the week and put this in a existing variable used by the plugin:IF sunday is turned on THEN $ThermoThuis = "{$weekday.text}{$AtHome}"
This worked in the previous version. When same dynbumber was used in multiple variables/programs the latest was used. It looks like that you ‘fixed’ this in the current version.
As soon as one daynumber is used more than 1 time, the colored bars disappear.Is it home somehow possible to allow a redefinition of a existing daynumber in the variables?
Like my projects and help? Consider donating electroneum etnjwAKGPqF6omQWRmpp9u2BPyVDG9VuyRQjNJ1S8yfBdfR9qeUQ46kRy8KS2CNqbpNLRrsgmNW6F2TMzxmZgPrh6KctrkrYbm
-
@koffienl said in New Plugin - ChronoTherm (ex CronoAccesoSpento):
Thanks, it’s working.
Problem : you also fixed a ‘bug’ in the previous version I was abusingI have a button called “today as sunday”. When this button is switched to ON I do the following: take the contents of
$AtHome
(this vart is not used by the plugin) and take the daynumber of the week and put this in a existing variable used by the plugin:IF sunday is turned on THEN $ThermoThuis = "{$weekday.text}{$AtHome}"
This worked in the previous version. When same dynbumber was used in multiple variables/programs the latest was used. It looks like that you ‘fixed’ this in the current version.
As soon as one daynumber is used more than 1 time, the colored bars disappear.Is it home somehow possible to allow a redefinition of a existing daynumber in the variables?
For me work or … i don’t have understand
EXAMPLE
cas1Ref = $sunday
$a1 = 1245,0,10,05.30,3
$a2 = ,22.00,17.5
IF dummy-switch is turned on THEN set $sunday to $a01
$sunday = 1245,0,10,05.30,3
IF dummy-switch is turned off THEN set $sunday to “{$a01}{$a02}”
$sunday = 1245,0,10,05.30,3,22.00,17.5 -
a gui mode would be awesome
maybe someone can assist zacca on this?pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
@Zacca said in New Plugin - ChronoTherm (ex CronoAccesoSpento):
@koffienl said in New Plugin - ChronoTherm (ex CronoAccesoSpento):
Thanks, it’s working.
Problem : you also fixed a ‘bug’ in the previous version I was abusingI have a button called “today as sunday”. When this button is switched to ON I do the following: take the contents of
$AtHome
(this vart is not used by the plugin) and take the daynumber of the week and put this in a existing variable used by the plugin:IF sunday is turned on THEN $ThermoThuis = "{$weekday.text}{$AtHome}"
This worked in the previous version. When same dynbumber was used in multiple variables/programs the latest was used. It looks like that you ‘fixed’ this in the current version.
As soon as one daynumber is used more than 1 time, the colored bars disappear.Is it home somehow possible to allow a redefinition of a existing daynumber in the variables?
For me work or … i don’t have understand
EXAMPLE
cas1Ref = $sunday
$a1 = 1245,0,10,05.30,3
$a2 = ,22.00,17.5
IF dummy-switch is turned on THEN set $sunday to $a01
$sunday = 1245,0,10,05.30,3
IF dummy-switch is turned off THEN set $sunday to “{$a01}{$a02}”
$sunday = 1245,0,10,05.30,3,22.00,17.5Not sure if I understand you :P
For now I have:
$ThermoWerkdag 1245,0,17.5,05.30,19.5,07.30,18,13.30,20,22.00,17.5
$ThermoThuis 3,0,17.5,05.30,19.5,07.30,20,22.00,17.5
$ThermoWeekend 67,0,18,07.00,20,22.00,18That is working, without a problem. With rules I want to change
$ThermoThuis
from3,0,17.5,05.30,19.5,07.30,20,22.00,17.5
to for example43,0,17.5,05.30,19.5,07.30,20,22.00,17.5
(notice that I added day 4 on the beginning). Since that day is already defined in$ThermoWerkdag
the entire device on the GUI changes to ‘blank’ (al the red/green bars disappear). If I remove day 4 from either$ThermoWerkdag
or$ThermoThuis
the bars appear again.Also sometimes the green circle with the current temperature reports 0. Not sure if this is a display update thing or something else?
Like my projects and help? Consider donating electroneum etnjwAKGPqF6omQWRmpp9u2BPyVDG9VuyRQjNJ1S8yfBdfR9qeUQ46kRy8KS2CNqbpNLRrsgmNW6F2TMzxmZgPrh6KctrkrYbm
-
@koffienl said in New Plugin - ChronoTherm (ex CronoAccesoSpento):
@Zacca said in New Plugin - ChronoTherm (ex CronoAccesoSpento):
@koffienl said in New Plugin - ChronoTherm (ex CronoAccesoSpento):
Thanks, it’s working.
Problem : you also fixed a ‘bug’ in the previous version I was abusingI have a button called “today as sunday”. When this button is switched to ON I do the following: take the contents of
$AtHome
(this vart is not used by the plugin) and take the daynumber of the week and put this in a existing variable used by the plugin:IF sunday is turned on THEN $ThermoThuis = "{$weekday.text}{$AtHome}"
This worked in the previous version. When same dynbumber was used in multiple variables/programs the latest was used. It looks like that you ‘fixed’ this in the current version.
As soon as one daynumber is used more than 1 time, the colored bars disappear.Is it home somehow possible to allow a redefinition of a existing daynumber in the variables?
For me work or … i don’t have understand
EXAMPLE
cas1Ref = $sunday
$a1 = 1245,0,10,05.30,3
$a2 = ,22.00,17.5
IF dummy-switch is turned on THEN set $sunday to $a01
$sunday = 1245,0,10,05.30,3
IF dummy-switch is turned off THEN set $sunday to “{$a01}{$a02}”
$sunday = 1245,0,10,05.30,3,22.00,17.5Not sure if I understand you :P
For now I have:
$ThermoWerkdag 1245,0,17.5,05.30,19.5,07.30,18,13.30,20,22.00,17.5
$ThermoThuis 3,0,17.5,05.30,19.5,07.30,20,22.00,17.5
$ThermoWeekend 67,0,18,07.00,20,22.00,18That is working, without a problem. With rules I want to change
$ThermoThuis
from3,0,17.5,05.30,19.5,07.30,20,22.00,17.5
to for example43,0,17.5,05.30,19.5,07.30,20,22.00,17.5
(notice that I added day 4 on the beginning). Since that day is already defined in$ThermoWerkdag
the entire device on the GUI changes to ‘blank’ (al the red/green bars disappear). If I remove day 4 from either$ThermoWerkdag
or$ThermoThuis
the bars appear again.Yes is normaly, the filter check if a day is double or absent and then mark error.
Alternative is then put a variable only for the 4 day.
If …ON… then @day4is 4,0,17.5,05.30,19.5,07.30,20,22.00,17.5
If …OFF… then @day4is 4,0,17.5,05.30,19.5
the day 4 is always present and no errorAlso sometimes the green circle with the current temperature reports 0. Not sure if this is a display update thing or something else?
Uhmmm 0 is when it’s a error, can you tell me better when it does, random or … ?