X10 Community Forum
📱X10 WIFI => 🧾Wish list => Topic started by: Tuicemen on January 16, 2018, 07:26:24 PM
-
Currently the scenes option in the x10WIFI app are simple macros (maybe to simple for most of use experienced AHP users)
Most of us want to ditch running a PC 24/7 the WM100 has the potential for this.
The available memory is apparently there so lets use it. ;)
-
Currently the scenes option in the x10WIFI app are simple macros (maybe to simple for most of use experienced AHP users)
I've found my Wink and MyQ Garage along with the iPhone stuff.... to be really simplified. The CM15A was/is a real spoiler.... especially with AHP and a PC.
-
There are so many possibilities for improving (expanding) Scenes I think this needs to be broken down so things can slowly get added other wise this wish would always stay unfulfilled.
-
There are so many possibilities for improving (expanding) Scenes I think this needs to be broken down so things can slowly get added other wise this wish would always stay unfulfilled.
Agreed. Improved scenes would probably be at least 4 of the top 5 items on my wish list. ;) My suggestion is that we use this thread to brainstorm ideas and then break the top ones out into separate threads.
-
There are so many possibilities for improving (expanding) Scenes I think this needs to be broken down so things can slowly get added other wise this wish would always stay unfulfilled.
Agreed. Improved scenes would probably be at least 4 of the top 5 items on my wish list. ;) My suggestion is that we use this thread to brainstorm ideas and then break the top ones out into separate threads.
I like that idea :)%
-
If a "listener" (the unit/app already has X10 sensing/detection) was added so we can create X10 generated "triggers" we'd be halfway towards creating macros (short of ITTT and/or conditions).
Plus... don't forget... the Alexa also offers a tiny bit of programing. [Amazons settings are] NOTHING... compared to what AHP users are accustomed to. But I expect the code writers for Amazon to get imaginative as the user base grows.
-
The unit does see All x10 PLC this was one thing early versions didn't and thus required a hardware rebuild. That was require for it to be a polite transciever.
The question realy is how much onboard memory this truely has.
I asked for specs but not recieved them yet from the manufacture.
-
......The question realy is how much onboard memory this truely has.
I asked for specs but not recieved them yet from the manufacture.
The AHP only has.. what... 256kb of memory? How much memory does it really need.... and memory is dirt cheap now-a-days.
-
I'm not sure what this has or how it is designated.
We may only be using 1/3 of what is actualy in it.
A flash able ram may have required a good bit set aside for use. The Cm15 didn't have that.
We'll know more once( if ) I get a full specs report from the manufacture. ;)
-
I had put forth the option for a web requests to be added to a scene when in testing.
Which like many of my suggestions failed to materialize :( That doesn't mean they were rejected (at least I hope not) just the push was on to get a release done.
I figured if we knew the protocol expected by the other device geting the web request it would put this Hub ahead of many others.
One example of a web request would be to turn an IP camera to a specific location and or take a snapshot. (Airsights will do this from a web request)
We might even be able to trigger things on other hubs. ::) :'
The trick would be finding out what was expected in a web request but users could post their successful web request strings.
-
I think the important thing is that I downloaded the app, plugged it in, and it WORKED! And it transmits a much stronger signal than prior X10 controllers. Additional features can evolve over time, just like they did with some of my XTB products.
Jeff
-
And it transmits a much stronger signal than prior X10 controllers.
I think that's key - it will go a long way to rebut long time criticism of the X10 PLC system. If they release the protocol and provide pass-through and feedback functions, the memory and programming issues are easily solved with things like...
https://www.amazon.com/Lenovo-Touchscreen-Quad-core-Processor-Bluetooth/dp/B01MAU8TS2/ref=sr_1_5?ie=UTF8&qid=1516484009&sr=8-5&keywords=10+inch+windows+tablet (https://www.amazon.com/Lenovo-Touchscreen-Quad-core-Processor-Bluetooth/dp/B01MAU8TS2/ref=sr_1_5?ie=UTF8&qid=1516484009&sr=8-5&keywords=10+inch+windows+tablet)
-
I agree, I don't and nor should anyone else expect any suggestions put forth will happen over night.
This device is rock solid!
Many suggestions here may not get added to this unit they may result in a Pro version creation instead.
There are key suggestion put forth in this section that will solve many users demands as dhouston stated.
-
This device is rock solid!
....
And don't forget... once this is Alexa controlled there are simple little macro-like controls built into the Amazon app. Mixing and matching products and control abilities is a technology multiplier.
I went through my X10 macros today... deleted some, edited some other things. Pulled the laptop off-line. Still have a CM15A plugged into the outlet (with all remaining macros save to the CM15A). I still have some timers I want to convert to the WM100. I am making progress.
-
There are so many possibilities for improving (expanding) Scenes I think this needs to be broken down so things can slowly get added other wise this wish would always stay unfulfilled.
Agreed. Improved scenes would probably be at least 4 of the top 5 items on my wish list. ;) My suggestion is that we use this thread to brainstorm ideas and then break the top ones out into separate threads.
I like that idea :)%
Also, can we use standard, clear questions for the polls? My suggestion is to use the following:
- Very Important (I want it ASAP)
- Useful (I will want it one day)
- Neutral (I might use it)
- Not very useful (I probably won't use it)
- Unnecessary (I would never use it)
By using the same questions, it will be easier to compare the results. Also by making the questions clear, the results will be more consistent. People are also accustomed to ranking priorities.
-
We can request user post their polls with standard answers. That doesn't mean anyone will follow the suggestion.
Also the more options the more confusing it becomes less options are better.
eg:
1: Yes (very important to me)
2: Maybe (I may or may not use it)
3: No (I'd never use it)
-
We can request user post their polls with standard answers. That doesn't mean anyone will follow the suggestion.
But no one will follow any standard if we don't suggest it in the "don't post before you read" thread. Also, as admin, can you not change the questions in a poll?
Also the more options the more confusing it becomes less options are better.
eg:
1: Yes (very important to me)
2: Maybe (I may or may not use it)
3: No (I'd never use it)
I agree that too many options makes it more confusion, but too few removes the granularity from the features that are urgent from those that would be nice to have but can wait a bit (if everyone answers yes to everything they want, how will the developers know which features are most important?). Personally I think 5 questions is a good compromise between the two, but will deffer to your decision.
-
Well the maybe could be worded:
Maybe (I'm not in a rush for it)
-
Why not use a scale, ex: "How important is 'Feature X' to you?"
1. Very important
2. Somewhat important
3. Neutral
4. Mostly unimportant
5. Not important at all
That way, you could look at what is most important to the largest number of people - and those would be the ones they should focus on first.
-
That works too. However my experience shows only the Important features would get looked at.
Even if all those were added the somewhat important or maybe features would only get added if the developer was motivated enough. :(
3,4 and 5 would be the same as far as a suggestion getting consideration.
-
Why not use a scale, ex: "How important is 'Feature X' to you?"
1. Very important
2. Somewhat important
3. Neutral
4. Mostly unimportant
5. Not important at all
That way, you could look at what is most important to the largest number of people - and those would be the ones they should focus on first.
Isn't that similar to what I said originally?
-
Why not use a scale, ex: "How important is 'Feature X' to you?"
1. Very important
2. Somewhat important
3. Neutral
4. Mostly unimportant
5. Not important at all
That way, you could look at what is most important to the largest number of people - and those would be the ones they should focus on first.
Isn't that similar to what I said originally?
Remarkably, yes. Somehow, I had missed your comment when reading through the thread. But we are certainly thinking along the same lines. :-)
-
That works too. However my experience shows only the Important features would get looked at.
Even if all those were added the somewhat important or maybe features would only get added if the developer was motivated enough. :(
3,4 and 5 would be the same as far as a suggestion getting consideration.
True, but different features will be important for different people. If most people say a feature not important, it may not be implemented, but that is to be expected. The alternative is if we say every feature is equally important, we also may not get some of the critical ones if they are difficult to implement.
This gives us a way of ranking how important each feature is (if standardized, it is easy to calculate which features are the most important) so that they can compare that to how difficult it is to implement.
-
How a user puts forth their selectable options for a poll is up to the individual.
As well how a user votes is up to the indivdual they need not explain how or why they voted the way they did.
The main thing is that users are contributing.
I don't expect Authinx to push for any one of these suggestions until the Wifi unit has been in the public hands for at least a month (maybe longer).
-
....different features will be important for different people. If most people say a feature not important, it may not be implemented....
I've never seen a product designer (and I've known a few) that couldn't easily discard any poll or questionnaire about the "customers" desires. After all.... isn't the product designer the expert? :'
It's important that we give our heartfelt honest, feedback... I am with you on that guys. But our own emotional investment doesn't qualify as meaningful to the "value" of the product. After all.... we don't represent the vast majority of X10 users.
-
Also, can we use standard, clear questions for the polls? My suggestion is to use the following:
- Very Important (I want it ASAP)
- Useful (I will want it one day)
- Neutral (I might use it)
- Not very useful (I probably won't use it)
- Unnecessary (I would never use it)
By using the same questions, it will be easier to compare the results. Also by making the questions clear, the results will be more consistent. People are also accustomed to ranking priorities.
This is an awesome idea. I have changed my polls to reflect the improvement.
-
I've never seen a product designer (and I've known a few) that couldn't easily discard any poll or questionnaire about the "customers" desires.
I have met designers like that, but I have also met many good designers who try to give the customer what they want.
After all.... isn't the product designer the expert?
Usually not. They are the expert when it comes in terms of how to design things, but to them, requirements come from a document. If it isn't in the document, it isn't necessary. Now the requirements can be modified but that usually costs extra.
Specifying requirements is expectantly true when dealing with China. A combination of culture and time zone differences mean that if something isn't clear, they won't ask questions but instead will take a guess (asking questions is an embarrassment) and they probably won't tell you they did so. As a result it is important to specify things extremely accurately.
-
After all.... isn't the product designer the expert?
Usually not.
That's for sure! Look what they did to Microsoft Word!
I still use Word 2000 because the newer versions think they know better and screw up what I'm trying to do.
Jeff
-
May I suggest a first baby step to improve scenes. Add timers. This would make programming simpler as you could turn on a whole room with one timer. Also would allow repeats. Two improvements for the price of one.