search

skrollme / homebridge-eveatmo

Homebridge plugin which adds a Netatmo weatherstation as HomeKit device and tries to act like Elgato Eve Room/Weather
Apache License 2.0
69 stars 7 forks source link

Firmware-Update showing up #2

Closed DJay-X closed 7 years ago

DJay-X commented 7 years ago

First of all thanks for this great plugin. Love it and works good with my first try. Using Netatmo Rain Sensor and a few indoor and outdoor Sensors. What I was wondering is that the Eve App is showing a Firmware-Update for Version 1.3.1 (466) for the 8 Devices added by homebridge-eveatmo. Any chance to get rid of this?

Thanks again und viele Grüße. ;)

skrollme commented 7 years ago

I'm seeing this by myself but for the beginning it tried to change as little as possible from the current known state about the protocol. I will try to fix this in one of the next updates

simont77 commented 7 years ago

It should be due to the characteristic E863F11E. I saw the same behavior with the fake accessory I user for history experiments. I did not find any other useful use for that characteristic.

skrollme commented 7 years ago

thanks, @simont77. I will give it a try.

skrollme commented 7 years ago

Please check out the newest release 0.2.4, @DJay79. It is already on NPMJS, so (sudo) npm install -g homebridge-eveatmoshould do it.

DJay-X commented 7 years ago

@skrollme Thanks a lot. Version 0.2.4 works for me. No asking for Firmware-Update anymore. Great! 👍🏻 Any chance to see Netatmo Thermostat working with your plugin in the near future? This is now the only reason why I still use homebridge-netatmo.

Thanks again for your work and sharing.

skrollme commented 7 years ago

Thanks a lot. Version 0.2.4 works for me. No asking for Firmware-Update anymore. Great! 👍🏻

Great to hear that!

Any chance to see Netatmo Thermostat working with your plugin in the near future? This is now the only reason why I still use homebridge-netatmo.

I do not own a thermostat by myself so it has no real priority for me at the moment. My next goal is to get the history service running and some refactoring because the plugin seems to call the API more often than it should. This can easily lead to soft-bans at the Netatmo API, if you restart Homebridge too often. So for the moment I would suggest you use the homebride-netatmo and limit it to the thermostat via config. But feel free to add add a new Issue here for this topic. It won't get forgotten ;)