Eve history bug

[netRunner0]

I added a new sensor (temperature), it appeared in the homekit, but in the history of eve it is always empty. I checked if there is a history file, but it (the file) is not there)
Other sensors are present.
Homebridge reloaded.
How else to influence it?)

[ebaauw]

What type of sensor did you add? Can you list the output of ph get /sensors/xx for that sensor? See the Resource characteristic in Eve for the sensor ID. Is it a standalone temperature sensor, or does it also measure humidity? Can you post a screenshot of the sensor in Eve?

[netRunner0]

Xiaomi temperature sensor

[ebaauw]

The round temperature/humidity sensor? You need to set forceEveWeather in config.json, so homebridge-hue exposes a dummy pressure sensor for the accessory. Eve doesn't show history for a temperature/humidity sensor, only for a standalone temperature sensor, or for a combined temperature/humidity/pressure sensor (like the Eve Weather).

The history file should be there, though.

[netRunner0]

ebaauw Square sensor)

It’s not my first, but the only one for whom there is no history ...

[ebaauw]

The square one does temperature/humidity/pressure and should work. There's something else going on, maybe Xiaomi silently released a new model? Could you please attach the debug dump file (see https://github.com/ebaauw/homebridge-hue#debug-dump-file)?

Could you also please create a debug log file (see https://github.com/ebaauw/homebridge-hue#debug-log-file) and attach that? It should give some insight why the history file isn't created.

[netRunner0]

Just now I noticed that the sensor transmits a malfunction (inaccuracies in the measurement).

Could this be the reason?

[netRunner0]

The square one does temperature/humidity/pressure and should work. There's something else going on, maybe Xiaomi silently released a new model? Could you please attach the debug dump file (see https://github.com/ebaauw/homebridge-hue#debug-dump-file)?

Could you also please create a debug log file (see https://github.com/ebaauw/homebridge-hue#debug-log-file) and attach that? It should give some insight why the history file isn't created.

Ok

[netRunner0]

homebridge.log
homebridge-hue.json.gz

Problem sensor - "Multi Sensor noname"

[ebaauw]

I count 25 sensors and no lights. They raised the number of end devices supported by the RaspBee/ConBee to 32, but then they lowered it again - not sure what the limit is for firmware 0x26330500. You might run into the limit here.

Having said that, deCONZ is receiving updates from, Multi Sensor noname and homebridge-hue is receiving these. Also, homebridge-hue is creating history for the sensor:

[8/20/2019, 11:55:38 AM] [Hue] Multi Sensor noname: add history entry {"temp":28.7,"humidity":65,"pressure":989,"time":1566291338}

To confirm, there should be a history_00158d0002374fb8.json file in ~/.homebridge/accessories.

Most likely Eve is out of sync with the accessory and doesn't display the history entries, because it thinks they are from the future. If you have multiple iOS devices, can you check whether the history is also missing on those?

I think the best cause of action is to delete (uninstall) Eve (so it's local data is deleted) and re-install it. Your HomeKit configuration will be unaffected, but you will lose (layout) customisations made in Eve.

[netRunner0]

[netRunner0]

I deleted the empty file and restarted, now it works.

I think it would be nice to add a check that if there is evidence and the file is empty, overwrite the file) Since this error is not the first time

[ebaauw]

I’m glad it’s now working for you. I don’t think I’ve come across an empty history file before. I would expect homebridge-hue to re-initialise the history, just as when there’s no file, but apparently it doesn’t. I’ll have to look into that.

[tomky]

I encountered the same bug, which is surprising as the accessories with this issues are already online for months with no issues. One day these (but not all) accessories suddenly stopped reporting histories and I see those empty files in the folder. Removed and then it backs online, but the histories for months are lost. No clue what actually happened though.

[ebaauw]

What system are you running homebridge on? Did you check the file system?

[Phoenix-DH]

I will attach also my issue to this thread.
I have the Hue Motion sensor in place since more than a year without any problems.
When I have s look to the files in the accessories folder, everything seems to be fine.
Bit in the latest updated eve app there is no history available for those 2... means there is no arrow anymore to open zhe history.

[ebaauw]

Eve v3.8.1 is way more restrictive than previous version on when it will show history, see simont77/fakegato-history#76 (comment). The history for the following accessories no longer shows:

• Temperature sensor (without Humidity/Air Pressure, as for the Hue motion sensor with hueMotionTemperatureHistory set in config.json);
• Thermostat.

History for motion sensors, door sensors, and smart plugs should still show.

I think I know how to fix the thermostat; for the temperature sensor I need to do some more research.

[Phoenix-DH]

Yeah, that is exactly what I have 🤷🏼‍♂️
hueMotionTemperatureHistory Set to true.

So I will wait.
Thank you for your work.

[ebaauw]

v0.11.37 restores the history for the Temperature Sensor service (when you set forceEveWeather) and for the Thermostat service. See the release notes.

[Phoenix-DH]

Great! Tried and it is working fine. History is back. The dummy is not the problem. Maybe one remark or idea for the next releases:
Possibility to move the dummy to another room ... without moving the temp.

Thank you and have a nice weekend!

[ebaauw]

Possibility to move the dummy to another room ... without moving the temp.

That is technically impossible: they're both services of the same accessory. And they need to be, or Eve doesn't show the history.

[Phoenix-DH]

Okay, understood.

[tomky]

Thanks for the quick update. Will try it.
Just curious if you will continue test the Eve signature trick mentioned here?

simont77/fakegato-history#75 (comment)

This looks like a better solution if it works.

[ebaauw]

Yes, it does look better, although I still need to confirm that it works. Even then, It might take me some time to use this in homebridge-hue, hence this quick fix. I see no easy way to update fakegato-history to deal with different entries for motion detected vs periodic temperature updates. I might need to refactor homebridge-hue to use dynamic platform accessories (see #4), based on homebridge-lib. Before that, I want to be sure homebridge-lib does what I want it to do, so I'm rewriting my other plugins (with fewer users) first.

[tomky]

Understood. Then I got another issue about the CLIPSensors in this approach. I actually have some CLIPTemperature and CLIPHumidity sensors in pairs, treated as independent accessories. Is there a way to merge them as single multi sensors in deconz or Homebridge-hue? In this way I can get the humidity history and avoid the extra dummy humidity sensor.

[ebaauw]

Yes, MultiCLIP, see #164 (comment).

[ebaauw]

Just curious if you will continue test the Eve signature trick mentioned here?

v0.11.38 no longer uses dummy sensors, but a (mostly) hidden Eve Weather service.

[mtressl]

Just adding that I experienced the same issue as mentioned above:

• in Eve some of my sensors did not report the history (anymore)
• I checked ~/.homebridge/accessories and found matching 0 bytes (empty) files
• deleted all of them, restarted Homebridge, files were re-created, history values showing in Eve app

Maybe it really makes sense to implement something for the plugin to fix such issues.