Orbit Hose Timer - crazy log data


#1

Hey there, Just a quick Q -

I have an Iris Orbit Hose timer (scored off of Ebay and seems to work).

But I am noticing if I turn on debug logging its spitting out a metric ton of log data... makes me think this thing is going to burn its batteries out in days...

[dev:289](http://192.168.50.16/logs/past#dev289)2019-05-13 08:11:55.854 am [debug](http://192.168.50.16/device/edit/289)Parse: read attr - raw: FA320102010800013002, dni: FA32, endpoint: 01, cluster: 0201, size: 08, attrId: 0100, encoding: 30, command: 0A, value: 02

[dev:289](http://192.168.50.16/logs/past#dev289)2019-05-13 08:11:42.836 am [debug](http://192.168.50.16/device/edit/289)Parse: catchall: 0104 0020 01 01 0040 00 FA32 01 00 0000 00 01

[dev:289](http://192.168.50.16/logs/past#dev289)2019-05-13 08:11:06.836 am [debug](http://192.168.50.16/device/edit/289)Parse: read attr - raw: FA320102011C2300300024002100000201210000, dni: FA32, endpoint: 01, cluster: 0201, size: 1C, attrId: 0023, encoding: 30, command: 0A, value: 0024002100000201210000

[dev:289](http://192.168.50.16/logs/past#dev289)2019-05-13 08:10:48.834 am [debug](http://192.168.50.16/device/edit/289)Parse: read attr - raw: FA320102010800013002, dni: FA32, endpoint: 01, cluster: 0201, size: 08, attrId: 0100, encoding: 30, command: 0A, value: 02

[dev:289](http://192.168.50.16/logs/past#dev289)2019-05-13 08:10:00.862 am [debug](http://192.168.50.16/device/edit/289)Parse: read attr - raw: FA320102011C2300300024002100000201210000, dni: FA32, endpoint: 01, cluster: 0201, size: 1C, attrId: 0023, encoding: 30, command: 0A, value: 0024002100000201210000

[dev:289](http://192.168.50.16/logs/past#dev289)2019-05-13 08:09:42.081 am [debug](http://192.168.50.16/device/edit/289)Parse: read attr - raw: FA320102010800013002, dni: FA32, endpoint: 01, cluster: 0201, size: 08, attrId: 0100, encoding: 30, command: 0A, value: 02

[dev:289](http://192.168.50.16/logs/past#dev289)2019-05-13 08:09:41.842 am [debug](http://192.168.50.16/device/edit/289)Parse: catchall: 0104 0020 01 01 0040 00 FA32 01 00 0000 00 01

[dev:289](http://192.168.50.16/logs/past#dev289)2019-05-13 08:08:53.844 am [debug](http://192.168.50.16/device/edit/289)Parse: read attr - raw: FA320102011C2300300024002100000201210000, dni: FA32, endpoint: 01, cluster: 0201, size: 1C, attrId: 0023, encoding: 30, command: 0A, value: 0024002100000201210000

[dev:289](http://192.168.50.16/logs/past#dev289)2019-05-13 08:08:35.855 am [debug](http://192.168.50.16/device/edit/289)Parse: read attr - raw: FA320102010800013002, dni: FA32, endpoint: 01, cluster: 0201, size: 08, attrId: 0100, encoding: 30, command: 0A, value: 02

[dev:289](http://192.168.50.16/logs/past#dev289)2019-05-13 08:07:47.866 am [debug](http://192.168.50.16/device/edit/289)Parse: read attr - raw: FA320102011C2300300024002100000201210000, dni: FA32, endpoint: 01, cluster: 0201, size: 1C, attrId: 0023, encoding: 30, command: 0A, value: 0024002100000201210000

[dev:289](http://192.168.50.16/logs/past#dev289)2019-05-13 08:07:40.832 am [debug](http://192.168.50.16/device/edit/289)Parse: catchall: 0104 0020 01 01 0040 00 FA32 01 00 0000 00 01

[dev:289](http://192.168.50.16/logs/past#dev289)2019-05-13 08:07:28.872 am [debug](http://192.168.50.16/device/edit/289)Parse: read attr - raw: FA320102010800013002, dni: FA32, endpoint: 01, cluster: 0201, size: 08, attrId: 0100, encoding: 30, command: 0A, value: 02

[dev:289](http://192.168.50.16/logs/past#dev289)2019-05-13 08:06:40.849 am [debug](http://192.168.50.16/device/edit/289)Parse: read attr - raw: FA320102011C2300300024002100000201210000, dni: FA32, endpoint: 01, cluster: 0201, size: 1C, attrId: 0023, encoding: 30, command: 0A, value: 0024002100000201210000

[dev:289](http://192.168.50.16/logs/past#dev289)2019-05-13 08:06:22.847 am [debug](http://192.168.50.16/device/edit/289)Parse: read attr - raw: FA320102010800013002, dni: FA32, endpoint: 01, cluster: 0201, size: 08, attrId: 0100, encoding: 30, command: 0A, value: 02

[dev:289](http://192.168.50.16/logs/past#dev289)2019-05-13 08:05:39.841 am [debug](http://192.168.50.16/device/edit/289)Parse: catchall: 0104 0020 01 01 0040 00 FA32 01 00 0000 00 01

[dev:289](http://192.168.50.16/logs/past#dev289)2019-05-13 08:05:33.847 am [debug](http://192.168.50.16/device/edit/289)Parse: read attr - raw: FA320102011C2300300024002100000201210000, dni: FA32, endpoint: 01, cluster: 0201, size: 1C, attrId: 0023, encoding: 30, command: 0A, value: 0024002100000201210000

[dev:289](http://192.168.50.16/logs/past#dev289)2019-05-13 08:05:15.842 am [debug](http://192.168.50.16/device/edit/289)Parse: read attr - raw: FA320102010800013002, dni: FA32, endpoint: 01, cluster: 0201, size: 08, attrId: 0100, encoding: 30, command: 0A, value: 02

[dev:289](http://192.168.50.16/logs/past#dev289)2019-05-13 08:04:27.839 am [debug](http://192.168.50.16/device/edit/289)Parse: read attr - raw: FA320102011C2300300024002100000201210000, dni: FA32, endpoint: 01, cluster: 0201, size: 1C, attrId: 0023, encoding: 30, command: 0A, value: 0024002100000201210000

[dev:289](http://192.168.50.16/logs/past#dev289)2019-05-13 08:04:09.843 am [debug](http://192.168.50.16/device/edit/289)Parse: read attr - raw: FA320102010800013002, dni: FA32, endpoint: 01, cluster: 0201, size: 08, attrId: 0100, encoding: 30, command: 0A, value: 02

[dev:289](http://192.168.50.16/logs/past#dev289)2019-05-13 08:03:38.833 am [debug](http://192.168.50.16/device/edit/289)Parse: catchall: 0104 0020 01 01 0040 00 FA32 01 00 0000 00 01

Anyone have insight into WTF is going on with this thing and why it would be so chatty to the Hub? I also wanted to keep Debug logging on so I can track valve open/close But at this point I cant leave debug on or it will flood the logs.


#2

I would leave debug logging off and check to see if descriptionText is available from the settings page.

You could also create a simple notification rule in RM to alert you when the valve opens and closes as well.