Maxim Kulkin

@dezdeepblue It is not quite obvious from repository you mentioned what a "history" feature is. Could you elaborate that?

From fakegato-history repository I see that they use custom characteristics and base64 serialized data: https://github.com/simont77/fakegato-history/blob/master/fakegato-history.js#L84-L137 That could work but surely it will work only with Elgato application.

This log does not demonstrate the problem: some client sends request and gets 404. There's nothing wrong with that.

What you need to do is: 1) use .getter_ex and .setter_ex instead of .getter and .setter. The .*_ex variants are the same getters and setters, except for they [take a...

> is that ok or whats the function of „.primary=true“? No, this is not OK. Accessory should have only one primary service. > when should I make a new task...

I think primary attribute determines which accessory tile will be displayed in Home app. E.g. if you have a thermostat and an outlet services together in one accessory, whichever is...

It would be nice to allow accessories to expose their state and provide notifications on when this state changes so it can be persisted. I see that Accessory class implements...

Not sure how this has happened, python and python-dev are installed a few steps above in that Dockerfile (assuming you're using Dockerfile from step 2 on [the wiki](https://github.com/maximkulkin/esp-homekit-demo/wiki/Build-instructions-ESP8266-(Docker))).

It says "after restart". What restart? You're not supposed to reboot accessory right after pairing.

Disconnection after pair setup is a normal procedure. Controller then reconnects, goes through pair verification and then downloads accessory definition and shows what kind of services accessory provides on the...