iPhone 2nd Generation app 1.1

[slychiu]

Version 1.1 of the iPhone app has been published

The changes are

1. When the app is first installed, a default profile is created. Without any profile, the app will crash when you tap on the email attachment with the converted JRLCCIP file and select \"Open in Comfort\"
2. The slider on the Control menu mapped to Counter feedback is now working. The position of the slider sends the value 0 to 255 to the mapped counter, and any change in the counter value in Comfort also updates the position of the slider. This feature also requires Comfort firmware 7.067 (currently beta see http://www.comfortforums.com/forum79/4045.html )
   

[Howser]

[user=1]slychiu[/user] wrote:

1. The slider on the Control menu mapped to Counter feedback is now working. The position of the slider sends the value 0 to 255 to the mapped counter, and any change in the counter value in Comfort also updates the position of the slider. This feature also requires Comfort firmware 7.067 (currently beta see http://www.comfortforums.com/forum79/4045.html )

Any chance of expressing the values in percentages?

[CytechMartin]

No, 255 means 100%, 0 means 0%

[Howser]

[user=5285]CytechMartin[/user] wrote:

No, 255 means 100%, 0 means 0%

I know that. It might make more sense for end users, especially for dimming and the likes.

Just a thought.

[slychiu]

 There are some systems like Zwave where the counter values are 0 to 99 for dimming levels and 255 for on
Expressing the values as % in this case would be misleading as 99 would be only 40%

I think seeing the slider position should give a good indication of the percentage of full scale

[Howser]

[user=1]slychiu[/user] wrote:

 There are some systems like Zwave where the counter values are 0 to 99 for dimming levels and 255 for on
Expressing the values as % in this case would be misleading as 99 would be only 40%

I think seeing the slider position should give a good indication of the percentage of full scale

I was thinking of Clipsal who converts the HEX value into percentage. PICED does this quite well (and provides a formula as well). Expressing the converted value (instead of the actual value as in Zwave) might be beneficial to those that are not HEX inclined.

[slychiu]

For zwave this means that 50% ie value of 50 would be converted to 50/255 = 18% instead of 50%

Clipsal just has to work with CBus, comfort has to work with many diffrent systems

[Howser]

slychiu wrote:

For zwave this means that 50% ie value of 50 would be converted to 50/255 = 18% instead of 50%

The Zwave concept is totally flawed, hence why I mentioned how Clipsal does the conversion.

slychiu wrote:

Clipsal just has to work with CBus, comfort has to work with many diffrent systems

I was suggesting representing Counter values (Comfort values) in the iPhone App (Comfort app), this is a Comfort App representing Comfort values, no other system is in play here, or am I missing something?

[slychiu]

Counters can be mapped to Zwave, Cbus, KNX and many other systems, not just to counters in isolation from other systems

[Howser]

[user=1]slychiu[/user] wrote:

Counters can be mapped to Zwave, Cbus, KNX and many other systems, not just to counters in isolation from other systems

What I was suggesting was presenting the counter value in percentages within the iPhone app to the end user. This would be a display only attribute, which would not influence what is mapped to the counter.