Announcement

Collapse
No announcement yet.

hs.WriteLog as an immediate command

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

    hs.WriteLog as an immediate command

    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



    #2
    Try &nhs

    Comment


      #3
      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

      Comment


        #4
        I doubt you will find it documented in "the manual." Try here: https://forums.homeseer.com/forum/ho...54#post1060954
        HomeSeer Version: HS3 Pro Edition 3.0.0.500
        Operating System: Microsoft Windows 10 Pro - Work Station

        Enabled Plug-Ins:
        2.1.0.119: AmbientWeather | 3.0.21.0: BLLock | 2.0.24.0: BLUPS | 1.3.6.0: Device History | 3.0.0.56: EasyTrigger | 3.1.0.7: MeiHarmonyHub | 3.0.6681.34300: UltraCID3 | 3.0.6644.26753: UltraLog3 | 3.0.6554.33094: UltraMon3 | 3.0.0.91: weatherXML | 3.0.1.245: Z-Wave | 3.0.51: HS Touch Designer | 3.0.0.40 Z-Seer+

        Comment


          #5
          Originally posted by kenm View Post
          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.
          ​​​​​​

          Comment


            #6
            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

            Comment

            Working...
            X