Getting DID NOT PARSE MESSAGE errors

🛎️ Get Help
1

I'm running a C7 hub. I have a Webcore piston that turns on two exterior porch lights at sunset and turns them off at sunrise. This morning the lights were still on after sunrise even though the piston ran. As is my routine when things start to get janky, I shut down the hub, pulled the power, waited 30 minutes and powered it back up. Unfortunately, when I came home tonight, the lights weren't on even though if was after sunset and the piston ran as expected. When I look at the log, I see the info messages posted below. As a note, I haven't touched the piston or taken hub updates in over a year, meaning nothing has changed.

Here's what's in the log for one of the bulbs. The other bulb shows the same thing. Do these info messages suggest the cause of the problem? If so, is there something I can do to fix things? TIA.

dev:1612023-12-04 05:33:52.971 pm infoDID NOT PARSE MESSAGE for description : catchall: 0104 0008 01 01 0040 00 0377 00 00 0000 0B 01 0400

dev:1612023-12-04 05:30:26.795 pm infoDID NOT PARSE MESSAGE for description : catchall: 0104 0008 01 01 0040 00 0377 00 00 0000 0B 01 0400

dev:1612023-12-04 05:25:31.158 pm infoDID NOT PARSE MESSAGE for description : catchall: 0104 0008 01 01 0040 00 0377 00 00 0000 0B 01 0400

dev:1612023-12-04 05:25:29.727 pm infoDID NOT PARSE MESSAGE for description : catchall: 0104 0008 01 01 0040 00 0377 00 00 0000 0B 01 0400

dev:1612023-12-04 05:25:28.205 pm infoDID NOT PARSE MESSAGE for description : catchall: 0104 0008 01 01 0040 00 0377 00 00 0000 0B 01 0400

dev:1612023-12-04 04:56:54.445 pm infoDID NOT PARSE MESSAGE for description : catchall: 0104 0008 01 01 0040 00 0377 00 00 0000 0B 01 0400

dev:1612023-12-04 04:48:41.389 pm infoDID NOT PARSE MESSAGE for description : catchall: 0104 0008 01 01 0040 00 0377 00 00 0000 0B 01 0400

dev:1612023-12-04 04:48:32.859 pm infoDID NOT PARSE MESSAGE for description : catchall: 0104 0300 01 01 0040 00 0377 00 00 0000 07 01 00

dev:1612023-12-04 04:48:30.881 pm infoDID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0040 00 0377 00 00 0000 00 00 8300

dev:1612023-12-04 04:48:28.867 pm infoDID NOT PARSE MESSAGE for description : catchall: 0104 0300 01 01 0040 00 0377 00 00 0000 07 01 00

dev:1612023-12-04 04:48:26.855 pm infoDID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0040 00 0377 00 00 0000 00 00 7F00

dev:1612023-12-04 04:48:24.854 pm infoDID NOT PARSE MESSAGE for description : catchall: 0104 0008 01 01 0040 00 0377 00 00 0000 07 01 00

dev:1612023-12-04 04:48:22.824 pm infoDID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0040 00 0377 00 00 0000 00 00 7B00

dev:1612023-12-04 04:48:18.821 pm infoDID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0040 00 0377 00 00 0000 00 00 7700

dev:1612023-12-04 04:47:46.200 pm infoDID NOT PARSE MESSAGE for description : catchall: 0104 0008 01 01 0040 00 0377 00 00 0000 0B 01 0400

dev:1612023-12-04 08:36:47.185 am infoDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 0377 00 00 0000 00 00 00000A0109000003000000000300000000030000000003000000000300000000030000000003000000000300000000030000

dev:1612023-12-04 08:36:46.323 am infoDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 0377 00 00 0000 00 00 00000A0109000003000000000300000000030000000003000000000300000000030000000003000000000300000000030000

dev:1612023-12-04 07:23:58.684 am infoDID NOT PARSE MESSAGE for description : catchall: 0000 0013 00 00 0040 00 0377 00 00 0000 00 00 9977036B2E2CFEFF5ECFD08E

dev:1612023-12-04 07:18:26.815 am infoDID NOT PARSE MESSAGE for description : catchall: 0104 0300 01 01 0040 00 0377 00 00 0000 07 01 00

dev:1612023-12-04 07:18:24.810 am infoDID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0040 00 0377 00 00 0000 00 00 AE00

dev:1612023-12-04 07:18:22.810 am infoDID NOT PARSE MESSAGE for description : catchall: 0104 0300 01 01 0040 00 0377 00 00 0000 07 01 00

dev:1612023-12-04 07:18:20.797 am infoDID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0040 00 0377 00 00 0000 00 00 AA00

dev:1612023-12-04 07:18:18.807 am infoDID NOT PARSE MESSAGE for description : catchall: 0104 0008 01 01 0040 00 0377 00 00 0000 07 01 00

dev:1612023-12-04 07:18:16.791 am infoDID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0040 00 0377 00 00 0000 00 00 A600

dev:1612023-12-04 07:18:12.795 am infoDID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0040 00 0377 00 00 0000 00 00 A200

2

What is the actual device here (brand and model), and what driver ("Type" on the device detail page) is it using? This looks like a lot more like logs you'd see from a community driver than anything built-in, so the behavior you see may be a better question for the driver author. But often this kind of thing is not a problem, just an FYI you can use if debugging something the driver might need to be parsing into an event but isn't (but, again, you'd need to see for sure). It's unlikely to be the cause of not responding to a command. However, knowing more about your particular situation may help shed more light on possible problems.

2 Likes
3

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.