Latest release crashes on startup

[mbriney]

Something has gone wrong with the latest release on my system. It is possible to post a previous version number?

[2018-12-3 19:37:12] ---
Load homebridge-bond.Bond

/usr/lib/node_modules/homebridge-bond/dist/index.js:10
        let email = config['email'];
                          ^
TypeError: Cannot read property 'email' of null
    at new BondPlatform (/usr/lib/node_modules/homebridge-bond/dist/index.js:10:27)
    at Server._loadDynamicPlatforms (/usr/lib/node_modules/homebridge/lib/server.js:347:30)
    at Server.run (/usr/lib/node_modules/homebridge/lib/server.js:88:8)
    at module.exports (/usr/lib/node_modules/homebridge/lib/cli.js:45:10)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (module.js:653:30)
    at Object.Module._extensions..js (module.js:664:10)
    at Module.load (module.js:566:32)
    at tryModuleLoad (module.js:506:12)
    at Function.Module._load (module.js:498:3)
    at Function.Module.runMain (module.js:694:10)
    at startup (bootstrap_node.js:204:16)
    at bootstrap_node.js:625:3

[plainsane]

0.1.1 was previous version
https://www.npmjs.com/package/homebridge-bond/v/0.1.1
What version are you running because this error acts like it can’t read your config correctly

[iRayanKhan]

Make sure this is installed globally

Sudo npm i -g homebridge-bond

[iRayanKhan]

And it may help to delete the bond cache since it's what I did

[mbriney]

How do you delete the cache?

…

On Dec 5, 2018, at 11:41 AM, Rayan A. Khan ***@***.***> wrote: And it may help to delete the bond cache since it's what I did — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#11 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAPdtwfAR_TKsep0LIc26Z2e8lmcpHFCks5u1_cmgaJpZM4Y_sYs>.

[plainsane]

which version are you coming from? your error looks like a config issue

[miket0429]

I have the same issue with 0.2.0. Coming from 0.1.1 or 0.1.0, everything was fine before trying to upgrade.

[miket0429]

I just found a 0.1.1 tar.gz online and manually rolled back to 0.1.1 and it works fine again.

[mbriney]

@miket0429 how did you manually roll it back? I only see one official release for 0.2.0.

[iRayanKhan]

Try
sudo npm I -g homebridge-bond@0.1.1

[plainsane]

This is most likely caused by the reverse switch since I removed it, as it was superfluous after adding a direction characteristic to the fan

[aarons22]

Closing this as it is no longer applicable with v2 API.