Today I thought first I have a genious idea to see all messages from the controller (usually only visible in the app) by implementing the /messages API endpoint documented in the official API docs.
After a while I detected, that it might have been pretty useless, since not all needed and relevant information is contained in the Messages object. Esp. there is no obvious relation to a device...
here my forked branch including messages implementation
So if I'm wrong and my implementation is helpful, I'll create a pull request after a bit more testing.
Open topics:
test with polling / slow polling
I saw, that in the session.py the _process_long_polling_poll_result method also reacts on type message. Did not crosscheck if this clashes with my implementation
Just close it, if it is not worth of further following up.
Today I thought first I have a genious idea to see all messages from the controller (usually only visible in the app) by implementing the /messages API endpoint documented in the official API docs.
After a while I detected, that it might have been pretty useless, since not all needed and relevant information is contained in the Messages object. Esp. there is no obvious relation to a device... here my forked branch including messages implementation
So if I'm wrong and my implementation is helpful, I'll create a pull request after a bit more testing.
Open topics:
Just close it, if it is not worth of further following up.