Skip to content
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

Characteristic Warnings and Random Shutdown of AP #20

Open
Dann1bo1 opened this issue Feb 9, 2023 · 4 comments
Open

Characteristic Warnings and Random Shutdown of AP #20

Dann1bo1 opened this issue Feb 9, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@Dann1bo1
Copy link

Dann1bo1 commented Feb 9, 2023

Installed the forked plugin https://github.com/davidjbradshaw/homebridge-aeg-wellbeing a couple of days ago, everything ran fine for a several hours.
My AEG AX5 is properly being displayed in HomeKit.
Since Feb 8, I've been experiencing numerous issues. The airpurifier would not turn on at all through HomeKit, even Homebridge couldn't power it on. This issue seems to be remedied by restarting the child bridge.
My current issue is comprised of turning the airpurifier on and sometimes it just randomly powers off for no apparent reason.
The log just shows "Luftreiniger AirPurifier Active was set to: PowerOff".
I'm also getting numerous characteristics warnings for invalid values for a certain characteristic repeating at the interval that is set as "polling time" in the plugin's settings.

[09/02/2023, 20:31:57] [homebridge-aeg-wellbeing] This plugin generated a warning from the characteristic 'Swing Mode': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[09/02/2023, 20:32:06] [homebridge-aeg-wellbeing] This plugin generated a warning from the characteristic 'Current Temperature': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[09/02/2023, 20:32:06] [homebridge-aeg-wellbeing] This plugin generated a warning from the characteristic 'Current Relative Humidity': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[09/02/2023, 20:32:06] [homebridge-aeg-wellbeing] This plugin generated a warning from the characteristic 'Carbon Dioxide Level': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[09/02/2023, 20:32:06] [homebridge-aeg-wellbeing] This plugin generated a warning from the characteristic 'VOC Density': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[09/02/2023, 20:32:06] [homebridge-aeg-wellbeing] This plugin generated a warning from the characteristic 'Filter Life Level': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.

Environment:

  • Plugin Version: homebridge-aeg-wellbeing v1.0.2
  • Homebridge Version: v1.6.0
  • Node.js Version: v18.12.1
  • Operating System: Raspbian GNU/Linux Bullseye (11)
@Dann1bo1 Dann1bo1 added the bug Something isn't working label Feb 9, 2023
@davidjbradshaw
Copy link

I’ve also seen some issues last week where I think the remote server is hanging up the connection and the plugin fails to reconnect.

For the last week I’ve been testing a fix to force relogin when it fails and so far not seen the problem again, but maybe the remote has been better behaved.

Are you still having this issue?

@Dann1bo1
Copy link
Author

Dann1bo1 commented Feb 16, 2023

The characteristics warnings still persist, yes.

I can also confirm the reconnection issues on my end. Have to restart the child-bridge on an almost daily basis, to log in to the service again. A force relogin directly in the plugin would be amazing!

@davidjbradshaw
Copy link

@Dann1bo1 I have just published v1.1.0 of the AEG version. Hopefully that helps, as I have been running it for a week without issues.

I've also now enabled issue tracking on that project, so we should really continue the discussion over there.

@davidjbradshaw
Copy link

OK now on v1.1.1 and catching a lot more remote server issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants