Weirt example in Choosing a Start Time

[pando85]

What happened?

Documentation says:

Choosing a Start Time
~~~~~~~~~~~~~~~~~~~~~

Internally, AppDaemon keeps track of its own time relative to when it
was started. This make it possible to start AppDaemon with a different
start time and date to the current time. For instance, to test that
sunset App, start AppDaemon at a time just before sunset and see if it
works as expected. To do this, simply use the "-s" argument on
AppDaemon's command line. e.g.:

.. code:: bash

    $ apprun -s "2018-23-27 16:30:00"
    ...
    2018-12-27 09:31:20.794106 INFO     AppDaemon  App initialization complete
    2018-23-27 16:30:00.000000 INFO     AppDaemon  Starting time travel ...
    2018-23-27 16:30:00:50.000000 INFO     AppDaemon  Setting clocks to 2018-23-27 16:30:00
    2018-23-27 16:30:00.000000 INFO     AppDaemon  Time displacement factor 1.0
    ...

Note the timestamps in the log - AppDaemon believes it is now just
before sunset and will process any callbacks appropriately.

If you see that is not a valid datetime. I just wanted to point that it could be validated and also docu is weird with that value.

I don't use that functionality because it doesn't overwrite datetime.datetime.now() but I wanted to report it.

Version

4.4.2

Installation type

Home Assistant add-on

Relevant log output

No response

Relevant code in the app or config file that caused the issue

No response

Anything else?

No response