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

Illegal Characteristic Supplied on Homebridge 1.3.0 Beta #56

Closed
Marfre888 opened this issue Feb 16, 2021 · 13 comments
Closed

Illegal Characteristic Supplied on Homebridge 1.3.0 Beta #56

Marfre888 opened this issue Feb 16, 2021 · 13 comments
Assignees
Labels

Comments

@Marfre888
Copy link

Marfre888 commented Feb 16, 2021

Describe the bug
As Homebridge log states, firmware characteristic is supplied as a number not string.

Version you use

  • homebridge version 1.3.0-Beta
  • node version 14.15.5
  • plugin version 0.6.2

To Reproduce
Upon restarting Homebridge with 1.3.0Beta

error

battery

@mrmaximas
Copy link

same issue

@Marfre888
Copy link
Author

evatmo

@ghost
Copy link

ghost commented Feb 20, 2021

Same here too.

@DJay-X
Copy link

DJay-X commented Feb 20, 2021

Public of Homebridge v1.3.0

[20.2.2021, 11:45:42] [homebridge-eveatmo] This plugin generated a warning from the characteristic 'S2W2': SET handler returned write response value, though the characteristic doesn't support write response! See https://git.io/JtMGR for more info.
[Zuhause (Wohnzimmer) Balkon@Zuhause (Wohnzimmer) Balkon History@S2W1] SET handler returned write response value, though the characteristic doesn't support write response!
[20.2.2021, 11:45:42] [homebridge-eveatmo] This plugin generated a warning from the characteristic 'S2W1': SET handler returned write response value, though the characteristic doesn't support write response! See https://git.io/JtMGR for more info.

@skrollme
Copy link
Owner

Looks like I have to update to 1.3 to check and fix this... :D

@skrollme
Copy link
Owner

I fixed the firmware- and hopefully the battery-characteristics warning although the later does not showed up in my logs.
When do S2W1 and S2W2-warnings show up in your logs @DJay-X ? On Startup, every now and then, while fetching the data (via EVE.app)? I haven't seen them so far either.

skrollme pushed a commit that referenced this issue Feb 20, 2021
@ghost
Copy link

ghost commented Feb 20, 2021

@skrollme when can we expect the update and test if there are any further issues? :)

@skrollme
Copy link
Owner

I want to wait for the reply of DJay concerning his problem. As far as I understand the plugin works as it did before, there are just some warning log entries now. So no need to hurry

@mrmaximas
Copy link

after update HB to 1.3.0 release no warnings appear

@DJay-X
Copy link

DJay-X commented Feb 21, 2021

I want to wait for the reply of DJay concerning his problem. As far as I understand the plugin works as it did before, there are just some warning log entries now. So no need to hurry

Thanks @skrollme I waited yesterday and today but was not able to reproduce the log entry for whatever reason. So we are on the same page, nothing critical I guess. Thanks again.

skrollme pushed a commit that referenced this issue Feb 21, 2021
@skrollme
Copy link
Owner

update 0.6.3 was released an hour ago and is already running on my setup. So far most of the warning are gone. But now the S2W1 and S2W2-warnings showed up in my logs too, @DJay-X :D
It will take a look at it soon and publish another release when I found a fix for this.

skrollme pushed a commit that referenced this issue Feb 21, 2021
@ghost
Copy link

ghost commented Feb 21, 2021

update 0.6.3 was released an hour ago and is already running on my setup. So far most of the warning are gone. But now the S2W1 and S2W2-warnings showed up in my logs too, @DJay-X :D
It will take a look at it soon and publish another release when I found a fix for this.

Same here, I got the warnings now too ^^

PS: I am using V1 from Netatmo Weatherstation, with main indoor module, secondary indoor module and one outdoor module, if that helps to evaluate where theese warnings are coming from.

@skrollme
Copy link
Owner

Looks like the S2W1 and S2W2-warnings come from the underlying fakegato-plugin, which is used to handle the history-functionality. I updated homebridge-eveatmo to the latest version if fakegato (0.6.1) and just published another release 0.6.4. Because the S2W*-warnings come not from the code of homebridge-eveatmo, it looks like there is nothing more I can do about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants