hs.WriteLog as an immediate command

[kenm]

I'm feeling kind of like a turtle on his back right about now. Something that seems so simple isn't working.

For testing various event logic I commonly use (or used to in HS3) hs.WriteLog as the action for an event. For some reason, I can't seem to get this to work in HS4.

&hs.WriteLog("Debug", "Device 980 Reset") as an immediate command yields the following error in the log:

Running script(2) &hs.WriteLog("Debug", "Device 980 Reset"), init error: Class doesn't support Automation: 'hs.WriteLog'

Any help would be appreciated.

Ken

[Guest]

Try &nhs

[kenm]

Thanks. That worked, but now I'm really confused. Where is this documented and why the change? Also, why does hs.WriteLog work in a script?


Thanks again,
Ken

[ewkearns]

I doubt you will find it documented in "the manual." Try here: https://forums.homeseer.com/forum/ho...54#post1060954

[Guest]

Thanks. That worked, but now I'm really confused. Where is this documented and why the change? Also, why does hs.WriteLog work in a script?


Thanks again,
Ken

Documented here and there in this forum...

haven't migrated to HS4 yet for this reason.
Been assembling personal notes for the last few months on all the bugs and workarounds. Will migrate once the pace of reported issues slows down and/or once I feel HS is fixing them as they come in, which is not the case right now.

[kenm]

Thanks All! I now understand the difference between the two but there's no excuse for this not being documented properly. Then again, nothing with HS4 seems to be properly documented.

Thanks again,
Ken