Top listed topics sorted only on priority index
As described on the first page we decided to first sort on the amount of votes and then on the priority index. Without sorting the votes first a subject with only 10 votes could come in a top 10 with a priority index of 4.5 whilst a subject with a priority index of 4.4 with 30 votes probably couldn’t. If we leave out the votes count sorting the top listed topics will be as follow:
Top 10 of desired new features (based on only priority index)
Based on above intepretation these are the 10 most desired new features:
P | Subject | Priority index | Votes | Percentage voted |
---|---|---|---|---|
1 | [Devices] Change WiFi credentials for device within the app for all devices | 4.52 | 31 | 100% |
2 | [App others] eWeLink web supporting same feature set as app | 4.23 | 26 | 83.9% |
3 | [Scenes] Use device more than once in a scene on both trigger and action | 4.19 | 31 | 100% |
4 | [Devices] Ability to enable/disable each individual RF alarm | 4.18 | 22 | 71% |
5 | [App others] Ability to setup an own server | 4.04 | 28 | 90.3% |
6 | [Devices] Temperatures of monitoring devices on start screen of app | 4.03 | 29 | 93.5% |
7 | [Scenes] Scene action: toggle power state of device (between on and off) | 4.00 | 29 | 93.5% |
8 | [Devices] Detect main power failure | 3.97 | 30 | 96.8% |
9 | [Native app on:] Windows | 3.96 | 28 | 90.3% |
10 | [App others] Status website which automatically shows status and outages | 3.90 | 29 | 93.5% |
Some of the topics from the extended sorting did come back in the simple sorting. The absolute number one is Change WiFi credentials for device within the app for all devices. Also Use device more than once in a scene on both trigger and action, Detect main power failure, Temperatures of monitoring devices on start screen of app, Scene action: toggle power state of device (between on and off), Status website which automatically shows status and outages did come back in this simple sorted list.
eWeLink web supporting same feature set as app didn’t make it to the extended sorting top list but have been greatly demanded on social media. Since eWeLink Web has been released with only a few on/off devices supported it never have been updated.
The Ability to enable/disable each individual RF alarm would greatly improve the ability to use a RF hub with its connected RF alarm as a simple home alarm.
Quite some users on social media demanded the Ability to setup an own server to overcome frustrating central server outages that didn’t get resolved fast. Users also hope to find an easier solution in this than configuring an own Home Assistant setup.
A surprising one is the Native app on Windows. We as maintainers of the eWeLink community website thought people would give the most priority to the much requested Apple watchOS or Android WearOS apps but it turns out people demand a native Windows application even more. Possibly due the fact that eWeLink Web hasn’t developed further since its start.
A Status website which automatically shows status and outages can be a handy troubleshooter for people. Especially when a group of users seems to have the same issues on the same moment. A status website reporting the server and feature statusses and displaying the progress of resolving issues maybe partly prevents sending unnecessary feedback to eWeLink and unnecessary messages on social media.
Top 6 of bugs that needs to be fixed urgently (based on only priority index)
We only had 6 bugs on our survey this time and so all bugs are listed in the table below:
P | Subject | Priority index | Votes | Percentage voted |
---|---|---|---|---|
1 | [Devices] LAN mode not working as it pretent it should be | 4.25 | 24 | 77.4% |
2 | [App others] Not having a clear indication of which RF device fires an alarm | 4.00 | 21 | 67.7% |
3 | [Devices] Zigbee devices loosing their names all the time | 3.94 | 17 | 54.8% |
4 | [Time] Unable to choose a date at the scheduler | 3.65 | 17 | 54.8% |
5 | [App others] Unable to reorder devices in lower part of the reorder screen | 3.62 | 21 | 67.7% |
6 | [Scenes] Not being able to set brightness of a light in a scene | 3.23 | 22 | 71% |
Only the number one stays on its place. All others get mixed in the order. Go to page 3 (Top 6 of bugs that needs to be fixed urgently (with votes count taken into account)) to see an explanation of each item in the list.