Davee Nguyen

I think the Worker thread is getting killed. When the sensors stop responding, `ws._Dongle__thread.is_alive()` was returning `False`. I don't know the reason the thread is dead. Don't see anything in...

@RonSpawnson I think you are right about non-OSError Errrors causing the thread to die. Been running similar changes for a few days now. I noticed the thread haven't been killed...

logging.exception does log some trace info. https://docs.python.org/3/library/logging.html#logging.exception @gterpstra75 do you see more lines after the error message without date and time? The only errors I've encountered in the past 4...

@RonSpawnson I think it's not a red herring because the bare except is catching all Errors that would've been raised before. Uncaught errors are now "handled" in this loop. To...

https://github.com/daveenguyen/ha-wyzesense/blob/bugfix/dead-thread/custom_components/wyzesense/wyzesense_custom.py#L381 Updated my branch to `raise` in the bare except. Thread dies. My sensor and restart automation kicks in. After the non-OSError/restart service, it is `(Thread-15)` and not `(Thread-2)` The...

I think people can use #129 as a simple workaround for now and share non-OSError they encounter

@gterpstra75 If you're using a change with `log.exception`, you should be able to see it in `/developer-tools/logs` when you click on the wyzesense error to view more details. 

Looks like the same issue as pyatom/pyatom#156 Security Agent elements are not visible until the title bar is clicked. I'll get `selenium.common.exceptions.NoSuchElementException: Message: An element could not be located on...

I don't have a mac machine to try out, but I think you can call `activate()` on the app reference which should bring the app to the front.

`pyautogui` is there because atomac provided methods to send native keyboard/mouse inputs. I wanted this project to be a sort of drop-in replacement for atomac. However, I also didn't want...