Free domotica! › Forums › Report a bug › Incorrect timestamp into Log.txt from scene
Tagged: log;scene;timestamp
- This topic has 14 replies, 5 voices, and was last updated 4 years, 9 months ago by
Mika.
-
AuthorPosts
-
March 31, 2016 at 6:42 pm #3112
leroymth
ParticipantHi,
Since update into DSM6.0 or update into PulseStation 1.3.1 yesterday, the timestamp inside log.txt from scene is not correct.Therefore I noticed a lag time…Below an extract….
Typically, log from core process are correctly timestamped…
Thx !
2016-04-01 00:38:00 Periodic : Start 2016-04-01 00:38:01 Periodic : Start 2016-04-01 00:38:03 Periodic : End 2016-04-01 00:38:04 Pas de PUSH TEMPERATURE SALLE 2016-04-01 00:38:04 Je bouge pas 2016-04-01 00:38:04 [LUMINOSITE]=>42 2016-04-01 00:38:04 [SENSOR]=>False 2016-04-01 00:38:04 [TEMPERATURE]=>21.0 2016-04-01 00:38:04 [BATTERIE]=>100 2016-04-01 00:38:04 [REVEIL]=>3600 2016-04-01 00:38:04 [REPORTING LUMIERE TRESH]=>0 2016-04-01 00:38:04 [REPORTING LUMIERE INT]=>1800 2016-04-01 00:38:04 [LED SIGNALING MODE]=>LED inactive. 2016-04-01 00:38:04 [TEMPERATURE OFFset]=>-11 2016-04-01 00:38:04 Periodic : End 2016-04-01 00:38:05 Pas de PUSH TEMPERATURE SALLE
March 31, 2016 at 9:46 pm #3113vryf
ParticipantBonjour,
Même constat pour moi.
Le log “scene” est décalé de +6 heures par rapport à l’heure locale connue du système.
Cordialement,
FVMarch 31, 2016 at 10:06 pm #3114leroymth
ParticipantAnother complement, it’s impact blocky scenes as soon as we are using the notion of time….typically my scene setted @ midnight are postponed….even for summer/winter hour the gap is important 😀
April 2, 2016 at 11:54 am #3118MacDavis
ParticipantHello,
I have the same problem.
Somebody knows like solving it?(PulsStation on a DS412+)
April 4, 2016 at 9:36 am #3125Mika
KeymasterI’ll check it, I don’t notice that.
April 4, 2016 at 9:42 am #3128K.Rens
KeymasterIf you enter following command in ssh, do you get the correct time and date?:
date
Kind regards,
K.RensApril 4, 2016 at 9:51 am #3129leroymth
ParticipantHi,
On my side date function give me correct datetime.
RegardsApril 4, 2016 at 7:57 pm #3135Mika
KeymasterDo you have the same problem for all log info for each services (eg : vdevices)?
What you can try is create a simple file “date.php” file inside “/web” folder ?
And add this line :Then try to access the file via http://ipsyno/date.php
If you see that the time have 6 hours less/more
, it’s probably a problem regarding the php configuration.April 4, 2016 at 8:19 pm #3136leroymth
ParticipantHi Mika,
I create the test file as you advised and it return me back correct date time.
“Mon Apr 4 20:14:03 CEST 2016″….so it is not linked to PHP configuration.
To answer to your first question, OZW.log from Zwaves devices is correctly timestamped….
Regards
April 5, 2016 at 4:14 pm #3141April 5, 2016 at 9:34 pm #3143vryf
ParticipantBonsoir,
Je confirme que seul le log “scene” est affecté par le décalage de 6h. Le log des autres services est correct.
Mon NAS est un DS212.
Cordialement,
FVApril 5, 2016 at 9:44 pm #3144leroymth
Participant@ Mika, my NAS Model is a DS213j.
April 18, 2016 at 9:31 pm #3201vryf
ParticipantBonsoir,
Y a t’il du nouveau pour corriger ce bug ?
Merci,
FVApril 18, 2016 at 10:30 pm #3203leroymth
ParticipantBonsoir,
Je pense que le bug est corrigé via la procédure que Mika a diffusé sur le home de l’administration de PulseStation : Ici
Je viens d’appliquer le changement de version PHP et de mon côté l’horodatage de scene.txt est redevenu correct.Exemple du changement dans ma log :
2016-04-19 04:19:05 Periodic : End 2016-04-19 04:19:05 [REPORTING LUMIERE INT]=>1800 2016-04-19 04:19:05 [LED SIGNALING MODE]=>LED inactive. 2016-04-19 04:19:05 [TEMPERATURE OFFset]=>-11 2016-04-18 22:20:02 Periodic : Start 2016-04-18 22:20:03 Periodic : Start 2016-04-18 22:20:06 Periodic : End 2016-04-18 22:20:06 Pas de PUSH TEMPERATURE SALLE
Merci Mika ! Pour moi le bug est résolu
April 19, 2016 at 8:26 pm #3218Mika
KeymasterOK donc je dirais que c’était la version PHP qui était en cause…
-
AuthorPosts
- You must be logged in to reply to this topic.