HS4 Feature Poll (Pick 5 features)

[macromark]

We need a little help prioritizing some already identified improvements and feature requests for upcoming HS4 releases. If possible, please take a moment and respond to this poll. Thanks in advance!

You may make multiple selections but please limit this to 5 selections. Note that the results will be public so others will see your choices.

Already logged issues

HS-228 Device Type Filter This existed in HS3... allows users to quickly view devices by type (like battery devices)
HS-271 Email Test Function Allows users to test email settings from the setup page instead of having to create an event to do this
HS-366 Add camera snapshot email notification Netcam plugin does this but would be nice to have that in HS4 natively
HS-397 Add "On Startup" and "On Shutdown" Triggers Allows users to run events automatically when the system starts up or shuts down. This would be much easier than messing with scripts
HS-436 Add log filter indicator to alert that filter is set Allows users to know at a glance that a filter has been set
HS-467 Add cancel function to event editing Allows users to cancel edits to any part of an event without saving the changes.
HS-472 Add feature to enable or disable camera Allows users to enable or disable cameras. This would be good to add as an event action and also a setting on the camera page.
HS-474 Add notification icon for available update Allows users to see at a glance when HS4 updates are available
HS-528 Event Action to enable or disable events Allows users to enable or disable events based on any trigger/condition combination. Would be very powerful
HS-587 Display a list of associated events for a device Allows users to see all events that a device is included in.
HS-598 Automatically disable auto-update when scrolling log Prevents log from updating when users are scrolling it
HS-612 Filter event list based on Device Would allow users to select a device on the event page and then just see a list of events that use that device in some way
HS-676 Rename existing timers and counters Allows users to rename timers and counters. At present, only option is to delete and re-add if you need to rename.
HS-1227 Ability to create multiple features for virtual devices Allows users to create multiple features (child devices) for a single virtual device
HS-1337 Allow multiple log type or from filters Allows users to select multiple entry types or from values in a single filtered search
HS-1358 Allow drag and drop to event actions and triggers Allows users to reorder event components with a drag/drop operation
HS-1524 Individual Camera Page GUI improvements Moves all camera buttons to ONE row and lines up right and left buttons with the edge of the camera image
HS-1525 Add record button to "ALL" camera page Allows uses to initiate recording without the need to click into the individual camera page
HS-1618 Energy Graph Improvements for a more modern energy graph
HS-1683 Conditional Actions Allows users to apply conditions specifically to event actions. this would allow more granular control of action and would reduce the need to create multiple events with the same trigger/condition combinations
HS-1739 Add Event trigger for log entry type Allows users to launch events when log entries match a specific type

If you have additional features you'd like to see, please add those to the comments below.

Thanks!

[macromark]

Please limit responses to 5 choices!!! If you choose more than that, it makes the data a lot less helpful.

[randy]

There are more than 5 good ones.

We need a replacement for the functionality of the Node Information page. Ability to see a list of all Z-Wave devices, their affiliated controllers, routing and polling info is something I go to when diagnosing Z-Wave issues.

[randy]

Please limit responses to 5 choices!!! If you choose more than that, it make the data a lot less helpful.

There are 2 respondents and 10 votes. Seems like it is working.

[rmasonjr]

Please continue with the Plugin-SDK outstanding items and we REALLY need better example applications and finished documentation.

[macromark]

There are more than 5 good ones.

We need a replacement for the functionality of the Node Information page. Ability to see a list of all Z-Wave devices, their affiliated controllers, routing and polling info is something I go to when diagnosing Z-Wave issues.

The poll includes HS4-specific issues. I may do the same for plugin-specific issue later on.

[ksum]

These two are very similar in the end result of being able to know which Events use a given a Device. As a result, I would suggest focusing on one and dropping the one which has the least # of votes from the top 5:

• Display a list of associated events for a device
• Filter event list based on Device

Even if, from a programming end, the same code is referenced for both, I would still drop one of them from the end results.

[randy]

These two are very similar in the end result of being able to know which Events use a given a Device. As a result, I would suggest focusing on one and dropping the one which has the least # of votes from the top 5:

• Display a list of associated events for a device
• Filter event list based on Device

Even if, from a programming end, the same code is referenced for both, I would still drop one of them from the end results.

Or like HS3, accomplish both with the device filtering drop down.

[TC1]

These two are very similar in the end result of being able to know which Events use a given a Device. As a result, I would suggest focusing on one and dropping the one which has the least # of votes from the top 5:

• Display a list of associated events for a device
• Filter event list based on Device

Even if, from a programming end, the same code is referenced for both, I would still drop one of them from the end results.

I agree 100%, both of these proposed features accomplish the same thing in the end and by splitting the vote across two of them that will push a more valuable feature down the list.

[Bob_Linux_User]

It would also be nice to be able to disable an event action within an event. I have events with numerous actions and some are needed during summer and some during winter. Instead of multiple events or deleting actions, a disable/enable would be great.

Bob

[mrceolla]

I've been waiting to push for this again once HS4 was more mature and you all hopefully had time for something like this.

Please improve Google Home/Assistant integration. I see two potential improvement areas.

1) Remember your first integration with Google Assistant and HomeSeer where you had to say "Hey Google, ask HomeSeer" followed by a command? That should be brought back. The ability to send the spoken text to HomeSeer is powerful. This would allow Google users to be able to make use of Jon00's excellent Echo Skill Helper, or simply let HomeSeer's native speech parsing engine do the work. I believe HST communicated that they needed to ditch the "ask HomeSeer" method in order to make room for the Google Home smart device integration. I was in a long back and forth with Google developer support about this and they told me there is no reason HST couldn't use both of these integrations at the same time. Frustrated by my inability to do with Google what others were able to do with Alexa (direct device control + "ask Homeseer"), I rolled my own solution, but I'd love to see this available for everyone.

2) I understand Google now has a Local Home SDK for local fulfillment. I'm not 100% sure what this is or if HomeSeer can leverage it, but if so this is perfectly inline with HomeSeer's strength's of not needing the clound to function. Additionally, this would allow for much speedier response times. I often experience varying amounts of latency when giving commands to my smart speakers and displays. This Local Home SDK may also allow for something like "ask HomeSeer" functionality so it could kill two birds with one stone.

I hope these can be considered. If not now, I'll revive my old threads in the Google Home sub-forum another day for another attempt.

I haven't been clamoring for anything in that list above, but I will pick my 5 favorite anyway. The two items I wrote about above would be in that 5 if available.

Thank you for reaching out to us to help guide prioritization!

[macromark]

I agree 100%, both of these proposed features accomplish the same thing in the end and by splitting the vote across two of them that will push a more valuable feature down the list.

Fair enough. Removed the "filter list..." option.

It would also be nice to be able to disable an event action within an event. I have events with numerous actions and some are needed during summer and some during winter. Instead of multiple events or deleting actions, a disable/enable would be great.

Bob

Conditional actions will accomplish what you want Bob!

[rjh]

The V4 plugin has the node info page, what is missing from it? It should have all the same information.

There are more than 5 good ones.

We need a replacement for the functionality of the Node Information page. Ability to see a list of all Z-Wave devices, their affiliated controllers, routing and polling info is something I go to when diagnosing Z-Wave issues.

[rjh]

If you enter a device name in the search box (or partial device name) (from the top bar) it will display the device and all events that use that device. I think that does what this issue is addressing. It even tells you if the device is used as a trigger or an action and clicking the link brings up the event in edit mode.

These two are very similar in the end result of being able to know which Events use a given a Device. As a result, I would suggest focusing on one and dropping the one which has the least # of votes from the top 5:

• Display a list of associated events for a device
• Filter event list based on Device

Even if, from a programming end, the same code is referenced for both, I would still drop one of them from the end results.

[rjh]

A couple of things to note here. The "Tell HomeSeer" skill still available with Amazon. Look for the skill named "HomeSeer Home Automation Skill". This simply sends the raw text that was heard to HS. You can do whatever you want with the text including parsing it yourself with a script. I can check if we can do this with Google. Amazon devices are so cheap and work well that why not use one of those? I have both in my home but use the Echo devices more often.

We can look more into #2, I have not looked into that yet. However, you can use the mic icon in HSMobile to give voice commands and that does not use the cloud, its all local. Same with the HSTouch client app.

I've been waiting to push for this again once HS4 was more mature and you all hopefully had time for something like this.

Please improve Google Home/Assistant integration. I see two potential improvement areas.

1) Remember your first integration with Google Assistant and HomeSeer where you had to say "Hey Google, ask HomeSeer" followed by a command? That should be brought back. The ability to send the spoken text to HomeSeer is powerful. This would allow Google users to be able to make use of Jon00's excellent Echo Skill Helper, or simply let HomeSeer's native speech parsing engine do the work. I believe HST communicated that they needed to ditch the "ask HomeSeer" method in order to make room for the Google Home smart device integration. I was in a long back and forth with Google developer support about this and they told me there is no reason HST couldn't use both of these integrations at the same time. Frustrated by my inability to do with Google what others were able to do with Alexa (direct device control + "ask Homeseer"), I rolled my own solution, but I'd love to see this available for everyone.

2) I understand Google now has a Local Home SDK for local fulfillment. I'm not 100% sure what this is or if HomeSeer can leverage it, but if so this is perfectly inline with HomeSeer's strength's of not needing the clound to function. Additionally, this would allow for much speedier response times. I often experience varying amounts of latency when giving commands to my smart speakers and displays. This Local Home SDK may also allow for something like "ask HomeSeer" functionality so it could kill two birds with one stone.

I hope these can be considered. If not now, I'll revive my old threads in the Google Home sub-forum another day for another attempt.

I haven't been clamoring for anything in that list above, but I will pick my 5 favorite anyway. The two items I wrote about above would be in that 5 if available.

Thank you for reaching out to us to help guide prioritization!