version 0.1.2 released 2018-03-30
- hide sparklines initially for all numeric attributes
New plugin [pimatic-datetime]
version 0.1.2 released 2018-03-30
@saxnpaule said in New plugin [pimatic-datetime]:
The datetime plugin wasn’t build for displaying things.
What you realized is a device and for me devices were always for displaying in the past. I see no problem in displaying it. It has working xAttributes ‘hidden’ and ‘displaySparkline’, the only thing I see which is missing is the a ‘label’ property for each attribute.
As far as I can see, there is no possibility to define a label/acronym for a variable in a “normal” device. Its only possible in a generic VariableDevice. Or is there something I don’t have in mind @mwittig
version 0.2.0 released 2018-04-03
@SaxnPaule I have file a pull request with a few suggested changes to improve the code. The most important one for me was to get rid of the second timer. Attributes are now updated when the reload cycle is performed. I have also tried to reduce code duplication by using the @_createGetter helper. Please give it a try.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
Pull request was already merged. Nice improvement. Thank you.
version 0.3.0 released 2018-04-12
Hi, nice plugin. It is a pity that this has been forgotten. This would be enough and not just for work with time and date.
Pimatic = Smart Home
@saxnpaule said in New plugin [pimatic-datetime]:
Have a look here: https://forum.pimatic.org/topic/4141/date-time-difference-expressions-and-calculation/14
Yes, I’ve already seen it.
My proposed solution, 2 years ago, allows much wider use than just date diff. And without Pimatic core modification. Without another plugin and many unused variables.
http://www.fresse.org/dateutils/
Not to mention the possibility to use many other programs/utilities/scripts (ls, ps, cat, jq and so on).
Pimatic = Smart Home
I have a slight problem which might be a bug in the system. The rule
when every 10 minutes then set $woliSpeech to “$myTimeDateDevice.time”
delivers 21:09, 21:19,… instead of the expected 21:10, 21:20 …
Same with other conditions like
when every 1 hour…
Always one minute to less.
Well, another candidate for a workaround. I use now
when every 10 minutes then set $woliSpeech to “$myTimeDateDevice.time” after 10 seconds
Not fine, but it works.