-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
iobroker.ham funktioniert nicht mehr mit homebridge 1.0.x #58
Comments
Indeed no functionality with 1.0.x `
` |
Jupp. Bitte downgraden. Die 1.0 ist wie die Versionsnummer sagt „breaking“ und da hat sich sehr viel geändert. Muss mal schauen was geht überhaupt. |
Do I need to downgrade to 0.4.5? How should I do it? |
If you have the adaoter working again then yes you should downgrade. Downgrade the same way as you updated but with @0.4.5 or such |
Somehow you updated homebridge ... it was not via the adapter |
Yes, I upgraded it too. Do I need downgrade adapter or homebridge? |
homebridge is the reason not the adapter |
OK. If I leave the current version of the adapter and downgrade the homebridge it will be enough? |
should be |
Which version of hombridge is right for me? |
which one you had befopre you upgraded homebride? I don't know ... it needs to be <1.0 |
I am updated on every new version |
sudo npm install -g -unsafe-perm homebridge@0.4.53 -g Is it right command? |
Is there any chance to get this fixed quite soon? Otherwise it would start to separate homebridge and iobroker again. |
Quite soon ... hm ... let me think ... homebridge 1.1.0 is based on a new hap library version and both projects where converted to typescript and so i consider them as a rewrite. The ham adapter is doing quite some interception magic and overwrites methods from the original classes. You are welcome to get familiar with all of this and provide needed PRs and code changes. Then it will be faster. If you can not then I‘m really sorry that you need to wait till I find time analyzing this. The solution to get it working again for now is to head back to homebridge <1.0 ... or what’s the exact reason to be on 1.x? |
Please try with a homebridge 1.1 and the new 2.0 of the adapter |
i have updated to v2.0 and the adapter gets green again with the plugin merdok/homebridge-xiaomi-fan#17 but the problem is i don't get any data set points for mapping to yahka |
As said: Please set iobroker adapter logging to debug (instances - exper mode - column loglevel) and then get the full log from adapter start from the logfile on disk (NOT via admin web ui!!) (/opt/iobroker/log/...) and post here |
iobroker.ham funktioniert nicht mehr mit homebridge 1.0.x
The text was updated successfully, but these errors were encountered: