I've fixed WS connection process to connect right after websocket is connected not after welcome message is received. Tested it with my RPI and it works fine, should be more reliable then before.
Another enhancement requested by @ba58smith was sending watch status in separate SK paths, this PR does it. INew paths are:
{watchname}.battery = 53
{watchname}.temperature = 288
{watchname}.uptime = "19:43:45" (data are from my watch on my desk)
I've fixed WS connection process to connect right after websocket is connected not after welcome message is received. Tested it with my RPI and it works fine, should be more reliable then before.
Another enhancement requested by @ba58smith was sending watch status in separate SK paths, this PR does it. INew paths are: {watchname}.battery = 53 {watchname}.temperature = 288 {watchname}.uptime = "19:43:45" (data are from my watch on my desk)
Thanks