Announcement

Collapse
No announcement yet.

Logfile is set to /JowiHue.log

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Logfile is set to /JowiHue.log

    I got this in hs logs. So a file is created outside hs4 root folder.

    it is in fact created in the root of my hard drive ( think it is releated to the last e-mail I sent you :
    7/10/2020 20:00:19


    JowiHue
    Info
    Logfile is set to /HomeSeer/Logs/JowiHue.log
    7/10/2020 20:00:19


    JowiHue
    Info
    Logfile is set to /JowiHue.log


    Attached Files

    #2
    Matthieu,

    I think you are pointing to two kinds of logs. JowiHue.log is a file that - depending on the version of the plugin - should be created in /<hs install folder>/ or (latest version) /<hs install folder>/Logs directory. You can check for this when you set the log to files options in the tracing options. If this log ends up in the root folder, I don't know why as it is using the HS variable "apppath" for setting the location. That would suggest this variable is not correctly set by HS in Linux? It works in Windows here. Can you check where the file with the name 'JowiHue.log" is located when you enable the log to file option?

    The file JowiHue.console.txt is a different file that is not created or used by the plugin. Don't know if this file gets created when you enable the developer mode in the HS4 settings? Is it possible the console output in Linux is forwarded to a text file maybe? I have no clue from here on that one.

    Wim
    -- Wim

    Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData

    1210 devices/features ---- 392 events ----- 40 scripts

    Comment

    Working...
    X