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

Error: Communicating via an not-yet-implemented protocol #24

Closed
carp3-noctem opened this issue Mar 3, 2024 · 4 comments
Closed

Error: Communicating via an not-yet-implemented protocol #24

carp3-noctem opened this issue Mar 3, 2024 · 4 comments

Comments

@carp3-noctem
Copy link

Hi,

when try to setup the local Integration I get the following message, so I go ahead and create the issue ;-)
image

In the Logfiles the following lines where found:
2024-03-03 17:18:54.203 INFO (MainThread) [custom_components.tibber_local] restarting TibberLocalBridge integration... for host: '192.168.0.44' node: '1' com_mode: '3' with options: None 2024-03-03 17:18:54.391 WARNING (MainThread) [custom_components.tibber_local] access to bridge failed with exception: 404, message='Not Found', url=URL('http://192.168.0.44/node_params.json?node_id=1') 2024-03-03 17:18:54.391 DEBUG (MainThread) [custom_components.tibber_local] detect_com_mode: after detect_com_mode_from_node_param27 mode is: -1 2024-03-03 17:18:54.391 DEBUG (MainThread) [custom_components.tibber_local] detect_com_mode is -1: will try to read 99 2024-03-03 17:18:54.426 WARNING (MainThread) [custom_components.tibber_local] access to bridge failed with exception: 404, message='Not Found', url=URL('http://192.168.0.44/data.json?node_id=1') 2024-03-03 17:18:54.426 DEBUG (MainThread) [custom_components.tibber_local] detect_com_mode 1 is -1: 99 failed - will try to read 3 2024-03-03 17:18:54.463 WARNING (MainThread) [custom_components.tibber_local] access to bridge failed with exception: 404, message='Not Found', url=URL('http://192.168.0.44/data.json?node_id=1') 2024-03-03 17:18:54.463 DEBUG (MainThread) [custom_components.tibber_local] detect_com_mode 2 is -1: 99 failed and 3 failed 2024-03-03 17:18:54.463 ERROR (MainThread) [custom_components.tibber_local.config_flow] Could not connect to Tibber Pulse Bridge at 192.168.0.44, check host ip address 2024-03-03 17:22:11.565 INFO (MainThread) [custom_components.tibber_local] restarting TibberLocalBridge integration... for host: '192.168.0.44' node: '1' com_mode: '3' with options: None 2024-03-03 17:22:11.676 WARNING (MainThread) [custom_components.tibber_local] access to bridge failed with exception: 404, message='Not Found', url=URL('http://192.168.0.44/node_params.json?node_id=1') 2024-03-03 17:22:11.676 DEBUG (MainThread) [custom_components.tibber_local] detect_com_mode: after detect_com_mode_from_node_param27 mode is: -1 2024-03-03 17:22:11.676 DEBUG (MainThread) [custom_components.tibber_local] detect_com_mode is -1: will try to read 99 2024-03-03 17:22:11.730 WARNING (MainThread) [custom_components.tibber_local] access to bridge failed with exception: 404, message='Not Found', url=URL('http://192.168.0.44/data.json?node_id=1') 2024-03-03 17:22:11.731 DEBUG (MainThread) [custom_components.tibber_local] detect_com_mode 1 is -1: 99 failed - will try to read 3 2024-03-03 17:22:11.774 WARNING (MainThread) [custom_components.tibber_local] access to bridge failed with exception: 404, message='Not Found', url=URL('http://192.168.0.44/data.json?node_id=1') 2024-03-03 17:22:11.774 DEBUG (MainThread) [custom_components.tibber_local] detect_com_mode 2 is -1: 99 failed and 3 failed 2024-03-03 17:22:11.774 ERROR (MainThread) [custom_components.tibber_local.config_flow] Could not connect to Tibber Pulse Bridge at 192.168.0.44, check host ip address 2024-03-03 17:22:14.498 INFO (MainThread) [custom_components.tibber_local] restarting TibberLocalBridge integration... for host: '192.168.0.44' node: '1' com_mode: '3' with options: None 2024-03-03 17:22:14.651 WARNING (MainThread) [custom_components.tibber_local] access to bridge failed with exception: 404, message='Not Found', url=URL('http://192.168.0.44/node_params.json?node_id=1') 2024-03-03 17:22:14.652 DEBUG (MainThread) [custom_components.tibber_local] detect_com_mode: after detect_com_mode_from_node_param27 mode is: -1 2024-03-03 17:22:14.652 DEBUG (MainThread) [custom_components.tibber_local] detect_com_mode is -1: will try to read 99 2024-03-03 17:22:14.693 WARNING (MainThread) [custom_components.tibber_local] access to bridge failed with exception: 404, message='Not Found', url=URL('http://192.168.0.44/data.json?node_id=1') 2024-03-03 17:22:14.693 DEBUG (MainThread) [custom_components.tibber_local] detect_com_mode 1 is -1: 99 failed - will try to read 3 2024-03-03 17:22:14.725 WARNING (MainThread) [custom_components.tibber_local] access to bridge failed with exception: 404, message='Not Found', url=URL('http://192.168.0.44/data.json?node_id=1') 2024-03-03 17:22:14.726 DEBUG (MainThread) [custom_components.tibber_local] detect_com_mode 2 is -1: 99 failed and 3 failed 2024-03-03 17:22:14.726 ERROR (MainThread) [custom_components.tibber_local.config_flow] Could not connect to Tibber Pulse Bridge at 192.168.0.44, check host ip address

But the Device is reachable when surfing to it's IP:
Bildschirmfoto

@carp3-noctem
Copy link
Author

I did found that my Bridge don't use /node/1/data, it uses /node/2/data and has the following Output:
image

@marq24
Copy link
Owner

marq24 commented Mar 3, 2024

When it's node 2, then simply make use of the "expert-setting" in the Integration setup dialog and enter your node 2 (replace the default node 1)

@carp3-noctem
Copy link
Author

Stupid me, overseen this option. But also found that a few minutes later then original :-D

Thanks for the great Work, Issue closed as it is working with node 2 setting

@marq24
Copy link
Owner

marq24 commented Mar 3, 2024

I just enhanced the error message (to avoid such a situation in the future) thanks for mention this issue!

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

2 participants