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.

Sign up for GitHub

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

Jump to bottom

Problem mit zigbee2mqtt server nutzt https #191

Closed
ticaki opened this issue Jul 1, 2023 · 6 comments · Fixed by #204
Closed

Problem mit zigbee2mqtt server nutzt https #191

ticaki opened this issue Jul 1, 2023 · 6 comments · Fixed by #204
Labels
problem Something isn't working

Comments

@ticaki
Copy link

ticaki commented Jul 1, 2023 •
edited
Loading

What happened?

Ich habe den zigbee2mqtt-Server auf https:// mit Zertifikaten umgestellt. Und danach bekam ich unten gezeigten Zustand

What did you expect to happen?

Das dieser Adapter sich über https anmelden kann

How to reproduce it (minimal and precise)

Siehe oben umstellen auf https

Adapter version

2.7.5

Log

2023-07-01 03:18:42.752 - info: zigbee2mqtt.0 (26371) starting. Version 2.7.5 in /opt/iobroker/node_modules/iobroker.zigbee2mqtt, node: v18.16.1, js-controller: 5.0.5

2023-07-01 03:18:42.806 - info: zigbee2mqtt.0 (26371) ================================= Adapter Config =================================
2023-07-01 03:18:42.807 - info: zigbee2mqtt.0 (26371) || Zigbee2MQTT Frontend Scheme: https
2023-07-01 03:18:42.808 - info: zigbee2mqtt.0 (26371) || Zigbee2MQTT Frontend Server: 192.168.178.96
2023-07-01 03:18:42.809 - info: zigbee2mqtt.0 (26371) || Zigbee2MQTT Frontend Port: 8089
2023-07-01 03:18:42.810 - info: zigbee2mqtt.0 (26371) || Zigbee2MQTT Connection Type: ws
2023-07-01 03:18:42.811 - info: zigbee2mqtt.0 (26371) || Zigbee2MQTT Websocket Server: 192.168.178.96
2023-07-01 03:18:42.811 - info: zigbee2mqtt.0 (26371) || Zigbee2MQTT Websocket Port: 8089
2023-07-01 03:18:42.812 - info: zigbee2mqtt.0 (26371) || Zigbee2MQTT Websocket Auth-Token: unused
2023-07-01 03:18:42.812 - info: zigbee2mqtt.0 (26371) || Zigbee2MQTT Websocket Dummy MQTT-Server: deactivated
2023-07-01 03:18:42.812 - info: zigbee2mqtt.0 (26371) || Zigbee2MQTT Debug Log: deactivated
2023-07-01 03:18:42.813 - info: zigbee2mqtt.0 (26371) || Proxy Zigbee2MQTT Logs to ioBroker Logs: activated
2023-07-01 03:18:42.813 - info: zigbee2mqtt.0 (26371) || Use Kelvin: yes
2023-07-01 03:18:42.814 - info: zigbee2mqtt.0 (26371) ==================================================================================
2023-07-01 03:18:42.843 - silly: zigbee2mqtt.0 (26371) States system redis pmessage io.system.adapter.zigbee2mqtt.0.logLevel/io.system.adapter.zigbee2mqtt.0.logLevel:{"val":"silly","ack":true,"ts":1688174322817,"q":0,"from":"system.adapter.zigbee2mqtt.0","lc":1688173851915}
2023-07-01 03:18:42.870 - debug: zigbee2mqtt.0 (26371) Error: socket hang up
2023-07-01 03:18:42.871 - warn: zigbee2mqtt.0 (26371) Start try again in 1 seconds...
2023-07-01 03:18:42.880 - debug: zigbee2mqtt.0 (26371) Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
2023-07-01 03:18:43.877 - debug: zigbee2mqtt.0 (26371) Error: socket hang up
2023-07-01 03:18:43.878 - warn: zigbee2mqtt.0 (26371) Start try again in 1 seconds...
2023-07-01 03:18:43.883 - debug: zigbee2mqtt.0 (26371) Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
2023-07-01 03:18:44.884 - debug: zigbee2mqtt.0 (26371) Error: socket hang up
2023-07-01 03:18:44.885 - warn: zigbee2mqtt.0 (26371) Start try again in 1 seconds...
2023-07-01 03:18:44.892 - debug: zigbee2mqtt.0 (26371) Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
2023-07-01 03:18:45.889 - debug: zigbee2mqtt.0 (26371) Error: socket hang up
2023-07-01 03:18:45.890 - warn: zigbee2mqtt.0 (26371) Start try again in 1 seconds...
2023-07-01 03:18:45.893 - debug: zigbee2mqtt.0 (26371) Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
2023-07-01 03:18:46.896 - debug: zigbee2mqtt.0 (26371) Error: socket hang up
2023-07-01 03:18:46.896 - warn: zigbee2mqtt.0 (26371) Start try again in 1 seconds...
2023-07-01 03:18:46.900 - debug: zigbee2mqtt.0 (26371) Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
2023-07-01 03:18:47.903 - debug: zigbee2mqtt.0 (26371) Error: socket hang up
2023-07-01 03:18:47.903 - warn: zigbee2mqtt.0 (26371) Start try again in 1 seconds...
2023-07-01 03:18:47.907 - debug: zigbee2mqtt.0 (26371) Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
2023-07-01 03:18:48.908 - debug: zigbee2mqtt.0 (26371) Error: socket hang up
2023-07-01 03:18:48.909 - warn: zigbee2mqtt.0 (26371) Start try again in 1 seconds...
2023-07-01 03:18:48.915 - debug: zigbee2mqtt.0 (26371) Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
2023-07-01 03:18:49.461 - info: host.tims-pi1 "system.adapter.zigbee2mqtt.0" disabled
@ticaki ticaki added the problem Something isn't working label Jul 1, 2023
@o0shojo0o
Copy link
Contributor

Ja das ist Korrekt, die Websocketverbindung unterstützt aktuell kein WSS, das muss erst noch angepasst werden.

o0shojo0o added a commit that referenced this issue Jul 12, 2023
@o0shojo0o
added WSS support for websoket connection
20a5a16 
closed #191
@o0shojo0o
Copy link
Contributor

Kannst du bitte mal den Dev Branche testen? -> https://github.com/o0shojo0o/ioBroker.zigbee2mqtt/tree/%23191
Und dann Hier die Einstellung vornehmen:
image

@ticaki
Copy link
Author

ticaki commented Jul 13, 2023 •
edited
Loading

geht nicht.
EDIT: im Debuglog stehts.

2023-07-13 10:10:39.667 - debug: zigbee2mqtt.0 (8400) Error: self-signed certificate

Sry das steht noch auf der Todoliste :)

@ticaki
Copy link
Author

ticaki commented Jul 13, 2023 •
edited
Loading

👍

2023-07-13 15:02:29.829 - info: zigbee2mqtt.0 (17350) starting. Version 2.7.5 (non-npm: o0shojo0o/ioBroker.zigbee2mqtt#%23191) in /opt/iobroker/node_modules/iobroker.zigbee2mqtt, node: v18.16.1, js-controller: 5.0.7
--
2023-07-13 15:02:29.891 - info: zigbee2mqtt.0 (17350) ================================= Adapter Config =================================
2023-07-13 15:02:29.892 - info: zigbee2mqtt.0 (17350) \|\| Zigbee2MQTT Frontend Scheme: https
2023-07-13 15:02:29.892 - info: zigbee2mqtt.0 (17350) \|\| Zigbee2MQTT Frontend Server: zigbee2mqtt.kiemen.com
2023-07-13 15:02:29.893 - info: zigbee2mqtt.0 (17350) \|\| Zigbee2MQTT Frontend Port: 8089
2023-07-13 15:02:29.894 - info: zigbee2mqtt.0 (17350) \|\| Zigbee2MQTT Connection Type: ws
2023-07-13 15:02:29.894 - info: zigbee2mqtt.0 (17350) \|\| Zigbee2MQTT Websocket Server: zigbee2mqtt.kiemen.com
2023-07-13 15:02:29.895 - info: zigbee2mqtt.0 (17350) \|\| Zigbee2MQTT Websocket Port: 8089
2023-07-13 15:02:29.895 - info: zigbee2mqtt.0 (17350) \|\| Zigbee2MQTT Websocket Auth-Token: unused
2023-07-13 15:02:29.896 - info: zigbee2mqtt.0 (17350) \|\| Zigbee2MQTT Websocket Dummy MQTT-Server: deactivated
2023-07-13 15:02:29.896 - info: zigbee2mqtt.0 (17350) \|\| Zigbee2MQTT Debug Log: deactivated
2023-07-13 15:02:29.897 - info: zigbee2mqtt.0 (17350) \|\| Proxy Zigbee2MQTT Logs to ioBroker Logs: activated
2023-07-13 15:02:29.897 - info: zigbee2mqtt.0 (17350) \|\| Use Kelvin: yes
2023-07-13 15:02:29.897 - info: zigbee2mqtt.0 (17350) ==================================================================================
2023-07-13 15:02:30.121 - info: zigbee2mqtt.0 (17350) Connect to Zigbee2MQTT over websocket connection.
2023-07-13 15:02:30.161 - info: zigbee2mqtt.0 (17350) ============================ Zigbee2MQTT Information =============================
2023-07-13 15:02:30.162 - info: zigbee2mqtt.0 (17350) \|\| Zigbee2MQTT Version: 1.32.0
2023-07-13 15:02:30.162 - info: zigbee2mqtt.0 (17350) \|\| Coordinator type: ConBee2/RaspBee2 Version: 0x26720700 Serial: /dev/ttyACM0
2023-07-13 15:02:30.162 - info: zigbee2mqtt.0 (17350) \|\| Network panid 27759 channel: 11 ext_pan_id: 0xdddddddddddddddd
2023-07-13 15:02:30.163 - info: zigbee2mqtt.0 (17350) ==================================================================================
2023-07-13 15:02:38.727 - info: host.tims-pi1 "system.adapter.zigbee2mqtt.0" disabled

nur das hier scheint noch falsch zu sein:

2023-07-13 15:02:29.894 - info: zigbee2mqtt.0 (17350) \|\| Zigbee2MQTT Connection Type: ws
Bildschirmfoto 2023-07-13 um 15 08 06

@o0shojo0o
Copy link
Contributor

o0shojo0o commented Jul 13, 2023 •
edited
Loading

Nein das ist der Typ und der Stimmt nur das Scheme habe ich im Log noch nicht drinnen.

@o0shojo0o
Copy link
Contributor

Jetzt sollte auch ein self-signed certificate gehen -> https://github.com/o0shojo0o/ioBroker.zigbee2mqtt/tree/%23191

@o0shojo0o o0shojo0o mentioned this issue Jul 19, 2023
Merged
o0shojo0o added a commit that referenced this issue Jul 19, 2023
@o0shojo0o
#191 (#204)
8757763 
* added WSS support for websoket connection

closed #191

* accept self-signed certificate
o0shojo0o added a commit that referenced this issue Jul 19, 2023
@o0shojo0o
chore: release v2.8.0
2fe98f2 
-   (o0shojo0o) added WSS support for websoket connection([#191](#191))
-   (o0shojo0o) small fixes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
problem Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

#191 arteck/ioBroker.zigbee2mqtt
2 participants
@o0shojo0o @ticaki