Recent Posts

Pages: 1 2 3 [4] 5 6 ... 10
Users / Re: [12.04] OpenZWave Aeon ZStick Issue
« Last post by RayBe on October 15, 2014, 12:18:55 pm »

Recently i used a extension cable to get my aeon-labs z-stick away from my core, more towards my z-wave network, so there was no interference from my core on the stick.
Before it was plugged in the back of my core. I also positioned the z-stick vertikal.
I found a article online, discribing this as the recommended way.

After some testing i found out that my z-wave network responded much better.
Even a battery operated sensor, which previously responded every now and then, now responce great.

Users / Re: Raspberry Pi as a MediaDirector
« Last post by RayBe on October 15, 2014, 12:11:16 pm »
Thanks for looking into it.

Code: [Select]
root@moon293:~# apt-cache policy pluto-orbiter
  Installed: (none)
  Version table: 0
        500 wheezy/main armhf Packages
        100 /var/lib/dpkg/status

Seems like it's not installed, which is very strange to me because it did before.
This is on the newly installed rPi-MD, after update&&upgrading my core and running /usr/pluto/bin/
I did not recreate the SD-card, as this was at your latest content.

Users / Re: [12.04] OpenZWave Aeon ZStick Issue
« Last post by davegravy on October 15, 2014, 07:25:30 am »
Thanks Raybe.

I haven't added back all my other nodes yet, so I still just have the one test node in my network.

This morning I couldn't control that test node anymore. From the logs it looks like overnight my CORE decided that the node was dead after several attempts to reach it. I tried a router reload but that wouldn't bring it back. A reboot fixed it however.

The node represents a lamp module which is 5ft away from the Zstick so it shouldn't have trouble communicating to it. I mistakenly deleted the log which shows the point last night where the communication died, but I'll wait to see if it happens again and post the log if it does.
Users / Re: Raspberry Pi as a MediaDirector
« Last post by phenigma on October 14, 2014, 07:02:50 pm »
No idea what is up.  No issues here.  apt-cache policy pluto-orbiter just to be sure.

Users / Re: NEW Remote Screens for UI1
« Last post by phenigma on October 14, 2014, 07:01:18 pm »
Let me know if you have any issues with the screens, everything is mostly good here but I have yet to add the Bind to Remote commands which may cause some undesired input switching until I can get those added.

Users / Re: Need some dedicated testers.
« Last post by davegravy on October 14, 2014, 06:30:16 pm »
First, thank you to everyone who has spent a couple minutes providing feedback on qorbiter for android. After some serious thought and discussion as well as observation, I think its time to slow this train down a bit. I dont mean development will stop. Not in the least bit. But, I am guilty of jumping to the shiniest new object. Also, some other things need to be taken into consideration. Qorbiter now has binaries for:
*x86 Linux - Desktops
*Arm linux - Raspberry pi's

Other platforms:
Windows is touch and go at this time...
Sailfish ive just not gotten around to
Same with blackberry
Made my first iOs app yesterday

This means there needs to be both active skin development and testing for all these platforms (no, not right now!) But in light of this, I think  I as a developer have a duty to take this a little more seriously, as its graduated far from a prototype toy. So, with all of that long winded statement out of the way, im proposing that we start working using the concept of agile development. There are many ways to do this, but I will share with you my understanding of this process.

1. Backlog - This is basically the entire wishlist of features. Everything you can think of. It supposed to be weighted by difficulty. A challenge here is to decide on how we deal with features across platforms.

2. Backlog Grooming - Taking stuff from the wish lists and putting it on the sprint task list. You are careful not to overload the sprint with too many tasks. the goal is to get things working within the sprint.

3. Sprint - Development time where things are developed. It could be bug fixes, new features, or a mix of both.

4. Sprint demo - Demonstration of sprint implementation

People involved.

Product Owners - This would normally be the client. They fill the backlog, weight the importance of features (1-5), and test features after a sprint. In this case, its the linuxmce community.

Scrum Master - This person directs the flow of traffic. Part project manager / Part developer the help with sprint planning and normally moderate daily standups (something we cant do)

Developer - Implements features and fixes bug according to the sprint plan.

SO, with all that said, basically I want to do something similar to this where...

*QOrbiter feature list / backlog is put in wiki.
*Tasks get groomed from feature list in wiki, to active tickets in trac.
*Tasks get completed over a 2 week sprint, people test
*Rinse repeat

The tasks could be picked by the community every two weeks for most important focus.

More stable releases
Targeted feature completion.
Easier update paths

Slower updates
Community decisions can be slow
Requires involvement of everyone (cause you know, its your product)

So, let me know what you think, but I seriously leaning this direction with the first tasks being
*Improve initial installation experience.
*Fix skin detection to properly detect phones / tablets
*Add remote screens
*Fix remote errors in sizing, commands sent.


Seems like a great direction to me.
Users / Re: First look at the new Athena Orbiter iOS App
« Last post by RayBe on October 14, 2014, 03:52:19 pm »
Looking great!
Marketplace / Dianemo Raspbmc-CEC Firmware
« Last post by totallymaxed on October 14, 2014, 01:17:43 pm »
We've taken your feedback on-board regarding our original Dianemo Raspbmc-CEC firmware images and we have moved over to a new installer for Dianemo Raspbmc-CEC firmware. Now you just install Raspbmc on an SD card and then run the installer from the booted card to install - and that's it. Any customer who has an original firmware image and would like the new installer should contact me.

We have updated installation instructions for the new installer here;

If you have any questions related to Raspbmc-CEC then contact me here;


Users / Re: NEW Remote Screens for UI1
« Last post by RayBe on October 14, 2014, 12:44:40 pm »
great work, they look cool!
thanks phenigma
Users / Re: [12.04] OpenZWave Aeon ZStick Issue
« Last post by RayBe on October 14, 2014, 12:43:45 pm »
hi davegravy,

In order to get Lmce to reset your controller, you must send a reset command to the ZWave device, with the argument set to "ResetController".
These links discribe in detail how to use the Lmce 12.04 open-zwave implementation:

Pages: 1 2 3 [4] 5 6 ... 10