Announcement

Collapse
No announcement yet.

Device property does not survive an hs3 reboot

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

    Device property does not survive an hs3 reboot

    Hi,


    I just realised that some devices property are not persistent across reboots.


    Here is an example of a root device create by mcsmqtt plugin.


    The first picture is what i want.

    The second picture is what it is reverted to after a reboot.
    Attached Files

    #2
    also got this in hs3 log... seems to miss the mcs part of mcsMQTT? :
    Apr-28 16:13:17 Warning File does not exist: /HomeSeer/html/MQTT
    Apr-28 16:13:17 Warning File does not exist: /HomeSeer/html/MQTT
    Apr-28 16:13:17 Warning File does not exist: /HomeSeer/html/MQTT
    Apr-28 16:13:17 Warning File does not exist: /HomeSeer/html/MQTT
    Apr-28 16:13:17 Warning File does not exist: /HomeSeer/html/MQTT

    Comment


      #3
      Can you explain the relationship of these posts to mcsSprinklers?

      Also note that the Control Status UI in the original screenshot is unspecified which means an unstable/indeterminate state. The second screen shot shows that data has been received that makes it appear that the payloads are numeric.

      On post #2 there is not enough information to know what is producing this output. It seems there may a device string somewhere that has a href that has become obsolete.

      Comment


        #4
        Originally posted by Michael McSharry View Post
        Can you explain the relationship of these posts to mcsSprinklers?
        I am really sorry i posted in the wrong thread.

        Also note that the Control Status UI in the original screenshot is unspecified which means an unstable/indeterminate state. The second screen shot shows that data has been received that makes it appear that the payloads are numeric.
        Ok I think this might explain the problem.


        i’ll dig more tomorrow and will create another subjet in the good subforum if there is a need .



        On post #2 there is not enough information to know what is producing this output. It seems there may a device string somewhere that has a href that has become obsolete.
        Ok i'll keep an eye!


        thanks again for your insight.

        Comment

        Working...
        X