Interesting. I don’t have an Eve Degree device, though I have vague feelings a friend has an Eve Degree that is slow to update (even in iOS).
Not sure what we can do here - your debugging is flawless and there is nothing else I can think to suggest. The big difference between iOS and HA is that a real iOS device wouldn’t poll once a minute to conserve power, it would rely on events a lot lot more. So it doesn’t surprise me that the Extend is returning cached values. And at least with my Eve devices (like the Eve Energy) events are delivered and processed within a second.
The format of PAIRINGDATAFILE is broadly compatible with whats in .storage/core.config_entires… you should have something like this:
{
"version": 1,
"key": "core.config_entries",
"data": {
"entries": [
{
"entry_id": "sdfsdfsd",
"version": 1,
"domain": "homekit_controller",
"title": "Philips hue",
"data": {
"AccessoryIP": "192.168.1.1",
"AccessoryLTPK": "asdasdasdasd",
"AccessoryPairingID": "AA:BB:CC:DD:EE:FF",
"AccessoryPort": 8080,
"Connection": "IP",
"iOSDeviceLTPK": "asdasdasd",
"iOSDeviceLTSK": "asdasdasd",
"iOSPairingId": "1-2-3-4-5"
},
"options": {},
"system_options": {
"disable_new_entities": false
},
"source": "user",
"connection_class": "local_poll",
"unique_id": "aa:bb:cc:dd:ee:ff"
},
Ths stuff inside data is as it should appear in a PAIRINGDATAFILE. If memory serves its something like:
{
"myeve": {
"AccessoryIP": "192.168.1.1",
"AccessoryLTPK": "asdasdasdasd",
"AccessoryPairingID": "AA:BB:CC:DD:EE:FF",
"AccessoryPort": 8080,
"Connection": "IP",
"iOSDeviceLTPK": "asdasdasd",
"iOSDeviceLTSK": "asdasdasd",
"iOSPairingId": "1-2-3-4-5"
}
}
Hope that helps.
