Illia Antypenko

I'm experiencing the same here. It reports wrong values for several seconds and then it's OK.  I've prepared app diagnostic report. It's ID: 1316bf45-c7d1-4abb-8a94-247fbe42c556 

Hi @stevenvachon Thanks for this great tool Do you have any chance to review this PR and related (#148)?

@dulemis I can confirm this and I see the same temperature change on internal AC display. I guess it was added by developers to add some temperature difference between different...

Yes, I don't think that this is a bug. Probably this change is compensating heating/cooling of the temp sensor itself during the work. But it's just my guess.

Just an interesting findings. Several days ago one user reported issues with current temp value. I checked the logs and found this: ``` [finder] Message: { t: 'dev', cid: 'xxxxxxxxx',...

Related to #77 Probably we should consider to use `kernel.cache_dir` instead of hacks with `kernel.root_dir` Also, we need to adjust https://github.com/symfony/recipes-contrib/pull/155 to use `kernel.cache_dir`

About `kernel.cache_dir`. This parameter has environment-dependent value. That means for dev env it will be `/var/cache/dev` and for prod - `/var/cache/prod`. And `lock`/`unlock` will affect only specific env. So, I'm...

Hi @Cypaubr @gizmo-rt Do you remember which exactly symfony3 version did you use? This issues could be caused by https://symfony.com/blog/new-in-symfony-3-3-a-simpler-way-to-get-the-project-root-directory But `%kernel.root_dir%/cache/lock` for symfony3 points to the directory with `AppKernel.php`...

Hi @mrdgama In general it means that your system was not locked with `lexik:maintenance:lock`. Try to call `app/console lexik:maintenance:lock --env prod` before.

@m-vo what is the result of `lexik:maintenance:lock`? Which driver are you using? File?