Doesn't reconnect to MQTT if loses connection

[mcolyer]

No description provided.

[adamf663]

I am seeing something similar. voltlet only seems able to keep working for about 20-40 hours until it quits working. restarting it always cures it.
Some typical log messages before and after a failure are:
13:59:41.073Z [56a07964-6a22-43d2-a950-687dbf09e296] ping
13:59:41.274Z [56a07964-6a22-43d2-a950-687dbf09e296] recv: map[uri:/kr]
13:59:43.176Z [4c721ebd-c328-4285-8dd6-f73ddcce5fab] ping
13:59:43.276Z [4c721ebd-c328-4285-8dd6-f73ddcce5fab] recv: map[uri:/kr]
13:59:46.08Z [56a07964-6a22-43d2-a950-687dbf09e296] ping
13:59:48.184Z [4c721ebd-c328-4285-8dd6-f73ddcce5fab] ping
13:59:51.088Z [56a07964-6a22-43d2-a950-687dbf09e296] ping
13:59:53.191Z [4c721ebd-c328-4285-8dd6-f73ddcce5fab] ping
13:59:56.096Z [56a07964-6a22-43d2-a950-687dbf09e296] ping
13:59:58.2Z [4c721ebd-c328-4285-8dd6-f73ddcce5fab] ping
14:00:01.105Z [56a07964-6a22-43d2-a950-687dbf09e296] ping
14:00:01.274Z read error: read tcp 192.168.5.43:17273->192.168.5.142:28780: i/o timeout
14:00:01.305Z [56a07964-6a22-43d2-a950-687dbf09e296] offline
14:00:01.406Z Unsubscribing to mqtt topic: /voltson/56a07964-6a22-43d2-a950-687dbf09e296
14:00:01.407Z Unsubscribed to mqtt topic: /voltson/56a07964-6a22-43d2-a950-687dbf09e296
14:00:03.21Z [4c721ebd-c328-4285-8dd6-f73ddcce5fab] ping
14:00:03.277Z read error: read tcp 192.168.5.43:17273->192.168.5.42:21153: i/o timeout
14:00:03.311Z [4c721ebd-c328-4285-8dd6-f73ddcce5fab] offline
14:00:03.511Z Unsubscribing to mqtt topic: /voltson/4c721ebd-c328-4285-8dd6-f73ddcce5fab
14:00:03.512Z Unsubscribed to mqtt topic: /voltson/4c721ebd-c328-4285-8dd6-f73ddcce5fab
14:08:52.319Z Client connected
14:08:52.42Z [] recv: map[deviceVersionCode:%!s(float64=5) type:wifi-switch firmName:cosytek_firm_a firmVersion:1.89 firmVersionCode:%!s(float64=89) account$
14:08:52.478Z Subscribing to mqtt topic: /voltson/56a07964-6a22-43d2-a950-687dbf09e296
14:08:52.479Z Subscribed to mqtt topic: /voltson/56a07964-6a22-43d2-a950-687dbf09e296
14:08:52.479Z [56a07964-6a22-43d2-a950-687dbf09e296] send: {"uri":"/loginReply","error":0,"wd":3,"year":2018,"month":9,"day":20,"ms":479,"hh":0,"hl":0,"lh":$
14:08:52.579Z [56a07964-6a22-43d2-a950-687dbf09e296] command: false
14:08:52.579Z [56a07964-6a22-43d2-a950-687dbf09e296] send: {"uri":"/relay","action":"break"}
14:08:52.779Z [56a07964-6a22-43d2-a950-687dbf09e296] recv: map[relay:break meastate:idle power:0:0 voltage:0:0 current:NaN uri:/runtimeInfo]
14:08:57.386Z [56a07964-6a22-43d2-a950-687dbf09e296] ping
14:08:57.487Z [56a07964-6a22-43d2-a950-687dbf09e296] recv: map[uri:/kr]
14:09:02.395Z [56a07964-6a22-43d2-a950-687dbf09e296] ping
14:09:02.495Z [56a07964-6a22-43d2-a950-687dbf09e296] recv: map[uri:/kr]
14:09:07.402Z [56a07964-6a22-43d2-a950-687dbf09e296] ping
14:09:07.503Z [56a07964-6a22-43d2-a950-687dbf09e296] recv: map[uri:/kr]

[mcolyer]

I am seeing something similar. voltlet only seems able to keep working for about 20-40 hours until it quits working. restarting it always cures it.

It's possible that this is caused by this if it loses the connection to your MQTT daemon. Unfortunately I won't have time to fix this for the forseeable future.

[adamf663]

that's cool. An easy workaround is to restart it periodically.

…

----- Original Message -----

From: "Matt Colyer" ***@***.***> To: "mcolyer/voltlet" ***@***.***> Cc: "adamf663" ***@***.***>, "Comment" ***@***.***> Sent: Sunday, September 23, 2018 10:17:51 AM Subject: Re: [mcolyer/voltlet] Doesn't reconnect to MQTT if loses connection (#2) > I am seeing something similar. voltlet only seems able to keep working for about > 20-40 hours until it quits working. restarting it always cures it. It's possible that this is caused by this if it loses the connection to your MQTT daemon. Unfortunately I won't have time to fix this for the forseeable future. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #2 (comment)