gazoscalvertos / hass-persistence Goto Github PK

Recently awesome people in home assistant community have created a very useful tool to automate follow up on custom components https://github.com/custom-components/custom_updater

In order to make it work the maintainer of repo should add json file to repo for change tracking. Example:
https://raw.githubusercontent.com/keatontaylor/alexa_media_player/master/custom_components.json

Would be coll to have similar feature for the component. Thanks!

Hey,
Thanks for this component, it's something that HA really misses.
(at least i cant get restore_state to work)

I have enabled your component on several input_number entities,
After restart the values are retained but they no longer react as sliders.
There is no line to drag next to them, and in the states page, i get the name and state correct, but blank attributes.

Here is the sensor i have enabeld:

 - platform: persistence
    entities:
       - input_number.irrigation_routine_1_start_hour
       - input_number.irrigation_routine_1_zone_1_min
       - input_number.irrigation_routine_1_zone_2_min
       - input_number.irrigation_routine_1_zone_3_min
       - input_number.irrigation_routine_1_zone_4_min
       - input_number.irrigation_routine_1_zone_5_min

And sample of my input_number code:

  irrigation_routine_1_zone_1_min:
    name: Zone 1 Timer
    initial: 0
    min: 0
    max: 20
    step: 1
    unit_of_measurement: m
    mode: slider
    icon: mdi:timer
    

ANy ideas?
Thanks in advance

After implementing hass-persistence I continuously get errors like the one below:

Sun May 20 2018 07:26:55 GMT+0200 (W. Europe Daylight Time)

Error doing job: Future exception was never retrieved

Traceback (most recent call last):
  File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/pi/.homeassistant/custom_components/sensor/persistence.py", line 99, in state_change_listener
    self._persistence_list[event.data['entity_id']] = event.data.get('new_state', None).state
TypeError: list indices must be integers or slices, not str

Running Home-assistant 0.69.0

Relevant configurtation.yaml:

sensor:
  - platform: persistence
    entities: #ADD ALL OF YOUR ENTITIES HERE
      - counter.doorbell_counter
      - counter.dryer_counter
      - counter.frankaway_counter
      - counter.jetaway
      - counter.toilet_counter
      - counter.washmachine_counter
      - light.badkamer_lamp
      - light.badkamer_spiegel
      - light.bank_licht
      - light.eettafel
      - light.gang
      - light.gang_boven
      - light.gang_zolder
      - light.keuken
      - light.kledingkamer
      - light.lieke_grote_lamp
      - light.lieke_kleine_lamp
      - light.rommelhok
      - light.schuur_binnenverlichting
      - light.schuur_buitenverlichting
      - light.slaapkamer_frank_en_jet
      - light.toilet
      - light.tv_licht
      - light.wasmachinehok
      - light.werkkamer_lamp
      - light.werkkamer_spots
      - light.yeelight_rgb_7811dc6ba370
      - sensor.boiler_mean
      - sensor.boilerdaily_mean
      - sensor.dryer_mean
      - sensor.dryerdaily_mean
      - sensor.gas_consumption
      - sensor.hourly_gas_consumption
      - sensor.mqttdailykwhboiler
      - sensor.mqttdailykwhdryer
      - sensor.mqttdailykwhtotal
      - sensor.mqttdailykwhtv
      - sensor.mqttdailykwhwashing_machine
      - sensor.mqtthourlykwhboiler
      - sensor.mqtthourlykwhdryer
      - sensor.mqtthourlykwhtotal
      - sensor.mqtthourlykwhtv
      - sensor.mqtthourlykwhwashing_machine
      - sensor.total_mean
      - sensor.totaldaily_mean
      - sensor.tv_mean
      - sensor.tvdaily_mean
      - sensor.washing_machine_mean
      - sensor.washing_machinedaily_mean

Testing this interesting plugin, it appears to break Friendly name of input booleans.

One of my booleans "input_boolean.night" shows up on the Home dash as "night" after a restart using persistence, instead of with its friendly name "Night mode".

As the structure of the custom components has changed since HA version 0.92 the component needs some refactoring.
Thanks

I'm still learning Python and HASS. Tried your persistence sensor (thank you). Have some suggestions based on errors I saw. There are timing issues because multiple threads are running, so don't know if this is comprehensive or not or if the solutions are proper....

1. declare self._persistence_list as a dictionary vs. list.
2. limit the restoration of a state to just the state value otherwise the whole state (like icon, friendly name) is cleared. Replace self._hass.states.set(key,val) with
   state_temp = self._hass.states.get(key);
   self._hass.states.set(key,val,state_temp.attributes)
3. I've had timing issues where the initial state of an entity is saved before the persistence_load has had a chance to run, thus overwriting the "persisted" values with the initial values. I changed the first line of persistence_save to check if self._initialised has completed otherwise the update is ignored-- if self._persistence_list is not None and self._initialised

Thanks again for this effort.

First off, thank you so much for this! Been highly annoyed that my alarm will revert to disarmed on a reboot. Found a bug though. Whenever I enable this, it prevents me from being able to arm/disarm the alarm. As soon as I comment out the sensor, I'm able to set the alarm again. Not sure what's causing this. It also goes from "Home Alarm" to "home alarm" on my home screen.

With persistence sensor enabled:

Without persistence sensor enabled: