Messages

1

Installation issues / 12.04 multichannel sound card with squeezeslave

« on: August 26, 2014, 05:50:58 am »

I am having a problem getting virtual output on a sound card with squeezeslaves to work in 12.04 Aug 16th snapshot.  I have the virtual outputs setup and when I do a speaker test I get the front right, front left on the correct port on the sound card, but when I try to play something on the squeezeslave I get no sound or the sound comes from a different port on the sound card or even from another sound card.  I double checked that the alsa output in the squeezeslave was set to the correct Virtual_XX, and everything looks the same as I had it setup in 10.04.  Anyone have any ideas?

2

Installation issues / Re: NAS CIFS errors on April 13 28939 snap

« on: April 16, 2014, 05:01:51 pm »

I was getting the same errors as you cifs and link errors, I could be wrong but I think something changed in 12.04 version of cifs.  My NAS is just Ubuntu 12.04 with samba installed.  I think the problem with the link errors was because I did not have a username/password for my media share and therefor cifs was mounting it as an unsecured share.  I also had security = share in my smb.conf and I think that was giving the cifs mount error.  changing security = user I belive fixed it, but I did change several other setting in the smb.conf on my NAS.

See if setting the password in the webadmin to yourpassword,iocharset=utf8,sec=ntlm this allowed cifs to mount the drive before I changed any of my smb.conf setting.  I don't think the iocharset is really needed, but the sec=ntlm worked for me.

I could be totally wrong but was able to get the NAS to mount and it had nothing to do with LMCE.

3

Developers / Re: New Template ISY994i uploaded

« on: December 14, 2013, 06:52:49 am »

Mike,

I have not had time to test everything, but I am getting this error in the XX_Generic_Serial_Device.log

error: undefined method `percenttohexint' for #, line: 1460
backtrace:
   in: (eval): 1460
   from (eval):1460:in `cmd_ReceiveCommandForChild'
   from (eval):1460
 <0xb4f70b70>
05   12/13/13 23:46:40.418      GSD-Sleep Post 184 : 0 <0xb7774b70>
05   12/13/13 23:46:40.418      _QueueProc Post - 184 : 0 <0xb7774b70>
05   12/13/13 23:46:40.418      _QueueProc Pre - 184 : 0 <0xb7774b70>
05   12/13/13 23:46:40.418      GSD-Sleep Pre 184 : 0 <0xb7774b70>
05   12/13/13 23:46:40.418      Process Queue = 1 <0xb7774b70>
01   12/13/13 23:46:40.576      Error while calling method: Cannot call class method: cmd_ReceiveCommandForChild
error: undefined method `percenttohexint' for #, line: 1460
backtrace:
   in: (eval): 1460
   from (eval):1460:in `cmd_ReceiveCommandForChild'
   from (eval):1460
 <0xb4f70b70>
05   12/13/13 23:46:58.419      GSD-Sleep Post 184 : 0 <0xb7774b70>
05   12/13/13 23:46:58.419      _QueueProc Post - 184 : 0 <0xb7774b70>
05   12/13/13 23:46:58.419      _QueueProc Pre - 184 : 0 <0xb7774b70>
05   12/13/13 23:46:58.419      GSD-Sleep Pre 184 : 0 <0xb7774b70>
05   12/13/13 23:46:58.419      Process Queue = 1 <0xb7774b70>
01   12/13/13 23:46:58.579      Error while calling method: Cannot call class method: cmd_ReceiveCommandForChild
error: undefined method `percenttohexint' for #, line: 1460
backtrace:
   in: (eval): 1460
   from (eval):1460:in `cmd_ReceiveCommandForChild'
   from (eval):1460
 <0xb4f70b70>



Chris

4

Developers / Re: New Template ISY994i uploaded

« on: December 14, 2013, 05:02:20 am »

Mike,
I added those two packages and it is working now.

Thanks so much for all your hard work!!!!

Chris

5

Developers / Re: New Template ISY994i uploaded

« on: December 13, 2013, 11:47:24 pm »

Mike,

cat /var/log/pluto/55_Generic_Serial_Device.log
http://pastebin.com/itjtqGvP

Did you install ruby gems or some other package when your wrote the template.

Chris

6

Developers / Re: New Template ISY994i uploaded

« on: December 13, 2013, 07:18:43 am »

On a fresh 10.04 install I get the following error in the ISY994i log file.

1479:01   12/13/13 0:08:32.908      Failed loading code: Error loading code:
error: (eval):479:in `require': no such file to load -- mysql, line: 479
. <0xb4fd7b70>

Chris

7

Installation issues / Re: NO sound on MD used to work out of the box.

« on: December 19, 2012, 11:58:44 pm »

It is still not working.  This stopped working sometime over the last 6 month.  It was working on an install I did in May/June, that I had not updated till last week, After the update it stopped working.  The other 3 MD's did not have any audio problems.

root@moon40:~# cat /etc/asound.conf | pastebinit
http://pastebin.com/Q5DJZLcv

root@moon40:~# cat /usr/pluto/bin/SetupAudioVideo.sh | pastebinit
http://pastebin.com/hBZuHR8L

root@moon40:~# cat /etc/pluto.conf | pastebinit
http://pastebin.com/pkhfbTwj

8

Installation issues / Re: NO sound on MD used to work out of the box.

« on: December 19, 2012, 07:50:20 am »

I am having the same problem.  Installed from the 12/15 snapshot and i no longer have sound using spdf optical.

root@moon40:~# dmesg | pastebinit
http://pastebin.com/CFXFh22W

root@moon40:~# aplay -l | pastebinit
http://pastebin.com/HRpFr387

root@moon40:~# lspci | pastebinit
http://pastebin.com/1L66Js08

root@moon40:~# cat /etc/asound.conf | pastebinit
http://pastebin.com/zfdFLDVT

root@moon40:~# cat /etc/X11/xorg.conf | pastebinit
http://pastebin.com/Bvw7P11a

Any help would be appreciated.

9

Installation issues / Re: Insteon How-To?

« on: April 11, 2011, 07:07:22 pm »

I would go with this order
1. Install the 2476S
2. Plug in the 2412S PLM
3. Cross link the PLM and the switch
4. Connect to LMCE with RS232, and add the PLM device in LMCE
For some reason I thought that Ddamron has stated someplace that you have to have at lest on link created before you add the PLM to the system.

10

Installation issues / Re: Insteon How-To?

« on: April 11, 2011, 03:41:12 am »

For switches, at least the ones I have to, factory reset them you have to pull out the little button right below the paddle for like 10 sec and then push it in and hold it for 3 sec.  If I remember correctly.  Not all of the devices do both wired and wireless, you just have to look and see what you have.  There use to be a manual for the PLM, but I can't seem to find it online anymore.  I would call smarthome the customer support is not all that bad.  The receiver/transmitter in the PLM is not as strong as the ones in other devises, I ran into this when I only had a few Insteon devises.  Also from what I have read, CFL can cause a lot of interference if they are low cost, same with ceiling fans.  I do have a few eco Dimmable LED bulbs and they seem to work great.  What is the device you are trying to link with the PLM?

11

Installation issues / Re: Insteon How-To?

« on: April 10, 2011, 03:23:01 am »

If the lights do not stop blinking then a link was not created.  I think you have a problem with the devices not being able to communicate and not with linuxmce.  Is the PLM and the device on the same power phase?  Do you have a phase coupler?  For Insteon to work for the hole house you have to have at least 2 wired devices that are also capable of wireless transmission one installed on each phase, or a phase coupler.  You can test this by using an extension cord to power the PLM from the same circuit as one of the devices is on and try linking it that way.

12

Installation issues / Re: Insteon How-To?

« on: April 08, 2011, 06:57:03 pm »

I believe all you have left to do is to cross link the devises to the PLM.  When linking devices manual the first device that you put into linking mode will be the controller and the seconded device will be the responder.  For example to cross link a device you will go to the PLM and hold the set button for 10 sec until it starts blinking and then go to the light switch, for a switch link dimmer you hold paddle on for 10 sec, the dimmer should beep, and the light on the PLM should also have stopped blinking. you then have to repeat this process but put the light switch into linking mode first, and then put the PLM into linking mode.  This makes will make the two devices cross linked.  after you link all your devices this way reload the router and watch the log file wait till it is done doing everything and then look below the Config:["*****"] line everything listed below that line are the device ID's of all the devices that are now part of your system, and should have been added as children, you will need to reload your router one more time.  That should do it.

13

Users / Re: Snapshot testing

« on: March 30, 2011, 03:33:23 am »

Not sure if this is the right place, but i just installed the lastest snapshot 23858.  Everything went fine untill i tryed setting up a media director, a Zotac Ion 330, and i could not get the sound to work over HDMI.

cat /proc/asound/version on the core shows 1.0.23
cat /proc/asound/version on the MD shows 1.0.17
and both are usings alsamixer 1.0.18

Chris

14

Users / Re: Insteon not working - Need some ruby guidance

« on: May 05, 2009, 11:03:07 pm »

I had my PLM working with 710, and about 20 insteon devices, about 40% of the time when I would restart the core which is where my PLM is connected, I would lose a device or two on the floor plan.  I have looked through all of the ruby code to try and fix this problem, and also add support for the HVAC adapter and for the motion sensor.  The time out errors are because the PLM cannot communicate with the device at that address.  The chip inside the PLM that sends and receives commands form your power lines is about 75% as strong as the chips all other insteon devices.  So even though one device commutates perfectly with another device, It might not be getting the signal to the PLM.  I fix this problem in my network, and now it works 100% of the time and even the response time on sending commands is faster.  A few ways you can fix this problem.
1) Access Points should be located on the 1st receptacle on the line, As close as you can get it to the actual breaker box(this fixed my problem), and make sure one on is on each phase of your power.
2) Do not plug the PLM into a surge protector.
3) It would be ideal to have the PLM as close to the breaker box as possible.
4) Move the PLM to a different line that does not have lots of electronics on it.

After you get the communication problem fixed you should not see the timeout error any more.

I did look at trying to update the driver to support more devices, and I got the HVAC half way working, but I kept running into the problem of not having any link management available.  You can link every insteon device from the PLM and never have to go around and push the dumb button in for 10 seconds.  I could not figure out a good way to accomplish device linking natively in LMCE, so I stopped working on the driver.  I spent a lot of time looking around to see how others are handling insteon networks, and most of them have gone with ISY-99.  It has a lot of advantages over using just the PLM.  I just received it in the mail last week, and started working on a driver for it.
Hope this helps,
Chris

15

Users / Re: GSD and Ruby Question

« on: January 28, 2009, 10:20:53 pm »

That is not exactly what I need; I will try and be a bit clearer.  The TV is the only monitor attached to the MD and I amusing a wii remote so I have no way of seeing what media scenario I am activating, I also enabled ignore on/off because it was turning the TV off and I think on when I changed media scenarios.  Even if it was turning it on again, I still don’t want it to turning the TV off then On again, and maybe I am seeing this problem because I do not have the on command implemented yet because it has to be sent at a baud rate of 110.  Once I manually turn on the TV, it changes inputs correctly and works great.  I am looking for something like a start up media scenario that you can edit just like the other media scenarios?

Chris