ActiveByte / homebridge-loxone-connect

Websocket based homebridge plugin for controlling Loxone.
MIT License
24 stars 8 forks source link

Homebrige can't run #3

Closed digimon-Denmark closed 2 years ago

digimon-Denmark commented 3 years ago

I got a problem with the plugin.. can some one help me ? :/

[05/10/2021, 22:26:41] Plugin 'homebridge-loxone-connect' tried to register with an incorrect plugin identifier: 'homebridge-loxoneWs'. Please report this to the developer! [05/10/2021, 22:26:41] Registering platform 'homebridge-loxone-connect.LoxoneWs' [05/10/2021, 22:26:41] --- [05/10/2021, 22:26:41] Loading 3 platforms... [05/10/2021, 22:26:41] [Config] Initializing config platform... [05/10/2021, 22:26:41] [Config] Running in Service Mode [05/10/2021, 22:26:41] [google-smarthome] Initializing google-smarthome platform... [05/10/2021, 22:26:41] [google-smarthome] Initializing child bridge 0E:21:D7:BB:CA:2F [05/10/2021, 22:26:41] [LoxoneWs] Initializing LoxoneWs platform... [05/10/2021, 22:26:41] [LoxoneWs] Getting Loxone configuration. [05/10/2021, 22:26:41] [LoxoneWs] Platform - Waiting 8 seconds until initial state is retrieved via WebSocket. [05/10/2021, 22:26:41] [LoxoneWs] WS: connect [05/10/2021, 22:26:41] [HB Supervisor] Homebridge Process Ended. Code: null, Signal: SIGBUS [05/10/2021, 22:26:46] [HB Supervisor] Restarting Homebridge... [05/10/2021, 22:26:46] [HB Supervisor] Starting Homebridge with extra flags: -I -D [05/10/2021, 22:26:46] [HB Supervisor] Started Homebridge v1.3.4 with PID: 10460 Initializing HAP-NodeJS v0.9.4... [05/10/2021, 22:26:50] Loaded config.json with 0 accessories and 3 platforms. [05/10/2021, 22:26:51] Loaded 0 cached accessories from cachedAccessories. [05/10/2021, 22:26:51] --- [05/10/2021, 22:26:56] Loaded plugin: homebridge-config-ui-x@4.41.2 [05/10/2021, 22:26:56] Registering platform 'homebridge-config-ui-x.config' [05/10/2021, 22:26:56] --- [05/10/2021, 22:26:56] Loaded plugin: homebridge-gsh@2.1.0 [05/10/2021, 22:26:56] Registering platform 'homebridge-gsh.google-smarthome' [05/10/2021, 22:26:56] --- [05/10/2021, 22:26:57] Loaded plugin: homebridge-loxone-connect@1.1.1 homebridge API version: 2.7 [05/10/2021, 22:26:57] Plugin 'homebridge-loxone-connect' tried to register with an incorrect plugin identifier: 'homebridge-loxoneWs'. Please report this to the developer! [05/10/2021, 22:26:57] Registering platform 'homebridge-loxone-connect.LoxoneWs' [05/10/2021, 22:26:57] --- [05/10/2021, 22:26:57] Loading 3 platforms... [05/10/2021, 22:26:57] [Config] Initializing config platform... [05/10/2021, 22:26:58] [Config] Running in Service Mode [05/10/2021, 22:26:58] [google-smarthome] Initializing google-smarthome platform... [05/10/2021, 22:26:58] [google-smarthome] Initializing child bridge 0E:21:D7:BB:CA:2F [05/10/2021, 22:26:58] [LoxoneWs] Initializing LoxoneWs platform... [05/10/2021, 22:26:58] [LoxoneWs] Getting Loxone configuration. [05/10/2021, 22:26:58] [LoxoneWs] Platform - Waiting 8 seconds until initial state is retrieved via WebSocket. [05/10/2021, 22:26:58] [LoxoneWs] WS: connect [05/10/2021, 22:26:58] [HB Supervisor] Homebridge Process Ended. Code: null, Signal: SIGBUS

ActiveByte commented 3 years ago

Hey there,

how are you running homebridge? what version of homebridge are you running? Did you try running the homebridge-loxone-connect plugin alone?

digimon-Denmark commented 3 years ago

I'm running

Npm Version | v7.24.2 Node.js Version | v14.18.0 Homebrigde 1.3.4 homebridge-config-ui-x v4.41.2

And i have try to Run the Loxone plugin alonen and its still not working

digimon-Denmark commented 3 years ago

now i got a new problem.. made a fresh install of homebrige on ubuntu.

[6.10.2021 20.57.09] [LoxoneWs] WS: connect WebSocket error: Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006 [6.10.2021 20.57.09] [LoxoneWs] WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end Websocket Connection closed: 1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END Websocket Connection closed: 4003 Forbidden - IP 192.168.0.31 temporarily blocked, too many failed login attempts (1) [6.10.2021 20.57.09] [LoxoneWs] WS: connect Websocket Connection closed: 1002 Control frames must not be fragmented. Websocket Connection closed: 1002 Control frames must not be fragmented. Websocket Connection closed: 4003 Forbidden - IP 192.168.0.31 temporarily blocked, too many failed login attempts (75) Websocket Connection closed: 4003 Forbidden - IP 192.168.0.31 temporarily blocked, too many failed login attempts (75) Websocket Connection closed: 4003 Forbidden - IP 192.168.0.31 temporarily blocked, too many failed login attempts (75) Websocket Connection closed: 4003 Forbidden - IP 192.168.0.31 temporarily blocked, too many failed login attempts (74) Websocket Connection closed: 4003 Forbidden - IP 192.168.0.31 temporarily blocked, too many failed login attempts (74) Websocket Connection closed: 4003 Forbidden - IP 192.168.0.31 temporarily blocked, too many failed login attempts (74) Websocket Connection closed: 4003 Forbidden - IP 192.168.0.31 temporarily blocked, too many failed login attempts (74) Websocket Connection closed: 4003 Forbidden - IP 192.168.0.31 temporarily blocked, too many failed login attempts (73) Websocket Connection closed: 4003 Forbidden - IP 192.168.0.31 temporarily blocked, too many failed login attempts (73) Websocket Connection closed: 4003 Forbidden - IP 192.168.0.31 temporarily blocked, too many failed login attempts (73).

My Ip from the brige getting block by the miniserver..

skippone commented 3 years ago

It appears that your login detail eg. username and password are incorrect.

rc-itcon commented 3 years ago

Hi,

i opened a new case, bacause i'm not sure if you are facing exactly the same Problem. could you confirm that #7 is the same issue?

thanks

Arrow768 commented 2 years ago

I have the same issue.

When I try to set up the plugin to connect to the loxone miniserver I get the following errors in the log:

[12/5/2021, 9:57:37 PM] [LoxoneWs] WS: connect
Websocket Connection closed:  1000 normally closed
[12/5/2021, 9:57:39 PM] [LoxoneWs] WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[12/5/2021, 9:57:39 PM] [LoxoneWs] WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
[12/5/2021, 9:57:42 PM] [LoxoneWs] WS: connect
WebSocket error:  Socket Error: undefined ERR_STREAM_WRITE_AFTER_END 1006
[12/5/2021, 9:57:42 PM] [LoxoneWs] WS: connection error, reconnecting...Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END

Until the following message shows up in the logs:

homebridge    | Websocket Connection closed:  1006 Socket Error: undefined ERR_STREAM_WRITE_AFTER_END
homebridge    | Websocket Connection closed:  4003 Forbidden - IP 192.168.51.151 temporarily blocked, too many failed login attempts (108)
homebridge    | Websocket Connection closed:  4003 Forbidden - IP 192.168.51.151 temporarily blocked, too many failed login attempts (108)
homebridge    | Websocket Connection closed:  4003 Forbidden - IP 192.168.51.151 temporarily blocked, too many failed login attempts (108)
homebridge    | Websocket Connection closed:  4003 Forbidden - IP 192.168.51.151 temporarily blocked, too many failed login attempts (108)

Homebridge is running in a docker(-compose) container in the same subnet as the loxone miniserver. I was able to successfully login at the web-interface of the loxone mini-server with the credentials I have entered in the config file. My miniserver is running on version 12.2.11.5

ActiveByte commented 2 years ago

Are you using a custom user or the root from loxone? Try using the root account, i’m looking in to this but it seems that i get the same error when using a self made user account inside loxone

ActiveByte commented 2 years ago

Can you test if the problem still occurs with the latest version of this plugin?

digimon-Denmark commented 2 years ago

The plugin works after a few days. and works fine with the new update :)

Arrow768 commented 2 years ago

Sorry for the delay in responding. The issue has been resolved for me as well. Thank you for the update.