listen() not working again

[thechile]

Hi again

It seems #88 is back again :(

    wsclient.serviceHandlers.connected = function () {

        console.log('Bittrex Websocket connected !')

        bittrex.websockets.listen(function(data, client) {
            if (data.M === 'updateSummaryState') {
                data.A.forEach(function(data_for) {
                    data_for.Deltas.forEach(function(marketsDelta) {
                        console.log('Ticker Update for '+ marketsDelta.MarketName, marketsDelta)
                    })
                })
            }else{
                console.log(`data.M: ${data.M}`)
            }
        })
}

Just gives me

Bittrex Websocket connected !
data.M: undefined
data.M: undefined
data.M: undefined
data.M: undefined
data.M: undefined
data.M: undefined
data.M: undefined
data.M: undefined
data.M: undefined

And if i try the previous fix i.e.

wsclient.call('CoreHub', 'querySummaryState').done(function (err, result) {

Then it only gives me back the summaries info but no socket feed.

Anyone else have this failure ?

[dparlevliet]

can you run the examples/bittrex.websockets.listen.example.js file?

[thechile]

tried but doesn't work.. no data received. Only if i subscribe to individual coin pairs do i get anything. Seems the allTicker feed is broken or has been removed completely.

Anyone confirm ?

[dparlevliet]

I cannot confirm. I have bots running and receiving data fine and all of the examples work fine.

Can you double check to make sure you're a) running the right library (not the old one) and b) using the right version? That's really all I can offer you atm, sorry.

[thechile]

ok thanks, very odd. I run the listen example and it connects but no data. npm version is latest and is correct version homepage: 'https://github.com/dparlevliet/node.bittrex.api',

[nivonova]

+1; 0.8.2 introduced a breaking change preventing the callback in websockets.listen from being fired.

[dparlevliet]

I think I was able to replicate this issue and I think I have resolved it in the next release. Not 100% sure, but I ran in to an issue while testing. Stay tuned then you can test again.