Announcement

Collapse
No announcement yet.

Epoch time converting - result will not hold

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

    Epoch time converting - result will not hold

    I created the following flow. When the flow is triggered the Epoch time is correctly converted and the result of the HomeSeer node is equivalent to the Debug node.
    Click image for larger version

Name:	Capture start.png
Views:	57
Size:	102.5 KB
ID:	1600342
    However after 2 minutes the HomeSeer node revert back to the Epoch value, while the result of the debug node is still correct.
    Click image for larger version

Name:	Capture - within 2 minutes.png
Views:	71
Size:	17.0 KB
ID:	1600341

    When I manually trigger the flow after this the correct date and time is displayed.

    Anyone any idea?
    ---
    John


    #2
    Throw a debug node after the HomeSeer node and find when it changes. Are the last message changes between the two debug nodes the same within processing time reason? If not something else is triggering the change. If that is the case, look in the HomeSeer log to see what may have triggered the change.

    If the times are reasonably the same, look at the output of the debug node in the user interface area and make sure the changed value is in the proper variable. Meaning, do not rely on the value shown under the debug node in the flow.

    Without seeing more of the flow, my bet would be on something else changing the HomeSeer device.
    Karl S
    HS4Pro on Windows 10
    1070 Devices
    56 Z-Wave Nodes
    104 Events
    HSTouch Clients: 3 Android, 1 iOS
    Google Home: 3 Mini units, 1 Pair Audios, 2 Displays

    Comment


      #3
      Originally posted by ksum View Post
      Throw a debug node after the HomeSeer node and find when it changes. Are the last message changes between the two debug nodes the same within processing time reason? If not something else is triggering the change. If that is the case, look in the HomeSeer log to see what may have triggered the change.

      If the times are reasonably the same, look at the output of the debug node in the user interface area and make sure the changed value is in the proper variable. Meaning, do not rely on the value shown under the debug node in the flow.

      Without seeing more of the flow, my bet would be on something else changing the HomeSeer device.
      This is the content of the change node:
      Click image for larger version  Name:	image.png Views:	0 Size:	24.1 KB ID:	1600391

      Debug node 43 changes while debug node 42 will not change. There is nothing in the HomeSeer log. This device is not managed by HomeSeer. It is a Node-RED flow that will send information to HomeSeer.

      Click image for larger version  Name:	image.png Views:	0 Size:	33.4 KB ID:	1600394

      The content of the debug node is changing between correct/incorrect/correct,...
      Click image for larger version  Name:	image.png Views:	0 Size:	9.3 KB ID:	1600399

      Comment


        #4
        Originally posted by ksum View Post
        Throw a debug node after the HomeSeer node and find when it changes. Are the last message changes between the two debug nodes the same within processing time reason? If not something else is triggering the change. If that is the case, look in the HomeSeer log to see what may have triggered the change.

        If the times are reasonably the same, look at the output of the debug node in the user interface area and make sure the changed value is in the proper variable. Meaning, do not rely on the value shown under the debug node in the flow.

        Without seeing more of the flow, my bet would be on something else changing the HomeSeer device.
        Posted solution removed as it turned out that it will not work

        Comment


          #5
          Debug node 42 is changing when the flow is initiated upstream of the device node.
          Debug node 43 is changing when the HomeSeer device changes and that node starts a flow message.
          If 43 is getting a message and 42 is not, then something besides this flow is changing the value/status off the HomeSeer device. If this flow to this node changed the device, both debug nodes would receive a message. So if I'm understanding things correctly, I would be trying to figure out what is changing it.

          Try this. Force the flow to run and set the HomeSeer device properly. Then delete the wire going into the HomeSeer device node and save the changes. See if the HomeSeer device changes after 2 minutes. If it doesn't, you know something else is changing the setting.
          ​​​​​
          Karl S
          HS4Pro on Windows 10
          1070 Devices
          56 Z-Wave Nodes
          104 Events
          HSTouch Clients: 3 Android, 1 iOS
          Google Home: 3 Mini units, 1 Pair Audios, 2 Displays

          Comment


            #6
            Originally posted by ksum View Post
            Debug node 42 is changing when the flow is initiated upstream of the device node.
            Debug node 43 is changing when the HomeSeer device changes and that node starts a flow message.
            If 43 is getting a message and 42 is not, then something besides this flow is changing the value/status off the HomeSeer device. If this flow to this node changed the device, both debug nodes would receive a message. So if I'm understanding things correctly, I would be trying to figure out what is changing it.

            Try this. Force the flow to run and set the HomeSeer device properly. Then delete the wire going into the HomeSeer device node and save the changes. See if the HomeSeer device changes after 2 minutes. If it doesn't, you know something else is changing the setting.
            ​​​​​
            Did enter a function node and created 12 new virtual devices. Issue solved. Thanks for thinking with me.

            ---
            John

            Comment

            Working...
            X