-
Notifications
You must be signed in to change notification settings - Fork 26
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
No homebridge 1.0 Support #51
Comments
+1. same error messages. Run on a Synology DS218+, Loxone Miniserver. Everything up to date. |
same here. with the loxone-ws-adv (successor plugin) too. edit: rollback not working. seems to belong to dependencies, not homebride itself. very disappointing :/ |
@Sroose you current "inherit" your AbstractItem from PlatformAccessory. So to fix that you could correctly inherit from PlatfromAccessory, or just remove the inheritance altogether as there is not benefit, it's not used and it's just wasting memory. I don't know which mechanics you may abuse from the inhertiance, so other parts of the code may need to the adjusted. EDIT: the examples are written in Typescript, but the functionality can be discovered nonetheless and be converted into regular Javascript code. |
+1 same error here i am not that experienced programmer to find out myself how to solve this in your code but afterwards, explain me how to solve the problem edit: found in homebridge/homebridge#2545 to rollback to version 1.0.3, but that didnt helped me either, failure code completely identical to topic opener |
@keuninkske if you really want to rollback. You probably need to rollback to some 0.4.x version. |
pff, i had an old instalation, stopped working somewhere in november or december (issue unknown, probably due to an update of the UI plugin) i am hobby python programmer |
I tried to rollback to 0.4.x - working - but due to dependencies or somewhat else the loxone plugin does not work. |
Just got this bug overnight... any news? Has someone found any solution? |
Hi, I have updated this loxone plugin to the latest v1.0.9 (just committed) and i have homebridge v1.0.4 and i am still getting the looping/restarting error with the Platform Accessory error (below) [5/5/2020, 6:31:33 PM] [Loxone] Platform - Retrieving initial config from http://homebridge:[email protected]:7777/data/LoxApp3.json |
i just finished updating also anyway, i am looking forward to the solution |
This plugin needs an update. As already explained. Homebridge can’t really fix this. |
Yes that is why we are posting on here to assist @Lumoc with the issues and to inform him that we are having problems still with the latest updates he has committed today as he is the author. If it was an issue with homebridge we would post on the main homebridge pages? |
so, what you are explaining is that: what is very strange, i have only the loxone plugin metioned in the error i am having
|
Same here...
|
Lumoc was so kind to update homebridge-loxone-ws-adv, but his update did not work yet. |
It seems that there's a new version of Lumoc's ported plugin (1.0.17?), but I am not able to install it. Can someone confirm it that version is working? Thanks in advance |
I uninstalled the plugin (1.0.7) and reinstalled it (UI said 1.0.11?). |
I just installed a fresh Homebridge and homebridge-loxone-adv (.17) and it does not work. |
There were several updates from Lumoc yesterday i tried each one that came in, some threw new errors, one of them did connect to Loxone but couldn't handle any of the accessories & the latest version 1.0.17 still doesn't work with the same error (TypeError: Class constructor PlatformAccessory cannot be invoked without 'new' at PushbuttonItem.AbstractItem) looks like Lumoc is still working on it from all the updates so i'm going to wait a few days/week before i downgrade homebridge to get back up and running (if you run 'sudo npm install -g --unsafe-perm [email protected]' this will downgrade homebridge to v0.4.53 which does work, however some other plugins you have may have been updated to only work with homebridge v1+ so they may stop working by doing this, so if you have homebridge and only use the loxone plugin i would advise downgrading and checking this page until a stable release is made) |
I guess that there are no good news yet... I was afraid that this may eventually happend... |
You can have multiple instances of homebridge bridges running under HomeKit, and one instance only supports 100 accessories anyway so i was going to have to add another for loxone anyway soon as I have around 90 accessories in my loxone setup. For the sake of £40-60 you can buy another Pi and install homebridge v0.4.53 with loxone-we-adv which works fine, then use the other homebridge instance for the most up to date homebridge version for all other plugins ... this is what I’m going to do it is a relatively cheap way to get around the problem until this is fixed. Hope this helps |
It’s a bit of a hack, but I believe you can run multiple homebridge instances on the same server. |
Yes you can but I’m not sure if you can ru. Different versions of homebridge as multiple instances, for example I have the ring doorbell plugin which requires homebridge v1+ so I don’t think I can home that aswell as homebridge v0.4.53 on the same server (easily) ? |
I've seen that homebridge has updated to version 1.1.0. Has someone tried, or has someone any good news? |
Just tried it. Same issue. |
Fix is here with v1.0.18 of my plugin
|
thanks allot to @Lumoc and @geilername for helping out |
Awesome! It worked. Thanks for your effort @Lumoc !! |
I just installed it with a fresh homebridge. It works and I’m testing before replacing the main system. I’ve seen a few disconnects from the miniserver but I’ll advise of any problems. Thanks for your work! Update: It has been working for over a week now. Thanks again! |
Hi, I'm trien to get Loxone Ws Adv 1.0.18 running. We are using: So, basicly it will first connect once, show rooms and accessories, but after 1 sec it starts spamming:
When we change IP we can connect again once for 1 sec, then it loops again into error. Can somebody please help us?
|
@Masegi I have the same issue. Do you have solved it? |
no actually not :( |
I've did a clean install and having this issue too. Any fixes? |
well, I switched to another loxone plugin, that's working fine. |
@Masegi which one? |
After updating to homebridge 1.0.1, I got the following error message:
Running in an DS718+II Container with a Loxone Miniserver.
The text was updated successfully, but these errors were encountered: