New Plugin - ChronoTherm (ex CronoAccesoSpento)

---

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

I 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

@Michael-Rudek
Ok try again

@Zacca
Sorry, i´m on the graveyard-shift now.

Looks good now, i will test it the next days excessive.

But your new Timersettings make a new Problem. Because you kicked the TurnAuto the Manu/On/Off-Mode will never be switched back to Auto-mode if you are using the spinwheel or switch by api.
I think the best Solution would be to turn back to Auto with the next Event on the Timeline.The Off-Mode can/should stay off, but the Manu- and On-Mode should be switched back after a Time or with the next Event

M.

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

@Zacca
Sorry, i´m on the graveyard-shift now.

Looks good now, i will test it the next days excessive.

But your new Timersettings make a new Problem. Because you kicked the TurnAuto the Manu/On/Off-Mode will never be switched back to Auto-mode if you are using the spinwheel or switch by api.

Sorry but could you explain better please

I think the best Solution would be to turn back to Auto with the next Event on the Timeline.The Off-Mode can/should stay off, but the Manu- and On-Mode should be switched back after a Time or with the next Event

M.

I think it’s illogical, if you want the manu/off/on for 15 hours you have to reprogram all the schedule.
heheheheh I think it is more logical to fix what you said before, but I did not understand

@Zacca
/api/device/room/changeTemperatureTo?manuTemp=22 switches to Manu, but never back to Auto.

The same with
.
There are no Timersettings and no TurnAuto

The New Timersettings are good for Off-Mode (Holidays, if not longer then 24h!)

For just raising the Temperature by 0.5° they are uncomfortable.

@Michael-Rudek Sorry but it’s complicatet to write code to create a timersettings that work with api.
In my opinion the timersettings for web interface work well as it is.
The problem is how to create a “simple” solution for api.

Just published on npm

@Zacca Brilliant, really good job!

Hi,

I’m following this post for some time and waited that long for it to be released via npm
I installed the plugin, restarted pimatic, activated the plugin via GUI and restarted pimatic but it didn’t come up again. I manually deactivated the plugin in the config.json and pimatic started working.
I know that I didn’t totally follow your instructions, but I think it shouldn’t behave like this, when there is no device configured but the plugin is activated.
I will go on testing!

@quotschmacher Post your Log and check your config. Every ,is important
Did you make the 7 variables?

@Michael-Rudek no - like I said: just installed and activated the plugin and did nothing else. I see that the instructions are a lot longer, but I don’t thing that an activated plugin should prevent the whole system from restarting. The log in the UI does not report any errors. The UI didn’t even come up.

@quotschmacher If Pimatic doesn´t start,check the Log. pimatic-daemon.log. Scroll down to the Part where Pimatic is exiting…

And follow the instructions on Top of this site. I don´t think that the missing Variables prefend Pimatic from starting, but i didn´t test it

@Zacca in the https://github.com/AleZac/pimatic-chronotherm/blob/master/README.md is still a turnauto in the Text that should be removed.