Can you create a Top Level Topic Called “Devices and Support”?
The idea is to have one thread for each device model. Then people could search topics to see if someone else is using or fixed issues with it. Then others could follow. It would also be a good place to see what works best and what doesn’t work at all.
Is that Possible?
I voted yes- I think it’s a GREAT idea.
in general I think things would be more organized and easier for people to find info (and less apt to ask the same things over again- I know I’m guilty) if their were more subforums to be more specific.
I also think pulling out network and router setup would be good to pull out of the setup and usage.
And the luup forum could use some help, but that’s a tougher one to come up with ideas how to break it up to be more usable.
One way to prove your model is to start a few threads like what you’re looking for, and see if you can get synergy/momentum behind them.
For example, in the AVS Forums, folks have a tendency to create threads like:
" Onkyo TX-NR807 Official Thread"
(there are various other forms). Once you have enough of these, and have proven the model, then you’ll have weight for a special “breakout” category.
An alternative model might be to create “per Product/Device” Wiki pages on http://wiki.micasaverde.com, similar to how we’ve been doing for each Custom Plugin.
We can all get accounts there (it’s self-service as a number have found out) and simply create a “template” of what the Product page should look like (including Bugs, Gotcha’s etc)
In some respects that might be a better model than what’s there currently (where we try to squish instructions into a tiny table cell) or using a Forum (which tends to be more about “history” than “current” information.
Just my 2c
I think it would be great to see more device specific threads. Do you think the Wiki might be better suited for this? I agree with @guessed, it seems like its built for that type of documentation.
One user did point me to a decent article there, http://wiki.micasaverde.com/index.php/Wayne-Dalton_WDHA-12
I think your right. A wiki would be better for step by step and proven troubleshooting tips, but we still need a place to converse to work out implementation issues and solutions.
The forums are great for that and a direct link from the wiki to the device specific forum would allow for questions on items or issues not covered in the wiki.
Of course when a new solution is worked out, the wiki should be updated.
Continuing this topic, If we could add a navigation item “Devices” which links to a bulleted list of Device Type → Device which contains a link to the device specific wiki page. I would be happy to manage this.
Example:
Navigation Menu → Devices → Devices Wiki
Door Locks
[table]
[tr][td]Device[/td][td]Cost[/td][td]Rating (5)[/td][td]Compatibility[/td][td]Recommended[/td][/tr]
[tr][td]- Kwikset Smartcode Deadbolt[/td][td]$$[/td][td]4[/td][td]Full[/td][td]X[/td][/tr]
[tr][td]- Schlage LiNK[/td][td]$$$[/td][td]4[/td][td]Full[/td][td][/td][/tr]
[tr][td]- Acme Locks[/td][td]$[/td][td]1[/td][td]Limited[/td][td][/td][/tr]
[/table]
Thermostats
[table]
[tr][td]Device[/td][td]Cost[/td][td]Rating (5)[/td][td]Compatibility[/td][td]Recommended[/td][/tr]
[tr][td]- Wayne Walton [/td][td]$$[/td][td]4[/td][td]Full[/td][td]X[/td][/tr]
[tr][td]- Trane[/td][td]$[/td][td]1[/td][td]Limited[/td][td][/td][/tr]
[/table]
I think you’ll need to leave out the recommendation, cost and so forth. In some cases, these will be subjective and the market will determine the price.
For certain “types” of devices, it would be more useful to have the feature matrix. These can be quantified. In the case of thermostats, for example, some of the models have more features than others (built-in 5/2 schedule for autonomy), some have less features “supported” than others. These things are going to be safe to talk about, since it’s factual based upon documented specs, or current [Vera] support levels.
When I’m buying something, I make these comparison matrices. Price plays a factor, but I want to know why it’s cheaper… what am I trading off to make it that way.
… in some cases, that tradeoff is a power supply, a plastic box and some marketing. In other cases, the differences are more substantial.
The existing “Supported Devices” Wiki pages could be converted into these feature matrices, once the “Details” Wiki pages are built for each Device and these contain the current information… and a lot more.
btw, the Wayne Daltons are cheaper than the Trane’s… The Trane’s have more features. You and I might likely recommend differently here.
This all sounds fine to me. I wasn’t using anything factual for the example. Train does do a lot more. I’m playing with the Wiki right now.
Based on our conversation I have created a Wiki page (at least started one.) I added devices that were about the single device.
Can we add a link from the left navigation menu to this page?
[url=http://wiki.micasaverde.com/index.php/Z-Wave_Devices]http://wiki.micasaverde.com/index.php/Z-Wave_Devices[/url]
THANKS!
ok, so some comments. I was thinking this model would be a replacement for the tables we have here:
http://wiki.micasaverde.com/index.php/ZWave_Add_Controller
http://wiki.micasaverde.com/index.php/Supported_Hardware
http://wiki.micasaverde.com/index.php/Serial_Supported_Hardware
(etc). These tables would transform to be more “feature comparisons” (including a “Working Yes/No” column), and each row would be a pointer out to a separate Web/Wiki page on the product (with some sort of standard template for what information is presented)
Right now, these tables are a mashup of the product, along with some notes and install instructions.
Basically, they’re way too busy…
Aynhow, these notes/install stuff, along with most of the other columns (who added it, etc) would move out to the detail pages, leaving room for a “pure” feature comparison and the “is it working” flag (or a Vera Version# it works in)
Thoughts?
If we can agree on the template for these product pages, I’m more than happy to build the pages for the devices I own (mostly Leviton stuff). I’d imagine that, with a starter template, others might do the same for their components - most folks here are willing to chip in.
@guessed, I agree. I’m happy to help and I also run mostly Leviton devices… 
@Roger.NET, there are more classes of devices - eventually we would need to split in-wall scene/zone controllers from battery operated handheld primary/secondary controllers etc.
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules