New Plugin - ChronoTherm (ex 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
• 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.

@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 possible

@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 possible

Uhmmm 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 rules

if 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 rules

if 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.

@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 rules

if 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 rules

if 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,18

All the other variables where empty, but also I copied the contents of $ThermoWeekend to $thermo4 , $Thermo5, $Thermo6 and $Thermo7

@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 rules

if 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,18

All 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 update

For 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 abusing

I 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?

@koffienl said in New Plugin - ChronoTherm (ex CronoAccesoSpento):

Thanks, it’s working.
Problem : you also fixed a ‘bug’ in the previous version I was abusing

I 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?

@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 abusing

I 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

Not 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,18

That is working, without a problem. With rules I want to change $ThermoThuis from 3,0,17.5,05.30,19.5,07.30,20,22.00,17.5 to for example 43,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?

@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 abusing

I 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

Not 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,18

That is working, without a problem. With rules I want to change $ThermoThuis from 3,0,17.5,05.30,19.5,07.30,20,22.00,17.5 to for example 43,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 error

Also 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 … ?

Nice Work, i like it.
But two questions:

How can i use it as a Shiftworker? Making two Sets of Varaiables and write them alternately to the original variablels? Or is there a better way?

The “turnauto” time is set in seconds, not minutes,right?

Gruß M.

@Michael-Rudek said in New Plugin - ChronoTherm (ex CronoAccesoSpento):

Nice Work, i like it.
But two questions:

How can i use it as a Shiftworker? Making two Sets of Varaiables and write them alternately to the original variablels? Or is there a better way

Yes, I think is the best solution

The “turnauto” time is set in seconds, not minutes,right?

Gruß M.

Yes sorry, in seconds
I had put in minutes but i don t know why it s in seconds
In the next release i put it again in minutes. It s more logical
Thanks

How can i get the Value from $room.result . If i look at the Variables i get a 19 or something like that.
I tried to copy the variable into an other variable but i get always 0(Zero)
I want to send the Value to my Heater via MQTT, but it is always 0.
The other Variables are no Problem, only $room.result is acting like this.

Gruß M.

@Michael-Rudek said in New Plugin - ChronoTherm (ex CronoAccesoSpento):

How can i get the Value from $room.result . If i look at the Variables i get a 19 or something like that.
I tried to copy the variable into an other variable but i get always 0(Zero)
I want to send the Value to my Heater via MQTT, but it is always 0.
The other Variables are no Problem, only $room.result is acting like this.

Gruß M.

Yes thanks
Bug fixed

Tomorrow I hope to release the new version 1.9.5

Feedback V1.9.5

$room.result works now

The realtemperature jumps from Time to Time to 0°
"Temperatur Schlafzimmer" is the connected Sensor (DS18B20 on Raspberry)

Using the api:
/api/device/room/changeTemperatureTo?manuTemp=22 works
/api/device/room/changeModeTo?mode=auto works
/api/device/room/changeModeTo?mode=manu works
/api/device/room/changeModeTo?mode=off works
/api/device/room/changeModeTo?mode=boost does not work.
The api reports {"success":true} but doesnt switch.

Gruß M.

@Zacca Would be nice, if you could publish the plugin to npm.