Announcement

Collapse
No announcement yet.

A call was made to save a global variable (LogMessage) but that global variable ...

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

  • rprade
    replied
    It is normal to see that error in the log the first time a global variable is used after a restart. Global variables are not durable - they are lost when HS is restarted. Once they are used they will remain until the next restart. You will only see that error once, after that the variable exists.

    Leave a comment:


  • BigBadBuzz
    replied
    Sorry for the late reply - yes.

    Leave a comment:


  • Ultrajones
    replied
    I assume you only see those "errors" after a restart of the plug-in and on first use of the global variable, correct?

    Leave a comment:


  • BigBadBuzz
    replied
    Oops - sorry, I just realized you had started that thread...

    Sheepishly,
    BBB

    Leave a comment:


  • BigBadBuzz
    replied
    Megaman:

    Refer to this forum thread:

    https://forums.homeseer.com/forum/ul...riable-has-not

    Leave a comment:


  • A call was made to save a global variable (LogMessage) but that global variable ...

    Hi, I've recently been getting these errors.

    Code:
    A call was made to save a global variable (LogMessage) but that global variable has not been defined.
    A call was made to save a global variable (LogType) but that global variable has not been defined.
    I can see the variables listed in the HS global variables page, I wonder if it's caused by the fact that my event was triggered 3 times by matching the word "Error" in quick succession?

    Ultrajones, is this something that can be fixed in the plugin?

    Click image for larger version

Name:	error_rule.PNG
Views:	131
Size:	183.1 KB
ID:	1328946
    Click image for larger version

Name:	error_1.PNG
Views:	88
Size:	249.1 KB
ID:	1328947

    Thanks
Working...
X