-
-
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
Problem with version 2.3.1 and 2.3.3 #97
Comments
My config: |
Me too. Where is my Sensibo? |
Solved it myself |
Same problem for me, my AC units disappeared after update, but I still see humidity sensors. I'm logged in with creds, without API key. |
Same issue for me. Logged in via API, cred fields empty. Been working great until update. Only have humidity sensors with latest version. Reverted to 2.2.0 and AC units came back. Please fix! |
same situation... rollback on 2.2.0 working great |
Same here, AC is gone from HomeKit |
Confirmed same issue also for me, reverted to 2.2.0 version and everything again is back as normal. |
same happened to me, how do I revert back to 2.2.0? also will I loose all my automations that include sensibo accessories? |
hey guys any updates here? |
To revert (if you are using Homebridge) go to the tab Plugins and click on the wrench of the Sensibo plugin, then choose Install Previous Version. |
I reverted back to 2.2 and can confirm all the automations, scenes and button associates all got nuked and have to start from scratch for those ACs |
I confirm, at home, same issue with version 2.3.x. I switched back to 2.2.0 to retrieve my devices. |
@JacVid did it remove it from your automations and scenes? |
yes, the devices had completely disappeared from my home. |
yeah .. i think we ahve to live with it |
Instämmer med ovanstående, funkar bara med 2.2 |
My setup also has stopped working with versions 2.3.1 and 2.3.3. Humidity and temperature sensors reporting fine, but climate react switch ineffective. Tried alternatively using username and password or the API key and neither had any effect. Reverting to 2.2.0 restored functionality. Here's my config, running on Homebridge 1.6.0: { |
Not working here also, using 2.2.0 to make it work |
Hi all / @RB72 Very sorry to hear about the issue! Would it be possible to please turn on debug mode ("debug": true in the config) and provide an anonymised version of the Sensibo API response? Right now I'm specifically interested in what's stated for "productModel", but the full response will be most useful moving forward. Would also be great to get a copy of any Sensibo plugin specific error or warning messages when Homebridge restarts. |
“productModel”:”skyplus” |
Thanks @RB72 I've just created a beta version of v2.3.4 and released it on NPM which includes a hotfix In Homebridge you'll need to select it from the 'Alternate Versions' menu. |
Yeah, that seems to fix it. |
Just installed beta, and devices disappeared again... “productModel”:”skyv2” |
For me 2.3.4 beta2 is still working fine. |
Thx, a lot 🤝 Works fine now |
2.3.4 confirmed working for Sensibo Air as well. Thanks for the fix! |
@benwebbbenwebb I've upgraded to 2.3.4 and two of my three skyv2 are working, one shows up in HomeKit as "This accessory is not currently supported by the Home app" -- was fine on 2.2 |
That sounds a bit odd @slawnz Any chance you can share your Sensibo API response and other debug log info? It will be in the Homebridge logs when you turn on Debug mode within the homebridge-sensibo-ac plugin config. |
@benwebbbenwebb Deleting the bridge from my home and re-adding it fixed the problem |
2.3.4 fixed the issue also for me, thanks for the support and Merry Christmas to all! |
Closing as, based on feedback, resolved with v2.3.4 |
I have two Sensibo Air modules, they were working fine with plugin 2.2.0.
After updating to version 2.3.1 or version 2.3.3 they are gone in Apple Home.
Homebridge (v1.6.0) does not show any error messages, also after enabling debug logging for the plugin there are no errors or warnings.
I reverted to plugin version 2.2.0 to get the modules working again.
The text was updated successfully, but these errors were encountered: