Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

co-exist with PDA #4

Closed
ballle98 opened this issue Jan 14, 2019 · 1 comment
Closed

co-exist with PDA #4

ballle98 opened this issue Jan 14, 2019 · 1 comment

Comments

@ballle98
Copy link
Owner

need to periodically stop responding to status and go to sleep so that probes will start an another PDA has a chance to take control.

@ballle98
Copy link
Owner Author

When the browser connects:

Info: URI request: '/config.js '
Debug: Served WEB request
Debug: RS received packet of type Status length 12
Debug: ++ Websocket joined
Info: WS: Message - Key 'command' Value 'GET_DEVICES' | Key2 '(null)' Value2 '(null)'
Debug: WEB: homebridge used 1528 of 3000

...

when the browser is closed

Debug: -- Websocket left

ballle98 pushed a commit that referenced this issue Jan 31, 2019
Introducing last active timer.  This will release control 5 seconds
after thread terminates until 30 seconds have expired and it's time to
do another status update.
ballle98 pushed a commit that referenced this issue Mar 19, 2019
Introducing last active timer.  This will release control 5 seconds
after thread terminates until 30 seconds have expired and it's time to
do another status update.
ballle98 pushed a commit that referenced this issue May 18, 2019
Introducing last active timer.  This will release control 5 seconds
after thread terminates until 30 seconds have expired and it's time to
do another status update.
ballle98 pushed a commit that referenced this issue May 21, 2019
Introducing last active timer.  This will release control 5 seconds
after thread terminates until 30 seconds have expired and it's time to
do another status update.
ballle98 pushed a commit that referenced this issue Jun 14, 2019
Introducing last active timer.  This will release control 5 seconds
after thread terminates until 30 seconds have expired and it's time to
do another status update.
ballle98 pushed a commit that referenced this issue Jul 22, 2019
Introducing last active timer.  This will release control 5 seconds
after thread terminates until 30 seconds have expired and it's time to
do another status update.
ballle98 pushed a commit that referenced this issue Sep 6, 2019
Introducing last active timer.  This will release control 5 seconds
after thread terminates until 30 seconds have expired and it's time to
do another status update.
ballle98 pushed a commit that referenced this issue Sep 9, 2019
Introducing last active timer.  This will release control 5 seconds
after thread terminates until 30 seconds have expired and it's time to
do another status update.
ballle98 pushed a commit that referenced this issue Dec 4, 2019
Introducing last active timer.  This will release control 5 seconds
after thread terminates until 30 seconds have expired and it's time to
do another status update.
ballle98 pushed a commit that referenced this issue Dec 6, 2019
Introducing last active timer.  This will release control 5 seconds
after thread terminates until 30 seconds have expired and it's time to
do another status update.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant