Thank you sir, that solved it. Another dent in the ego
Cheers
Announcement
Collapse
No announcement yet.
How to log less frequently
Collapse
X
-
Originally posted by Whitenoise View PostAfter reinstalling my HS, I get the same issue. I just cant get it to log:
If I run this, all that comes into the log is this:
I also tried with just some random text instead of the devicevalue. My log settings are:
Any Ideas?
Cheers
Whitenoise
- Likes 1
Leave a comment:
-
After reinstalling my HS, I get the same issue. I just cant get it to log:
If I run this, all that comes into the log is this:
I also tried with just some random text instead of the devicevalue. My log settings are:
Any Ideas?
Cheers
Whitenoise
Leave a comment:
-
My log is now smooth as silk. Thank you all, truly appreciated.
Cheers
Whitenoise
Leave a comment:
-
Originally posted by Whitenoise View PostI now get the values, but without the decimals, with this command:
&nhs.WriteLog("AnyText", "Device value is " & hs.DeviceValue(163).ToString())
Any idea how to log the value with decimals?
&nhs.WriteLog("AnyText", "Device value is " & hs.DeviceValueEx(163).ToString())
Leave a comment:
-
Ok, I did get it to work, and yes it is very embarrassing. I had a Z-wave filter on in the log....
I now get the values, but without the decimals, with this command:
&nhs.WriteLog("AnyText", "Device value is " & hs.DeviceValue(163).ToString())
Any idea how to log the value with decimals?
Cheers
Whitenoise
Leave a comment:
-
This is getting embarrassing. I change the line, still nothing in the log. I run a HS4 on a Raspberry Pi. I saw that you used a dot (.) in the command, I assumed it should be a comma. Anyway, i tried both and with semicolon to be sure. I still only get Z-wave events in the log...
Thank you for your help
Whitenoise
Leave a comment:
-
I'm running HS4 and the &nhs.WriteLog command in post #6 works for me.
Leave a comment:
-
Originally posted by w.vuyk View PostI have understood that writelog is no longer working as immediate command. You would need to change it to &hs.writelogex("Test", "This is a test log entry". "")
Just Wow.
Any explanation for why?
Is this a bug or is it deliberate?
Is anyone keeping a list of the traps the have been set in HS4 for the unsuspecting?
Leave a comment:
-
You are running HS4. I have understood that writelog is no longer working as immediate command. You would need to change it to &hs.writelogex("Test", "This is a test log entry". "")
Watch the extra parameter. It can be an empty string or a color hex code to color the logline.
Wim
- Likes 1
Leave a comment:
-
That is correct, there are no errors in log, only spam from a Z-wave node. I even tried this:
&hs.WriteLog "Test", "This is a test log entry"
And i tried to run it, but nothing in the log. It must be some setting I dont know of...
Cheers
Whitenoise
Leave a comment:
-
I assume there are no errors in the log.
What happens if you run the event with the event run icon?
How about trying something simpler:
&hs.WriteLog "AnyText",hs.DeviceValue(144)
Leave a comment:
-
Is Auto-update checked on your log page? I don't have any other ideas. If your syntax were wrong you should be seeing scripting errors in the log. There may be some other global log setting that I'm not thinking of. Maybe check Setup. If none of that helps, hopefully someone else will jump in with suggestions.
Leave a comment:
Leave a comment: