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

Fronted auth_token #112

Closed
david883 opened this issue Jan 11, 2023 · 8 comments · Fixed by #117
Closed

Fronted auth_token #112

david883 opened this issue Jan 11, 2023 · 8 comments · Fixed by #117
Labels
enhancement New feature or request ready for testing The specified development branch can be tested

Comments

@david883
Copy link

What happened?

Sobald ein Auth Token im Frontend von ZigBee2Mqtt genutzt wird, kann der Adapter sich nicht mehr verbinden.

What did you expect to happen?

Auth Token in der configuration.yaml eingefügt. ZigBee2mqtt neu gestartet.

How to reproduce it (minimal and precise)

Auth Token in der configuration.yaml einfügen und Zigbee2mqtt neu starten.

Adapter version

2.6.0

Log

Websocket disconnected!

@david883 david883 added the problem Something isn't working label Jan 11, 2023
@o0shojo0o o0shojo0o added enhancement New feature or request and removed problem Something isn't working labels Jan 11, 2023
o0shojo0o added a commit that referenced this issue Jan 11, 2023
@o0shojo0o
Copy link
Contributor

@david883
Copy link
Author

Hi, danke für die schnelle Umsetzung. Ich kann es erst am Wochenende testen und sage dir dann bescheid. Mfg David

@o0shojo0o o0shojo0o added the ready for testing The specified development branch can be tested label Jan 12, 2023
@david883
Copy link
Author

Habe nun doch Zeit gefunden und den Dev Branch installiert. Auth Token im Adapter und auf dem zigbee2mqtt Server eingegeben und neu gestartet. Leider keine Verbindung möglich:

Log:
`zigbee2mqtt.0
2023-01-12 15:38:03.877 warn Start try again in 1 seconds...

zigbee2mqtt.0
2023-01-12 15:38:03.875 info Connect to Zigbee2MQTT over websocket connection.

zigbee2mqtt.0
2023-01-12 15:38:02.872 warn Start try again in 1 seconds...

zigbee2mqtt.0
2023-01-12 15:38:02.870 info Connect to Zigbee2MQTT over websocket connection.

zigbee2mqtt.0
2023-01-12 15:38:01.868 warn Start try again in 1 seconds...

zigbee2mqtt.0
2023-01-12 15:38:01.866 info Connect to Zigbee2MQTT over websocket connection.

zigbee2mqtt.0
2023-01-12 15:38:00.865 warn Start try again in 1 seconds...

zigbee2mqtt.0
2023-01-12 15:38:00.861 info Connect to Zigbee2MQTT over websocket connection.

zigbee2mqtt.0
2023-01-12 15:37:59.859 warn Start try again in 1 seconds...

zigbee2mqtt.0
2023-01-12 15:37:59.856 info Connect to Zigbee2MQTT over websocket connection.

zigbee2mqtt.0
2023-01-12 15:37:58.853 warn Start try again in 1 seconds...

zigbee2mqtt.0
2023-01-12 15:37:58.851 info Connect to Zigbee2MQTT over websocket connection.

zigbee2mqtt.0
2023-01-12 15:37:57.850 warn Start try again in 1 seconds...

zigbee2mqtt.0
2023-01-12 15:37:57.847 info Connect to Zigbee2MQTT over websocket connection.

zigbee2mqtt.0
2023-01-12 15:37:56.845 warn Start try again in 1 seconds...

zigbee2mqtt.0
2023-01-12 15:37:56.840 info Connect to Zigbee2MQTT over websocket connection.

zigbee2mqtt.0
2023-01-12 15:37:56.790 info ==================================================================================

zigbee2mqtt.0
2023-01-12 15:37:56.790 info || Use Kelvin: no

zigbee2mqtt.0
2023-01-12 15:37:56.790 info || Proxy Zigbee2MQTT Logs to ioBroker Logs: activated

zigbee2mqtt.0
2023-01-12 15:37:56.790 info || Zigbee2MQTT Debug Log: deactivated

zigbee2mqtt.0
2023-01-12 15:37:56.790 info || Zigbee2MQTT Websocket Dummy MQTT-Server: deactivated

zigbee2mqtt.0
2023-01-12 15:37:56.790 info || Zigbee2MQTT Websocket Auth-Token: use

zigbee2mqtt.0
2023-01-12 15:37:56.789 info || Zigbee2MQTT Websocket Port: 8080

zigbee2mqtt.0
2023-01-12 15:37:56.789 info || Zigbee2MQTT Websocket Server: 192.168.178.11

zigbee2mqtt.0
2023-01-12 15:37:56.789 info || Zigbee2MQTT Connection Type: ws

zigbee2mqtt.0
2023-01-12 15:37:56.789 info || Zigbee2MQTT Frontend Port: 8081

zigbee2mqtt.0
2023-01-12 15:37:56.789 info || Zigbee2MQTT Frontend Server: 192.168.178.11

zigbee2mqtt.0
2023-01-12 15:37:56.788 info || Zigbee2MQTT Frontend Scheme: https

zigbee2mqtt.0
2023-01-12 15:37:56.788 info ================================= Adapter Config =================================

zigbee2mqtt.0
2023-01-12 15:37:56.773 info starting. Version 2.6.0 (non-npm: #112-fronted-auth_token) in /opt/iobroker/node_modules/iobroker.zigbee2mqtt, node: v16.19.0, js-controller: 4.0.24

zigbee2mqtt.0
2023-01-12 15:37:52.083 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

zigbee2mqtt.0
2023-01-12 15:37:52.082 info terminating`

@o0shojo0o
Copy link
Contributor

o0shojo0o commented Jan 12, 2023

Hi, ich habe es eben auch auf meinen Live-System getestet und es läuft.
Kein Tippfehler oder Leerzeichen mit kopiert?

@david883
Copy link
Author

Ich habe es nun auch geschafft. Das Problem waren die Sonderzeichen.
Hatte ein # im Token eingebaut....

Läuft jetzt einwandfrei! Hoffe es kommt mit in die nächste Version ;-)

Danke

@o0shojo0o
Copy link
Contributor

Ich habe noch mal was geändert magst du das noch mal bei dir mit Sonderzeichen versuchen?

@david883
Copy link
Author

david883 commented Jan 12, 2023

Ich habe den Branch nochmals installiert. Passwort im Adapter und Zigbee2mqtt Server geändert. Neustart.

Leider funktioniert es nicht. Keine Verbindung. Dannach wieder Sonderzeichen entfernt und es läuft

@o0shojo0o
Copy link
Contributor

hmmm... schade
ich teste mal weiter

o0shojo0o added a commit that referenced this issue Jan 18, 2023
-   (o0shojo0o) added support for  wildcard actions (eg. *_single) ([#116](#116))
-   (o0shojo0o) added error handling optimizations ([more](ioBroker/ioBroker.repositories#1976 (comment)))
-   (o0shojo0o) added option `auth_token` for websocket connection ([#112](#112))
-   (o0shojo0o) websocket timeout increased
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request ready for testing The specified development branch can be tested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants