Add sensor for user input and split activity

[murphy85]

It would be great to split the activity handling into two seperate sensors. One for motion detection and one for user input or activity.
This would help to implement functionality like "activate screen on motion and user input during day and only on user input at night". So if I stumble out of the bedroom, I will not be flashed by an activating display :-D

[dcapslock]

Hi, rather than splitting to a new sensor, would attributes of the sensor be sufficient. e.g. activityType which would be userInput or fullyMotion in the end chose fullyOnMotion to match the fully event which lends to other fully events definig activity in the future. This is much easier to implement and test and does not clutter up sensors for what is an edge case.

[murphy85]

I think this should be fine. So no breaking change and easier automations if you want to react to both types

[dcapslock]

Code written. Will submit PR and get a new 2.4.2 beta out for testing.

[dcapslock]

v2.4.3-beta.2 has been released which includes this feature. See release notes for more.

[esand]

I'd like to point out that the beta release notes mention fulyOnMotion and not fullyMotion. I didn't check the code to see which it actually is, but the spelling error of "fuly" caught my eye.

[dcapslock]

@esand thanks for pointing out the release notes error. I have updated now. The activityType is fullyOnMotion which means that Browser Mod has recieved the OnMotion fullyKiosk event. It may be that other fullyKios events trigger activity (none currently) in which case the activity type would be fully<fullyevent>. Let me know if you have any further queries.

[dcapslock]

v2.4.3 now released.