Announcement

Collapse
No announcement yet.

HSEvent Line 0 Conversion from string " Date &nbs" to type 'Double' is not valid.

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

  • HSEvent Line 0 Conversion from string " Date &nbs" to type 'Double' is not valid.

    Aug-15 3:14:30 PM mcsMQTT HSEvent Line 0 Conversion from string " Date &nbs" to type 'Double' is not valid.
    I get this in my log file every few minutes. I haven't been able to find out what is causing it. Do you have any ideas?

    Jason

  • #2
    The debug will trace HSEvent which will identify which device is causing issue. General tab to enable. File will be /data/mcsMQTT/mcsMQTTdebug.txt

    Comment


    • #3
      Aug-15 9:30:27 PM mcsMQTT HSEvent Line 0 Conversion from string " Date &nbs" to type 'Double' is not valid.

      From log:
      8/15/2018 9:30:01 PM 82560747 | HSEvent Do= False STRING_CHANGE for Device 216
      8/15/2018 9:30:03 PM 82562557 | HSEvent Do= False STRING_CHANGE for Device 4645
      8/15/2018 9:30:03 PM 82562562 | HSEvent Do= False STRING_CHANGE for Device 4646
      8/15/2018 9:30:05 PM 82565242 | HSEvent Do= True VALUE_CHANGE for Device 731
      8/15/2018 9:30:05 PM 82565242 | HSEvent Add VALUE_CHANGE | 731
      8/15/2018 9:30:05 PM 82565251 | DoHsEvent Topic=STAT/salix/RSEasyTouch%20Device/RSEasyTouch/Pool/Air%20Temperature/RSEasyTouch/731/RSEasyTouch-AirTemp, Payload=72, Template=
      8/15/2018 9:30:05 PM 82565266 | ActoOnMessageFor Trigger Topic sensor/temp/outside-ambient,Payload=72
      8/15/2018 9:30:06 PM 82565282 | ActoOnMessageFor Trigger Topic STAT/salix/RSEasyTouch%20Device/RSEasyTouch/Pool/Air%20Temperature/RSEasyTouch/731/RSEasyTouch-AirTemp,Payload=72
      8/15/2018 9:30:08 PM 82567840 | HSEvent Do= False STRING_CHANGE for Device 4645
      8/15/2018 9:30:08 PM 82567843 | HSEvent Do= False STRING_CHANGE for Device 4646
      8/15/2018 9:30:13 PM 82573076 | HSEvent Do= False STRING_CHANGE for Device 4645
      8/15/2018 9:30:13 PM 82573078 | HSEvent Do= False STRING_CHANGE for Device 4646
      8/15/2018 9:30:18 PM 82578008 | HSEvent Do= False VALUE_CHANGE for Device 4504
      8/15/2018 9:30:19 PM 82578288 | HSEvent Do= False STRING_CHANGE for Device 4645
      8/15/2018 9:30:19 PM 82578291 | HSEvent Do= False STRING_CHANGE for Device 4646
      8/15/2018 9:30:24 PM 82583501 | HSEvent Do= False STRING_CHANGE for Device 4645
      8/15/2018 9:30:24 PM 82583504 | HSEvent Do= False STRING_CHANGE for Device 4646
      8/15/2018 9:30:26 PM 82585365 | HSEvent Do= True VALUE_CHANGE for Device 731
      8/15/2018 9:30:26 PM 82585366 | HSEvent Add VALUE_CHANGE | 731
      8/15/2018 9:30:26 PM 82585373 | DoHsEvent Topic=STAT/salix/RSEasyTouch%20Device/RSEasyTouch/Pool/Air%20Temperature/RSEasyTouch/731/RSEasyTouch-AirTemp, Payload=73, Template=
      8/15/2018 9:30:26 PM 82585388 | ActoOnMessageFor Trigger Topic sensor/temp/outside-ambient,Payload=73
      8/15/2018 9:30:26 PM 82585399 | ActoOnMessageFor Trigger Topic STAT/salix/RSEasyTouch%20Device/RSEasyTouch/Pool/Air%20Temperature/RSEasyTouch/731/RSEasyTouch-AirTemp,Payload=73
      8/15/2018 9:30:26 PM 82586240 | HSEvent Do= True VALUE_CHANGE for Device 1464
      8/15/2018 9:30:26 PM 82586240 | HSEvent Add VALUE_CHANGE | 1464
      8/15/2018 9:30:26 PM 82586248 | DoHsEvent Topic=STAT/salix/Z-Wave%20Luminance/ZWave/Garage/Luminance, Payload=1, Template=
      8/15/2018 9:30:26 PM 82586255 | ActoOnMessageFor Trigger Topic STAT/salix/Z-Wave%20Luminance/ZWave/Garage/Luminance,Payload=1
      8/15/2018 9:30:27 PM 82587108 | HSEvent Do= True STRING_CHANGE for Device 507
      8/15/2018 9:30:29 PM 82588728 | HSEvent Do= False STRING_CHANGE for Device 4645
      8/15/2018 9:30:29 PM 82588731 | HSEvent Do= False STRING_CHANGE for Device 4646
      8/15/2018 9:30:31 PM 82591054 | HSEvent Do= False VALUE_CHANGE for Device 4560
      8/15/2018 9:30:31 PM 82591246 | HSEvent Do= True VALUE_CHANGE for Device 4558
      8/15/2018 9:30:31 PM 82591247 | HSEvent Add VALUE_CHANGE | 4558
      8/15/2018 9:30:31 PM 82591257 | DoHsEvent Topic=STAT/salix/Z-Wave%20Watts/ZWave/Bedroom-Chase/Watts/Z-Wave/4558/003D3969-011-Q67, Payload=192.664, Template=
      8/15/2018 9:30:31 PM 82591263 | ActoOnMessageFor Trigger Topic sensor/watts/bedroom-chase-computer,Payload=192.664
      8/15/2018 9:30:32 PM 82591270 | ActoOnMessageFor Trigger Topic STAT/salix/Z-Wave%20Watts/ZWave/Bedroom-Chase/Watts/Z-Wave/4558/003D3969-011-Q67,Payload=192.664
      8/15/2018 9:30:32 PM 82592043 | HSEvent Do= True VALUE_CHANGE for Device 3887
      8/15/2018 9:30:32 PM 82592043 | HSEvent Add VALUE_CHANGE | 3887
      8/15/2018 9:30:32 PM 82592050 | DoHsEvent Topic=STAT/salix/BLTED%20Plug-In%20Device/BLTED/Z_BLTED/Gateway1%20-%20MTU1%20-%20LowVoltHr/BLTED/3887/BLTED-G01-MTU01-LowVoltHr, Payload=242.2, Template=
      8/15/2018 9:30:32 PM 82592053 | HSEvent Do= True STRING_CHANGE for Device 3887
      8/15/2018 9:30:32 PM 82592055 | HSEvent Add STRING_CHANGE | 3887
      8/15/2018 9:30:32 PM 82592071 | ActoOnMessageFor Trigger Topic STAT/salix/BLTED%20Plug-In%20Device/BLTED/Z_BLTED/Gateway1%20-%20MTU1%20-%20LowVoltHr/BLTED/3887/BLTED-G01-MTU01-LowVoltHr,Payload=242.2
      8/15/2018 9:30:32 PM 82592073 | DoHsEvent Topic=STAT/salix/BLTED%20Plug-In%20Device/BLTED/Z_BLTED/Gateway1%20-%20MTU1%20-%20LowVoltHr/BLTED/3887/BLTED-G01-MTU01-LowVoltHr, Payload=242.2, Template=
      8/15/2018 9:30:32 PM 82592084 | HSEvent Do= True VALUE_CHANGE for Device 3457
      8/15/2018 9:30:32 PM 82592084 | HSEvent Add VALUE_CHANGE | 3457
      8/15/2018 9:30:32 PM 82592090 | HSEvent Do= True STRING_CHANGE for Device 3457


      How do I figure out what is going on?

      Comment


      • #4
        HSEvent do= lines show the call from. HS to notify of a device change including the specific device reference . The times are correlated with the HS log error message. Knowing what device will help understand why. If do is true then the second Parm from HS is converted to double and this could be the error source.

        it looks like an HTML string is what is causing the problem where it has Date text rather than a number.

        Was the error generated during the time of the debug output posted?

        Comment

        Working...
        X