Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

last_activity und last_activity_age hinzugefügt #169

Closed
wants to merge 2,680 commits into from
Closed

last_activity und last_activity_age hinzugefügt #169

wants to merge 2,680 commits into from

Conversation

Ageman
Copy link

@Ageman Ageman commented Dec 3, 2016

regardless of the prev or current value, I need to know when the last update to an item value has been.
So I added "last_activity" next to "last_update".
last_update only changes in case the value changes
last_activity always changes independent of the current value.

walldi and others added 30 commits September 6, 2016 23:41
Ich merge das mal rein, immerhin sind wir auf dem DEV unterwegs und ich glaube keiner streitet ab, dass wir Blockly integriert möchten :)
ohinckel and others added 21 commits November 27, 2016 00:20
…items to

  initialize
# when setting to "yes" items will only be logged to database, but not initialized
# on startup
DB API2 support in SmartHome.py used in SQLite plugin

Hiermit gemerged um den PR einer breiteren Masse zum Testen zu geben.
Drexel und Weiss Plugin updated, made smart, added examples
Fix issue #82 - lock buffer while running dump/maintain
backend: polish translation & small fixes
squeezebox Plugin: smart plugin, fixed some issues with playlist mode updates
@Ageman Ageman closed this Dec 3, 2016
@Ageman Ageman reopened this Dec 3, 2016
@onkelandy
Copy link
Member

I guess this only refers to items, right? Any chance to expand this to logics?

@Ageman
Copy link
Author

Ageman commented Dec 5, 2016

Yes, this is items only. How would you want this with logics? When do you want last_activity to be set?

@onkelandy
Copy link
Member

whenever a logic gets triggered the last_activity would be set. Of course you can use a helper item that gets changes at the beginning of the logic.. and then execute the rest based on that item. But it would be much easer to get a logic.last_activity for that.

Reason is that I don't want to execute some logics or logic parts when it already just got triggered by a different item.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

10 participants