plugins stopped working, for example loxone-ws

Hello,

After yesterday’s upgrade I am experiencing an error with multiple plugins, but my main request is that the loxone-ws can not log in into my loxone miniserver, which worked before. os: ubuntu server 18.04 LTS

the log shows:

AbstractItem (/usr/lib/node_modules/homebridge-loxone-ws-adv/items/AbstractItem.js:22:25)
    at PushbuttonItem.SwitchItem (/usr/lib/node_modules/homebridge-loxone-ws-adv/items/SwitchItem.js:12:23)
    at new PushbuttonItem (/usr/lib/node_modules/homebridge-loxone-ws-adv/items/PushbuttonItem.js:6:27)
    at exports.Factory.parseSitemap (/usr/lib/node_modules/homebridge-loxone-ws-adv/libs/ItemFactory.js:66:29)
    at Request._callback (/usr/lib/node_modules/homebridge-loxone-ws-adv/index.js:88:38)
    at Request.self.callback (/usr/lib/node_modules/homebridge-loxone-ws-adv/node_modules/request/request.js:185:22)
    at Request.emit (events.js:310:20)
    at Request.<anonymous> (/usr/lib/node_modules/homebridge-loxone-ws-adv/node_modules/request/request.js:1154:10)
    at Request.emit (events.js:310:20)
    at IncomingMessage.<anonymous> (/usr/lib/node_modules/homebridge-loxone-ws-adv/node_modules/request/request.js:1076:12)
[4/30/2020, 10:51:41] Got SIGTERM, shutting down Homebridge...

config.json:

{ “bridge”: { “name”: “MyHome”, “username”: “0E:05:CD:57:42:3F”, “port”: 51484, “pin”: “907-20-397” }, “accessories”: [], “platforms”: [ { “name”: “Config”, “port”: 8581, “auth”: “form”, “theme”: “dark-mode”, “tempUnits”: “c”, “lang”: “auto”, “platform”: “config” }, { “platform”: “LoxoneWs”, “name”: “Loxone”, “host”: “10.0.0.10”, “port”: “80”, “username”: “username”, “password”: “password” } ] }

[Cardo1]

@Cardo1 how do you roll back to vs 1.0.3. It has all but broke my homebridge. I can no longer get it to add to homekit

npm install -g --unsafe-perm homebridge@1.0.3

Adding @ and a version number to the package name tells it to install that version.

[Cardo1]

@Cardo1 @FlyingKiwiJosh It would be great if you could actually report what plugins break and paste the error appearing in the log messages, so we can actually fix those problems.

I updated to 1.0.4 again and this time it all worked. ?? Must’ve glitched when I updated it the first time (I had last updated a few weeks ago, so jumped a few versions?)