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: MAX_CLIENTS=6 #128

Open
mark82436 opened this issue Mar 12, 2018 · 27 comments
Open

Error: MAX_CLIENTS=6 #128

mark82436 opened this issue Mar 12, 2018 · 27 comments

Comments

@mark82436
Copy link

i have some errors with version homebridge-harmonyhub v0.3.0-alpha.2
homebridge crashes some times

my config are 3 hubs on the network homebridge 0.4.38

Logfile
Uncaught exception error: { Error: MAX_CLIENTS=6 at Connection.onStanza (/usr/local/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-core/lib/Connection.js:355:17) at StreamParser.<anonymous> (/usr/local/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-core/lib/Connection.js:226:10) at emitOne (events.js:116:13) at StreamParser.emit (events.js:211:7) at SaxLtx.<anonymous> (/usr/local/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-core/lib/StreamParser.js:58:14) at emitOne (events.js:116:13) at SaxLtx.emit (events.js:211:7) at SaxLtx._handleTagOpening (/usr/local/lib/node_modules/homebridge-harmonyhub/node_modules/ltx/lib/parsers/ltx.js:31:18) at SaxLtx.write (/usr/local/lib/node_modules/homebridge-harmonyhub/node_modules/ltx/lib/parsers/ltx.js:105:26) at StreamParser.write (/usr/local/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-core/lib/StreamParser.js:123:17) at Connection.onData (/usr/local/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-core/lib/Connection.js:305:17) at emitOne (events.js:121:20) at Socket.emit (events.js:211:7) at addChunk (_stream_readable.js:263:12) at readableAddChunk (_stream_readable.js:250:11) at Socket.Readable.push (_stream_readable.js:208:10) at TCP.onread (net.js:594:20) stanza: Stanza { name: 'stream:error', parent: null, children: [ [Object], [Object] ], attrs: { 'xmlns:stream': 'http://etherx.jabber.org/streams' } } }

@mdpp
Copy link

mdpp commented Mar 25, 2018

I have the same issue (but I have just 1 harmony hub)

@m0rph2k
Copy link

m0rph2k commented Apr 11, 2018

same Error --> 2 harmony hubs

@jabz10
Copy link

jabz10 commented Apr 15, 2018

I have the same error, 2 hubs.

@dado3212
Copy link

Same error (sporadic), 1 hub.

@Squuiid
Copy link

Squuiid commented Apr 27, 2018

Same issue here. Happens after a few mins to an hour. The plugin is unusable unfortunately.
1 hub.

@MikeDeltaHH
Copy link

Same error here with 2 hubs and a lot of crashes per day... seems that this problem will never be solved! :(

@gvansteelant
Copy link

The latest version of homebridge and the harmony plugin ran fine for weeks but recently it started crashing again with this error message. I only have 1 hub and am really wondering what's going on here.
It seems there's not much response from the developer so I'm wondering whether or not to abandon the idea completely.

@shaneakus
Copy link

having this issue as well

@CharlesWiltgen
Copy link

Just installed homebridge-harmonyhub, and ran into this on the first day.

Error: MAX_CLIENTS=6                                                                                                                                                  
    at Connection.onStanza (/usr/local/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-core/lib/Connection.js:355:17)                                   
    at StreamParser.<anonymous> (/usr/local/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-core/lib/Connection.js:226:10)                              
    at StreamParser.emit (events.js:180:13)                                                                                                                           
    at SaxLtx.<anonymous> (/usr/local/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-core/lib/StreamParser.js:58:14)                                   
    at SaxLtx.emit (events.js:180:13)                                                                                                                                 
    at SaxLtx._handleTagOpening (/usr/local/lib/node_modules/homebridge-harmonyhub/node_modules/ltx/lib/parsers/ltx.js:31:18)                                         
    at SaxLtx.write (/usr/local/lib/node_modules/homebridge-harmonyhub/node_modules/ltx/lib/parsers/ltx.js:105:26)                                                    
    at StreamParser.write (/usr/local/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-core/lib/StreamParser.js:123:17)                                  
    at Connection.onData (/usr/local/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-core/lib/Connection.js:305:17)                                     
    at Socket.emit (events.js:185:15)                                                                                                                                 
    at addChunk (_stream_readable.js:269:12)                                                                                                                          
    at readableAddChunk (_stream_readable.js:256:11)                                                                                                                  
    at Socket.Readable.push (_stream_readable.js:213:10)                                                                                                              
    at TCP.onread (net.js:578:20)

@eshaka
Copy link

eshaka commented Jun 10, 2018

same error, one hub.
at Connection.onStanza (/usr/local/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-core/lib/Connection.js:355:17)
Error: MAX_CLIENTS=6

@Squuiid
Copy link

Squuiid commented Jun 10, 2018

Honestly, this project should be pulled. So many people are wasting their time on it.
It does NOT work unfortunately.

@dado3212
Copy link

It does SOMETIMES work.

@filoor
Copy link

filoor commented Jun 14, 2018

Having the same issue 2 hubs

@oetelaar24
Copy link

I think I may have a solution for you guys, see my comment here:
#137 (comment)

@lespatots
Copy link

As my error starts off slightly differently I've added below. I've removed the plugin for now. I might create a special Homebridge instance so that only that instance is affected by the failures.

/usr/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-core/lib/Connection.js:355
var error = new Error('' + getAllText(stanza))
^
Error: MAX_CLIENTS=6
at Connection.onStanza (/usr/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-core/lib/Connection.js:355:17)

@Squuiid
Copy link

Squuiid commented Sep 26, 2018

Folks, Harmony hub is no longer needed with the release of Apple Siri shortcuts. I now control my Harmony Hub with Siri Shortcuts and got rid of HomeBridge. See here for how:
https://www.macstories.net/ios/how-to-trigger-ifttt-applets-with-ios-12s-new-shortcuts-app-and-siri/
It works flawlessly every single time. Highly recommend.

@pponce
Copy link

pponce commented Dec 10, 2018

Has anyone checked recently if this error is still occurring?
I see changes have been made to https://github.com/swissmanu/harmonyhubjs-client to address this issue.

@pponce
Copy link

pponce commented Dec 11, 2018

I'm giving it a go with 0.3.0-alpha.2.
I actually had to edit the package.json file that was installed with 0.3.0-alpha2 and changed the value version for harmonyhubjs-client to "^1.1.6" within the file. It had some other value that caused it not to use the latest version.
Then I ran npm update in the existing directory where it was installed to get it to use the lastest harmonyhubjs-client version.

I'll report back how things go after a good week of using it.

@pponce
Copy link

pponce commented Dec 18, 2018

Things appeared to be working pretty well. Now my only problem is that Harmony removed the local API's in their most recent firmware. So now it does not work at all...... :(

@Pensive
Copy link

Pensive commented Feb 6, 2019

@pponce Just out of interest- I assume you've enabled the beta functionality now - and can you comment if your patching fixed the maxclients issue?

@pponce
Copy link

pponce commented Feb 6, 2019

Yeah I ran without issue for a long time using 0.3.0-alpha2 with harmonyhubjs-client 1.1.6. Didn’t have any max client issues that I could detect.

I recently moved to one of the websocket implementations that is using airborne04’s js client. Not sure if Logitech is going to favor ws or xmpp going forward. But it seems there are some great working options now for homebridge.

@Pensive
Copy link

Pensive commented Feb 6, 2019

I’m having trouble with websockets - tried nicos and materiks.

Works fine from Siri or the home app but both have problem when I link them via a hue switch.

Works fine at first but come down in the morning and materiks just doesn’t work and pings up a websocket not open error, nicos works but it takes 20 or 30 seconds.

For some reason the sockets go to sleep and they are not properly woken by a 3rd party HomeKit switch.

The hue switch clicks are reaching HomeKit because the icon shakes. So I’m thinking of resurrecting this one and making it 12.2 compliant.

Local apis will always be superior to web based ones.

@pponce
Copy link

pponce commented Feb 6, 2019

Have you tried materiks using airborne04’s xmpp client as a dependency?
I think they can be swapped out. Airborne04 said the websocket version of the client was a drop in replacement for the xmpp version.

But as for this plugin.
I don’t use a hue switch to control my activities but I didn’t have any issues with the 0.3.0 alpha2 with the latest harmonyhubjs-client.

@Pensive
Copy link

Pensive commented Feb 6, 2019

Ooooh that would be a quick and easy fix! I’ll give it a go!!!

@pponce
Copy link

pponce commented Feb 19, 2019

@Pensive
I know you said you were moving to use XMPP. Just wanted to let you know that Nico's websocket implementation i believe fixed the websockets not being open issue you experienced.

@nicoduj
Copy link

nicoduj commented Feb 19, 2019

Yes , and by the way the websocket api is a local one :)

Sent with GitHawk

@Pensive
Copy link

Pensive commented Feb 19, 2019

Interesting - thank you for the headsup! I haven’t had a chance to play with it so I’m still running websockets at the mo - I’ll try updating :)

I thought a huge part of the hoohah when they shut down the local API was that the websockets implementation went out to the cloud server?

I’ll look in greater detail

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