Thanks for the reply and asking for input to help hopefully you shape the product to what the market might require.
My requirements are.......
1. Multiple temperature zone sensors that feedback to M1 to monitor and have M1 do things under rules. The house we are building I would see a total of 11.
4 for the bedrooms (air conditioning control using multi head split system where I have control at a room by room area are by area )
1 for a general open living area (Kitchen/lounge/dine/family)
1 for study
1 for patio (which would also provide my outside temperature input)
1 for pool temperature (inline with water intake or return)
1 for my AV closet to enable a ceiling fan to draw air
1 for my garage (Open panel lift door say 2 foot when temp is >than XX)
1 for roof space
I would prefer flush mount remote temperature sensors. The ones that would finish off almost invisible once inserted into plasterboard/wall board/gyprock. They would install flush and then you paint over them. These would be perfect.
Then a surface mount version for those areas outside or roof spaces that do not lend themselves for the flush mount type. These would be nice to be cosmetically pleasing unlike the TZS currently available (I am being constructive).
This would give you just two packages to cover what my case scenarios are.
Now to push the envelope a bit......Humidity
Humidity is a must for me givne the house is in the tropics of Far North Queensland. I have bought an Ocelot and a Bobcat Humidity sensors and an XSP just to give me some RH input into MI, where I can exercise air-conditioning remotely as we will not be there when the wet season is there. I have three humidity sensors in the design. I know there were a number of people putting there hands up in previous threads for humidity sensors. The compact surface mount housing I was suggesting above could serve as the housing for any future humidity sensor. I suspect you couldn't have a flush humidity sensor as it would require some air movement to detect the humidity.
I would also prefer to have the iButtons packaged as an ELK/Ness product rather than having to source and try and package them up for fitment. This would come at price above the iButton but I suspect would not be too much over the top. Unless of course your superannuation is lagging behind!! :huh:
Thinking Outside the Square
Thinking outside the square given you are about to release the RF RX TX solution (assuming those dam Aussie lift there game
) is it feasible to consider having some remote <30Metre -90feet temperature TX into the RX which is enrolled on M1? What I have seen before I think with some weather station manufacturers is a TX that floats in the pool and transmits back to RX. This would not need to be transmitted constantly therefore not putting too much traffic on the RS-485 control data bus. Once every 15 minutes for example would probably see 6 months or more out of some "AA" batteries in the TX. It would I suspect in most situations give the input required. A pools temp is not going to change too much over 15 minutes. This would also lend itself for spas, Jacuzzis etc.
Continuing on the RF theme I would have an application for monitoring two refrigerators/freezers more so when we are not there. A RF TX that is battery operated or DC plug pack that sits outside the fridge (possibly with fridge magnet) with a thin possibly flat cable to allow the iButton sensor to sit inside the fridge.
This would be handy for other applications like remote cool rooms, wine cellars and of course down here in Australia our eskies where it is extremely important to have the correct temperature beer!
What exactly do you mean when you say "The M1KAM Access Module takes the place of a keypad? It supports a 26 bit Weigand Prox Reader and the 1-Wire data bus. "???
Are you meaning from M1's perspective it treats the M1KAM as the same type as a keypad? How can it take the place of a keypad? Is it a module that connects to the 2 wire weigand on the KP? Sorry to be vague but important to understand the connectivity.
How many iButton sensor devices could be connected to the one M1KAM Access Module? Are you saying it is one iButton per M1KAM?
Is just a serial loop around of Cat5e from one sensor to the next then to the M1KAM?
By now you may have not regretted asking for input!
I think I can talk on behalf of other CocoonTech members in saying that it continues to be a refreshing experience with you and ELK’s continuum of asking the market what they would like to see. Before it is released to the market!
What finishes up on the market will be determined by what feedback you get from here, dealers, end users, engineering, what the competition might be doing and heavens forbid the Sales and Marketing department
Nice to have an opportunity to put our two cents worth in.