NS Status Error: TypeError: Cannot read property 'toString' of null
Opened this issue · 0 comments
jimboca commented
The full snippet of the log is below, which shows the error:
2018-5-1 03:01:02 - error: HarmonyHub(2): NS Status Error: TypeError: Cannot read property 'toString' of null
and then for some reason, it set's the controller ST to zero?
2018-5-1 03:01:02 - info: HarmonyHub(2): n002_harmonyctrl ST set sucessfully to 0 : UOM 2
This is during the 3am query all, so it's really busy.
2018-5-1 03:01:01 - info: HarmonyHub(2): Processing command: status
2018-5-1 03:01:01 - debug: MQTTP: nsCommand Message: {"status":{"value":2.1,"driver":"GV1","address":"harmonyctrl","uom":56},"node":"2"}
2018-5-1 03:01:01 - info: HarmonyHub(2): Processing command: status
2018-5-1 03:01:01 - debug: ISY: 200 - http://192.168.86.64:80/rest/ns/2/report/request/4606/success
2018-5-1 03:01:01 - debug: MQTTP: nsCommand Message: {"status":{"value":11,"driver":"GV2","address":"harmonyctrl","uom":56},"node":"2"}
2018-5-1 03:01:01 - info: HarmonyHub(2): Processing command: status
2018-5-1 03:01:01 - debug: MQTTP: nsCommand Message: {"status":{"value":2,"driver":"GV3","address":"harmonyctrl","uom":25},"node":"2"}
2018-5-1 03:01:01 - info: HarmonyHub(2): Processing command: status
2018-5-1 03:01:02 - debug: MQTTP: nsCommand Message: {"status":{"value":null,"driver":"GV4","address":"harmonyctrl","uom":25},"node":"2"}
2018-5-1 03:01:02 - info: HarmonyHub(2): Processing command: status
2018-5-1 03:01:02 - debug: MQTTP: nsCommand Message: {"status":{"value":5,"driver":"GV5","address":"harmonyctrl","uom":25},"node":"2"}
2018-5-1 03:01:02 - info: HarmonyHub(2): Processing command: status
2018-5-1 03:01:02 - debug: MQTTP: nsCommand Message: {"status":{"value":60,"driver":"GV6","address":"harmonyctrl","uom":25},"node":"2"}
2018-5-1 03:01:02 - info: HarmonyHub(2): Processing command: status
2018-5-1 03:01:02 - debug: MQTTP: nsCommand Message: {"status":{"value":1,"driver":"GV7","address":"harmonyctrl","uom":25},"node":"2"}
2018-5-1 03:01:02 - info: HarmonyHub(2): Processing command: status
2018-5-1 03:01:02 - debug: MQTTP: nsCommand Message: {"status":{"value":1,"driver":"GV8","address":"harmonyctrl","uom":25},"node":"2"}
2018-5-1 03:01:02 - info: HarmonyHub(2): Processing command: status
2018-5-1 03:01:02 - debug: MQTTP: nsCommand Message: {"status":{"value":2,"driver":"GV9","address":"harmonyctrl","uom":25},"node":"2"}
2018-5-1 03:01:02 - info: HarmonyHub(2): Processing command: status
2018-5-1 03:01:02 - debug: ISY: 200 - http://192.168.86.64:80/rest/ns/2/nodes/n002_harmonyctrl/report/status/GV1/2.1/56
2018-5-1 03:01:02 - debug: ISY: 200 - http://192.168.86.64:80/rest/ns/2/nodes/n002_harmonyctrl/report/status/GV2/11/56
2018-5-1 03:01:02 - debug: ISY: 200 - http://192.168.86.64:80/rest/ns/2/nodes/n002_harmonyctrl/report/status/ST/0/2
2018-5-1 03:01:02 - info: HarmonyHub(2): n002_harmonyctrl GV1 set sucessfully to 2.1 : UOM 56
2018-5-1 03:01:02 - debug: ISY: 200 - http://192.168.86.64:80/rest/ns/2/nodes/n002_harmonyctrl/report/status/GV3/2/25
2018-5-1 03:01:02 - debug: ISY: 200 - http://192.168.86.64:80/rest/ns/2/nodes/n002_harmonyctrl/report/status/GV4//25
2018-5-1 03:01:02 - error: HarmonyHub(2): NS Status Error: TypeError: Cannot read property 'toString' of null
2018-5-1 03:01:02 - info: HarmonyHub(2): n002_harmonyctrl GV2 set sucessfully to 11 : UOM 56
2018-5-1 03:01:02 - info: HarmonyHub(2): n002_harmonyctrl ST set sucessfully to 0 : UOM 2
2018-5-1 03:01:02 - debug: MQTTP: nsCommand Message: {"status":{"value":1,"driver":"ST","address":"hc7023e62b09c2","uom":2},"node":"2"}
2018-5-1 03:01:02 - info: HarmonyHub(2): Processing command: status
111