a gui mode would be awesome
maybe someone can assist zacca on this?
-
New Plugin - ChronoTherm (ex CronoAccesoSpento)
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 … ?
-
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 fixedTomorrow I hope to release the new version 1.9.5
-
Feedback V1.9.5
$room.result
works nowThe 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.
pimatic-google-calendar | pimatic-wmi | pimatic-snmp | pimatic-wakeonlan |
Like my work? Then consider a donation
Follow me: www.thorstenreichelt.de -
The 0° happens if the Temperature Sensor reports something with “.00”.
Like 20.00 , 21.00 etc.
Gruß M. -
@Michael-Rudek said in New Plugin - ChronoTherm (ex CronoAccesoSpento):
Feedback V1.9.5
$room.result
works nowThe 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.
Yes Thanks, i have see
-
@thost96 said in New Plugin - ChronoTherm (ex CronoAccesoSpento):
@Zacca Would be nice, if you could publish the plugin to npm.
I m working to a new function, after that i will register to npm
-
@Michael-Rudek said in New Plugin - ChronoTherm (ex CronoAccesoSpento):
The 0° happens if the Temperature Sensor reports something with “.00”.
Like 20.00 , 21.00 etc.
Gruß M.Thanks…you are my best beta tester
I have insert this function but for now I have no way to try it.
I made a patch and I hope it works, but we will see only the next few days -
New version 0.9.6
-
Version 0.9.6
Can´t really test it.
At first it worked and i couldt switch to Manuell-Mode, but now it stucks in Auto-mode.
Can´t switch to Manuell. Restarted Pimatic, restartet Raspberry, no Changes.What i saw in the moments it worked:
“Calcel” should be “Cancel”
Roomtemperature shows now 22.9°, not 22.934° ,Great
Sorry to say that
M.
-
@Michael-Rudek i m desolated
Have you try to create a new one? Or change manu mode from rules?
I don t understand why do so.
Tomorrow i will check all my code -
@Zacca I made a new one and its the same with one Difference.
The Timer Field is empty:
What i can see, is that the mode is switched for a short time. I can´t see it in Pimatic but a triggert Rule sends the status via MQTT to my Particle Photon.
I tried to switch via the API, but its the same Result.Is there a way to reset all the Timers?
@All Is someone else testing this Plugin and can Report the same Problem?
-
@Michael-Rudek said in New Plugin - ChronoTherm (ex CronoAccesoSpento):
@Zacca I made a new one and its the same with one Difference.
The Timer Field is empty:
What i can see, is that the mode is switched for a short time. I can´t see it in Pimatic but a triggert Rule sends the status via MQTT to my Particle Photon.
I tried to switch via the API, but its the same Result.Is there a way to reset all the Timers?
@All Is someone else testing this Plugin and can Report the same Problem?
@Michael-Rudek said in New Plugin - ChronoTherm (ex CronoAccesoSpento):
@Zacca I made a new one and its the same with one Difference.
The Timer Field is empty:
What i can see, is that the mode is switched for a short time. I can´t see it in Pimatic but a triggert Rule sends the status via MQTT to my Particle Photon.
I tried to switch via the API, but its the same Result.Is there a way to reset all the Timers?
No, the timer reset every time that start the function
@All Is someone else testing this Plugin and can Report the same Problem?
Sorry Michael but i ll check it only tomorrow
In the week end i v only a tablet. I think is not the right way to change some code -
@Zacca
No need to hurry. There is no “Real” Heater connectedI tested the Lite Version too. Can’t switch On or Off, always Auto.
Maybe its easier to start there.
Have a nice weekend. -
I think it s a conflict to the id of timeoutinput.
Tomorrow I ll change it