(2016-03-11, 01:05)pkscout Wrote:

(2016-03-10, 11:04)rafikW Wrote: So far it running perfectly but I have one question: I see information on screen is presented only when in csv file there are more than 15 lines. If there is less - black screen without values is shown. Why is it that limit?

I honestly don't know. I didn't intentionally code anything to ignore a file with less than 15 lines, but it's possible that some of the logic to find the last line of the file (without having to read the whole thing in to memory) might have caused that. I'm guessing I never noticed because the SpeedFan log file very quickly gets longer than 15 lines, so the only time this would be an issue is for a few seconds right after the log file rolls each day. Since I'm not usually up and checking temps at midnight, I never noticed.

If you post a debug log (turn on debugging in both Kodi *and* in the SpeedFan settings) with a file of less than 15 lines, maybe something will jump out that I can fix.

(2016-03-11, 11:33)rafikW Wrote: Hi, here you are the log:

10:26:02 128490.687500 T:1344373824 NOTICE: [SpeedFan Info] script version 0.7.2 started
10:26:02 128490.687500 T:1344373824 NOTICE: [SpeedFan Info] debug logging set to true
10:26:02 128490.750000 T:1344373824 ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <type 'exceptions.IndexError'>
Error Contents: string index out of range
Traceback (most recent call last):
File "/storage/.kodi/addons/script.speedfaninfo/default.py", line 55, in onInit
self._populate_from_all_logs()
File "/storage/.kodi/addons/script.speedfaninfo/default.py", line 158, in _populate_from_all_logs
self._populate_from_log()
File "/storage/.kodi/addons/script.speedfaninfo/default.py", line 168, in _populate_from_log
temps, speeds, voltages, percents = self._parse_log()
File "/storage/.kodi/addons/script.speedfaninfo/default.py", line 109, in _parse_log
first, last = self._read_log_file()
File "/storage/.kodi/addons/script.speedfaninfo/default.py", line 287, in _read_log_file
first = self._parse_line( f, 0 )
File "/storage/.kodi/addons/script.speedfaninfo/default.py", line 263, in _parse_line
if read_str[offset - 1] == '\n':
IndexError: string index out of range
-->End of Python script error report<--
10:26:05 128493.203125 T:1344373824 NOTICE: [SpeedFan Info] script stopped



I suspect it could be related to values in column "Seconds"
When I was performing my tests I simply generated some values for that column and probably I did not followed the order.
Do you know how those values are calculated?

(2016-06-07, 20:12)rafikW Wrote: Hi,
Using Keymap Editor you can assign any of TV remote's button to launch speedfan window.
I did that so when I press "red" button on my TV remote it popup Compact Display window of speedfan.
One question only: would it be possible that pressing again assigned button Compact Display window will be closed? In current speedfan version in order to close that Compact Display window it is required to press "Back" button on TV remote.

(2016-06-07, 22:54)pkscout Wrote:

(2016-06-07, 20:12)rafikW Wrote: Hi,
Using Keymap Editor you can assign any of TV remote's button to launch speedfan window.
I did that so when I press "red" button on my TV remote it popup Compact Display window of speedfan.
One question only: would it be possible that pressing again assigned button Compact Display window will be closed? In current speedfan version in order to close that Compact Display window it is required to press "Back" button on TV remote.

Unfortunately, no. At least I'm pretty sure the answer is no. You have to define in the addon what key commands will do what, and there's no way to know what command someone might have chosen. I used to use a remote keymap program that had some logic to it, so it would know if SpeedFan was running and quit it if I hit the same key again. But the key mapper got kind of temperamental, so I went with something else that doesn't have the logic pieces. Now I do the same thing you do. I hit a key to launch speed fan and BACK to quit it.

(2016-07-20, 21:03)johntaaffe Wrote: I'm not sure if this is an issue with the latest version of Speedfan or if this will help anyone else, but I could only get Celsius temps to display in Kodi. Might be an issue with the latest release of Speedfan, but it will only log in Celsius. Switching between Celsius and Fahrenheit in Kodi only changes whether "F" or "C" is used.

I played around with _parse_log in default.py and added a Fahrenheit conversion when Fahrenheit is selected in Kodi. Here is the github fork I made if anyone else has run into this issue:

https://github.com/johnftaaffe/script.speedfaninfo

This will be unnecessary for anyone only using Celsius and should be avoided by anyone somehow already logging in Fahrenheit.

(2016-07-21, 14:19)pkscout Wrote:

(2016-07-20, 21:03)johntaaffe Wrote: I'm not sure if this is an issue with the latest version of Speedfan or if this will help anyone else, but I could only get Celsius temps to display in Kodi. Might be an issue with the latest release of Speedfan, but it will only log in Celsius. Switching between Celsius and Fahrenheit in Kodi only changes whether "F" or "C" is used.

I played around with _parse_log in default.py and added a Fahrenheit conversion when Fahrenheit is selected in Kodi. Here is the github fork I made if anyone else has run into this issue:

https://github.com/johnftaaffe/script.speedfaninfo

This will be unnecessary for anyone only using Celsius and should be avoided by anyone somehow already logging in Fahrenheit.

I haven't updated SpeedFan in forever, so I haven't seen this yet. I'm out of town right now, but when I get back I'll look into this and see if I can duplicate it.