I will end the following branches....

[Brad]

With the beta including all the work done in the following branches, I will end those branches.

hvacv12x
iui040restapi
iui4v12
prev121

Frank, Philippe and Brandt, Thanks for all the contributions.

Brad

[Brandt Daniels]

I swear I'll test when I get a chance just been busy with some other projects!

-Brandt

Sent from my iPhone

--
You received this message because you are subscribed to the Google Groups "domuslink-developers" group.
To post to this group, send an email to domuslink-...@googlegroups.com.
To unsubscribe from this group, send email to domuslink-develo...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/domuslink-developers?hl=en-GB.

[Brandt Daniels]

Brad,

trying out beta8 and I can't seem to login with the password I set in
the config file, getting incorrect password message.

-Brandt

[Brandt Daniels]

I was able to get in with the default '1234' even though that is not
what I have set in config.php :-/

-Brandt

On 2/27/11 7:33 PM, Brad wrote:

[Brad]

The config.php password is deprecated in this new version. The users are now managed under the setup area under a submenu item of "Users". There are default user and pin created when started for the first time and the password is 1234. You can change the password by editing the users and clearing out the password field and entering your favorite password. This is advised for both the admin user and pin1 as those are the default ones created. The CHANGES doc talks a bit about this, but needs to be enhanced to say to use the new "Users" screen.

Brad

[Brandt Daniels]

Doesn't seem to work. I put in a username of bdaniels as a pin type and it shows up as pin2 in the list under username. 

-Brandt

Sent from my iPhone

On Mar 3, 2011, at 6:22 AM, Brad <crus...@yahoo.com> wrote:

The config.php password is deprecated in this new version. The users are now managed under the setup area under a submenu item of "Users". There are default user and pin created when started for the first time and the password is 1234. You can change the password by editing the users and clearing out the password field and entering your favorite password. This is advised for both the admin user and pin1 as those are the default ones created. The CHANGES doc talks a bit about this, but needs to be enhanced to say to use the new "Users" screen.

Brad

--

[Brad]

Alright, guess the documentation is not as clear as I wanted it.

PIN types have no username assigned by the user, they are fabricated internally. That's why you see pin2. PIN types are only a password.

Username types exepect a username and a password.

Currently, the only part of the system that can use username/password is the RESTAPI. The domus.Link themes all use PIN types for now.

So, just create PINs with different passwords and security levels.

Brad

[Brandt Daniels]

I tried it on my iPhone...I was REALLY hoping to see some sort of numeric pin pad pop up, but I guess that isn't possible because you don't know what type of account it is until you have parsed the password.

Here is a really neat article for changing the iPhone keypad in a webapp:
http://stackoverflow.com/questions/773843/iphone-uiwebview-how-to-force-a-numeric-keyboard-is-it-possible


-Brandt

Brad

--

[Brad]

We could make a theme variation of the ones we have that pop up a pin pad. But then that would be the only mobile option and you would have to have numeric pins. That could be a selection though.

Brad

[Brandt Daniels]

What happen to the thermostat setpoint up/down buttons? Or did I never
commit that...

-Brandt

[Brad Samuels]

It's only in the web version, not the mobile version

Brad

[Brandt Daniels]

Not seeing them in my web browser on my MacBook. 

-Brandt

Sent from my iPhone

[Brad Samuels]

Are you seeing the mobile view?

Brad

[Brandt Daniels]

That makes no sense. I'd rather control the set point of my thermostat on the couch with a mobile device. In fact I would pass by the real thermostat before I got to my computer to bring up a web browser. 

-Brandt

Sent from my iPhone

On Mar 3, 2011, at 8:58 PM, Brad Samuels <bwsa...@gmail.com> wrote:

[Brandt Daniels]

It looks like a normal view to me

-Brandt

Sent from my iPhone

[Brad Samuels]

Well working on that. It's a beta...

Brad

[Brad Samuels]

In the default theme it's the module definition you created

Brad

[Brad]

Will add the Plus/Minus to the mobile theme. It was not in the hvac branch you created.

[Brad]

Hmm, I just checked the themes and both mobile themes have the +/- buttons. Which version do you have? 2beta8 is the latest.

[Brad]

I have ended the previous branches.

Brad

[Brad]

Now I see where the setpoint arrows are. Forgot about those. I think those should be on the module itself. Will add them there along with the current temp and setpoint value.

[Brad]

Too fast, the module's plus/minus buttons are the setpoint buttons. I will add the temp and setpoint values to those. All the controls are on modules and not the main page.

[Brandt Daniels]

Maybe the setpoint arrows are OK on the modules, however it would be
nice to be able to access them no matter what view you are on.

I don't think putting the temp and setpoint value on the module is a
good idea, because it will then ping the thermostat every time for this
value, and that would put extra x10 signal pollution on the lines, and
cause the webapp to slow down.

But really I feel that stuff is best left on the toolbar where it is
only reloaded occasionally.

[Brad]

It doesn't matter about the page reload as it is always reloaded every time you touch something. This is not ajax yet...

Anyway, I'm delving into the RCS status/control alot more right now and noticed it is pretty broke. It works for you as you have your HVAC control on house code "H" and I never changed that in the setpoint function. Restructuring the whole hvac control and adding the mode commands as well.

[Brad]

Brandt, could you send me the output from the command line of heyu with the rcs_req responses?

I need to make sure I am decoding the result string properly. If you could do it for all the mode states that would help too.

Thanks

Brad

[Brandt Daniels]

> heyu rcs_req preset A5 1 (temperature)
> heyu rcs_req preset A5 2 (setpoint temperature)
> heyu rcs_req preset A5 3 (system mode)
> heyu rcs_req preset A5 4 (fan mode)
> heyu rcs_req preset A5 5 (setback mode)
> heyu rcs_req preset A5 6 (setback delta temperature)

root@haplug:~# heyu rcs_req preset H5 1
03/05 12:35:33 Temperature = 76 : hu H0 (hvac_data)
root@haplug:~# heyu rcs_req preset H5 2
03/05 12:35:52 Temperature = 72 : hu H0 (hvac_data)
root@haplug:~# heyu rcs_req preset H5 3
03/05 12:35:58 System_mode = OFF : hu H0 (hvac_data)
root@haplug:~# heyu rcs_req preset H5 4
03/05 12:36:02 Fan = OFF : hu H0 (hvac_data)
root@haplug:~# heyu rcs_req preset H5 5
03/05 12:36:07 Setback = OFF : hu H0 (hvac_data)
root@haplug:~# heyu rcs_req preset H5 6
03/05 12:36:13 Temperature = 12 : hu H0 (hvac_data)

In newer revisions of the RCS TXB16 ( i have an older revision ) there
is also:

heyu rcs_req preset H5 7
heyu rcs_req preset H5 8

which I believe are the separate cool setpoint and heat setpoint. In my
thermostat revision the setpoint return value depends on what mode the
system is in.

-Brandt

[Brad]

Well, I have a new version up in the download area, but after looking at your output, I believe it will be broken. I think I will have the wrong index into the status returns.

Try it and let me know if I'm broke....

[Brad]

Just to be safe, I implemented a new parsing mechanism for the hvac status returns based on your command dumps. Thanks for that, it is a huge help.

So, try domus.Link2.0beta10.tar.gz as it is more robust in status parsing.

Brad