Recent Posts

Pages: 1 ... 4 5 [6] 7 8 ... 10
51
Users / Re: [12.04] OpenZWave Aeon ZStick Issue
« Last post by RayBe on October 16, 2014, 04:54:47 am »
Davegravy, FYI,
Please keep in mind that the z-wave implementation in Lmce 12.04 (based on open-zwave) is a lot different than the one in Lmce 10.04.
In comparison, the open-zwave based version has a lot more features and is very well maintained, but is also much pickier when it comes to its zwave-network setup.
Open-zwave needs a very good and stable z-wave network to work good, so if things worked in Lmce 10.04, that does not necessary mean they work as good in Lmce 12.04.

br,
Raymond
52
Developers / Re: squeezelite as an alternative to squeezeslave
« Last post by Esperanto on October 15, 2014, 07:54:15 pm »
It's not really code just shell script I referred to:
http://forum.linuxmce.org/index.php?topic=13714.msg99923#msg99923

Um?  No.  You can edit the device and describe it any way you would like, just like every other device in the system.
I mean the name squeezelite promotes itself with to the slimserver. That can be the description or whatever. It just a minor change which might help people when debugging.

Heh.  Ok.  I don't see any code or feature patches to support pulseaudio anywhere in the system in trac anywhere.  And since we don't support pulseaudio I will not add specific pulseaudio code until the system supports it.  That being said: Have you even tried it?  Have you put your pulse:sink name in as the output device?  I don't think you've even tried it and from the squeezelite documentation it appears that it should work as is.

I tried that when I created the squeezelite template and launchscript. The only option that is there beside the alsa options is pulse in general:
Code: [Select]
dcerouter_1039929:~# squeezelite -l
Output devices:
  default                        - Playback/recording through the PulseAudio sound server
You can however specify the sink as an environment variable as I did in my launchscript.


Look, I'm getting really frustrated that you that certain people continually complain about things without actually trying to do much of anything about it.  I work *really* hard here *for free* to try and support all kinds of things for people, including things that I don't use like the damn squeezeslave/squeezelite players.   So thanks for testing, I'm glad you're complaining that it doesn't slice and dice and make damn Julien fries at the same freakin' time.  I'm really happy that it's 'working' but not 'properly' becuase it doesn't describe the device to your satisfaction and that it doesn't support an audio subsystem that we don't support at all.

I feel your frustration. I spend just a fraction like you do and all my efforts towards most linuxmce things (like squeezelite) are wasted time since they are not used anyway. Back then I tried to create a separate device for squeezelite but could not get Linuxmce to recognize it as media playable device and stopped trying just because I felt it would end up as not being used anyway.

Since pulseaudio is on the list of wishes of some devs I thought that something small as supporting a pulsesink would not be a problem since it does not influence normal behavior although I understand it has zero priority.

But heeee J.... all your efforts are very much appreciated! We all love ya.  :-*
53
Users / Re: [12.04] OpenZWave Aeon ZStick Issue
« Last post by davegravy on October 15, 2014, 04:10:44 pm »
davegravy,

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.

br,
Raymond

Hi RayBe,

Thanks for the suggestion, I think it's already vertically oriented however. This test node, as well as the 30 or so others that I have in my house, have been behaving beautifully over the last year in their current config / placement /etc.  I don't know if it is my Zstick that is failing, or recent changes to the LMCE Zwave implementation, a prankster hacker, or something else that is to blame, but something is definitely up.

The test node survived the night this time, and has about 12 hours of uptime now. I'll keep an eye on it.

54
Users / Re: [12.04] OpenZWave Aeon ZStick Issue
« Last post by RayBe on October 15, 2014, 12:18:55 pm »
davegravy,

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.

br,
Raymond
55
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
pluto-orbiter:
  Installed: (none)
  Candidate: 2.0.0.46.14090829353
  Version table:
     2.0.0.46.14090829353 0
        500 http://deb.linuxmce.org/raspbian/ 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/Diskless_CreateTBZ.sh
I did not recreate the SD-card, as this was at your latest content.

br,
Raymond
56
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.
57
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.

J.
58
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.

J.
59
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
*Android
*OS X

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.

Pros:
More stable releases
Targeted feature completion.
Easier update paths

Cons:
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.

-golgoj4

Seems like a great direction to me.
60
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!
br,
Raymond
Pages: 1 ... 4 5 [6] 7 8 ... 10