Access Keys:
Skip to content (Access Key - 0)
 

Android Testers

Administrator

On May 25, 2010 04:19

Looking for a couple of people to test the new Android client for 2.0 which should be pretty identical to features in iPhone.

At this point need a developer type who is able to work things out from the version control by themselves and has a Android device to test with.

Send me an email or ping me here.

PS. Will make more consumable Android beta for others soon.
 
Labels: , , ,
Participants: Administrator , Dan Cong , Johan Buntinx , Juha Lindfors , Jesus Arias

Comments (9)

 

  1. May 26, 2010

    Administrator says:

    You can check out the sourcecode for the Android client: svn co http://openremo...

    You can check out the sourcecode for the Android client:

    svn co http://openremote.svn.sourceforge.net/svnroot/openremote/branches/feature/Android_profile_service/

    The checkout contains build.xml which you can use to build the binary with ANT tool.

    You will also need to build the controller from the sourcecode from this branch:

    svn co http://openremote.svn.sourceforge.net/svnroot/openremote/branches/feature/Controller_profile_service/

    The checkout contains build.xml which you can use to build the binary with ANT tool ('ant war' command)

    The controller configuration files can be generated with http://composer.openremote.org/demo - WARN: I haven't checked if the current online version produces compatible resource files, it should but.... this is untested stuff. Let me know if there's an issue here and I will try to put a more recent version of the tools online.

    This is very much untested at the moment, so expect glitches and issues. Feel free to contact if you need help.

    1. May 26, 2010

      Johan Buntinx says:

      Hi Quite a while ago I have been playing with some early versions of OpenRemote...

      Hi

      Quite a while ago I have been playing with some early versions of OpenRemote and set up an ORB on an alix machine to connect to my home (KNX) lighting system and some IR AV equipment. That work didn't really get further then the experimental phase, but I still want to get it fully operational. In the meantime I have bought an android device (HTC Magic  Android 1.5) and did some 'HelloWorld' android programming. As a java developer and having the hardware required I guess I fit in the profile you described for the android tester.  For the moment I'm downloading the sources to get started with deployment and configuration and I'll keep you informed of my progress.

      Regards

      Johan

      1. May 27, 2010

        Juha Lindfors says:

        Great! Thanks,

        Great! Thanks,

        1. Jul 05, 2010

          Johan Buntinx says:

          Hi, at last I got to playing around with the android client. I setup my control...

          Hi,

          at last I got to playing around with the android client. I setup my controller and managed to get it running. No major problems there, only tomcat doesn't seem to pickup the welcome file from web.xml, so I had to add to add index.html when browsing to the controller.

          I setup a very basic app on the modeler to get started and deployed the exported openremote.zip to the controller.

          When I run the android app on an emulator, I can add the controller url manually (autodiscover doesn't seem to work) , but after that I can only see a login screen (username & password entry fields). Which username password should I use there? I tried some variations of my openremote account because I don't know which other account it could be, but I'm still stuck at the login screen.

          Johan

          1. Jul 05, 2010

            Juha Lindfors says:

            The default config out-of-the-box in subversion currently comes with controller ...

            The default config out-of-the-box in subversion currently comes with controller URL's secured (with no default users setup).

            You can bypass this by going into the controller WEB-INF/web.xml file – at the very end of the file there's a longish section starting with <security-constraint> tag.

            You can remove the whole section until the end (leave the last </web-app> element in place though)

            	<!-- Constraint resource: /rest/control/* -->
	
	<security-constraint>
	  <web-resource-collection>
	    <web-resource-name>Control command RESTful service of Openremote Controller</web-resource-name>
	    <description>Control command RESTful service of Openremote Controller</description>
	    <url-pattern>/rest/control/*</url-pattern>
	    <http-method>GET</http-method>
	    <http-method>POST</http-method>
	  </web-resource-collection>
	  <auth-constraint>
	    <role-name>openremote</role-name>
	  </auth-constraint>
	</security-constraint>
	<!-- Constraint resource: /rest/panel/* -->
	<security-constraint>
	  <web-resource-collection>
	    <web-resource-name>Panel identity RESTful service of Openremote Controller</web-resource-name>
	    <description>Panel identity RESTful service of Openremote Controller</description>
	    <url-pattern>/rest/panel/*</url-pattern>
	    <http-method>GET</http-method>
	    <http-method>POST</http-method>
	  </web-resource-collection>
	  <auth-constraint>
	    <role-name>openremote</role-name>
	  </auth-constraint>
	</security-constraint>
	<!-- 
	<security-constraint>
	  <web-resource-collection>
	    <web-resource-name>Status command RESTful service of Openremote Controller</web-resource-name>
	    <description>Status command RESTful service of Openremote Controller</description>
	    <url-pattern>/rest/status/*</url-pattern>
	    <http-method>GET</http-method>
	    <http-method>POST</http-method>
	  </web-resource-collection>
	  <auth-constraint>
	    <role-name>openremote</role-name>
	  </auth-constraint>
	</security-constraint>
	<security-constraint>
	  <web-resource-collection>
	    <web-resource-name>Polling command RESTful service of Openremote Controller</web-resource-name>
	    <description>Polling command RESTful service of Openremote Controller</description>
	    <url-pattern>/rest/polling/*</url-pattern>
	    <http-method>GET</http-method>
	    <http-method>POST</http-method>
	  </web-resource-collection>
	  <auth-constraint>
	    <role-name>openremote</role-name>
	  </auth-constraint>
	</security-constraint>
	-->
	<login-config>
	  <auth-method>BASIC</auth-method>
	  <realm-name>OPENREMOTE_Controller</realm-name>
	</login-config>
	<security-role>
	  <role-name>openremote</role-name>
	</security-role>

            Removing the above section will give you an unprotected controller which is fine for testing.

            FYI, I've consolidated all the controller feature branches under http://openremote.svn.sourceforge.net/svnroot/openremote/branches/project/Controller_2_0_0_Alphas/ branch (also keeping http://openremote.svn.sourceforge.net/svnroot/openremote/trunk/Controller more or less up to date) aside from the latest JSON API addition to controller, and Marcus' earlier Russound work.

            Just for your future reference, the Controller_profile_service branch should be ok for initial testing but is no longer actively worked on.

            1. Jul 05, 2010

              Johan Buntinx says:

              ok thanks, that worked. I can now start testing some real functionality, but not...

              ok thanks, that worked. I can now start testing some real functionality, but not today. Need to get some sleep.

          2. Jul 07, 2010

            Dan Cong says:

            regarding auto-discovery in emulator, by default multicast port is not available...

            regarding auto-discovery in emulator, by default multicast port is not available, after launching emulator, run adb forward tcp:2346 tcp:2346 under %android_SDK_home%/tools, this command will enable multicast port.

  2. Jul 23, 2010

    Jesus Arias says:

    Any B-tester needed? I´ve got a HTC desire and a full KNX installation running....

    Any B-tester needed?

    I´ve got a HTC desire and a full KNX installation running. It would be great work on this project. I´m not a java guy, but people working with me are. We´re really looking forward to see this working.

    Regards!

    Jesús.

    1. Jul 29, 2010

      Juha Lindfors says:

      Hello Jesus, Sorry for taking long time to respond. The forums died on us. Abs...

      Hello Jesus,

      Sorry for taking long time to respond. The forums died on us.

      Absolutely yes, I'm about to start testing the Android app myself and would very much be interested in getting more people to test things, especially with KNX.

      I've been adding new KNX support into controller as well, and would be interested to have people take it for a spin (I don't have dimmers for 8-bit values, so need someone to test that for me).

      Will you be able to work things out from the source? If yes, you can start with Android by building this branch here: http://openremote.svn.sourceforge.net/svnroot/openremote/branches/feature/Android_profile_service

      If not, give me a few more days and I'll put a binary together and make it available for download/install.

      The latest developer binary of the OR Boss 2.0 controller is available for download here: http://sourceforge.net/projects/openremote/files/For%20Developers/OpenRemote_Boss_2_0_0_DeveloperRelease4.zip/download

      For the latest KNX features (3-bit controller and unsigned 8-bit value DPTs), I'll tag and create binaries in the next couple of days.

      Thanks for your offer to help,

      – Juha
Adaptavist Theme Builder Powered by Atlassian Confluence
Free theme builder license