16
Users / Re: adding a qorbiter messed up my rooms
« on: August 22, 2014, 12:25:32 am »
last post has the android screen shots, this one has the web orbiter screen shots...
News:
Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com
LinuxMCE sponsor
open.home.automation
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
17
Users / adding a qorbiter messed up my rooms
« on: August 22, 2014, 12:22:43 am »
I attempted to add my first qorbiter today and made quite a mess. The first one I added was device 73. I thought perhaps the reason it wasn't looking good was something I did wrong in the setup, so I deleted it and created another which was device 77. It was just as bad as the first. The display on my android phone is not very nice at all. Is there a better skin I should be using?
I now have two rooms in my room list which correspond to my home theater room. These rooms are listed as 73 and 77, not by the name "home theater" which is what used to be in my room list. "home theater" is now gone. That is the room I assigned both of my qorbiters to. I am attaching screenshots both of my android phone and of a web orbiter to illustrate.
Also noticeable in the android screenshots is that all of the rooms have a "0" after their name, with the exception of closet/storage (which shouldn't even show up in the list at all because I checked the "Don't show room on orbiters" box, it doesn't show up on the web orbiter room list as can be seen in the screenshots)
If anyone can help me get things back to the way they used to be it would be much appreciated.
I would very much like to use qorbiter, but the initial experience has not been good. Navigating the room list is especially annoying because when I am trying to scroll up/down it winds up scrolling left/right. It usually takes me a few touches at the screen to successfully get it to scroll up/down. It would be nice if left/right scroll were not even possible in the room list....
I now have two rooms in my room list which correspond to my home theater room. These rooms are listed as 73 and 77, not by the name "home theater" which is what used to be in my room list. "home theater" is now gone. That is the room I assigned both of my qorbiters to. I am attaching screenshots both of my android phone and of a web orbiter to illustrate.
Also noticeable in the android screenshots is that all of the rooms have a "0" after their name, with the exception of closet/storage (which shouldn't even show up in the list at all because I checked the "Don't show room on orbiters" box, it doesn't show up on the web orbiter room list as can be seen in the screenshots)
If anyone can help me get things back to the way they used to be it would be much appreciated.
I would very much like to use qorbiter, but the initial experience has not been good. Navigating the room list is especially annoying because when I am trying to scroll up/down it winds up scrolling left/right. It usually takes me a few touches at the screen to successfully get it to scroll up/down. It would be nice if left/right scroll were not even possible in the room list....
18
Users / Re: zwave network lockups/delays
« on: August 15, 2014, 07:32:22 am »
I'm running 12.04 now using the latest install dvd. I also added some zwave range extenders to my network to try to reduce delays/lockups. Things are working better now, but still not perfect. I still get instances where commands get delayed several seconds, sometimes up to a minute. When this occurs it blocks all subsequent commands until that one makes it through.
I have been playing around in the advanced zwave section, but haven't been able to make much sense of things. When I open the page most of the controls are blocked. I am attaching an screenshot. I was able to get to the blocked controls by removing the blocking elements using "inspect element" in chrome. After that I tried to do a "heal network". Doing this made the ZWave process start using close to 100% CPU and it has been doing that for over a day. Is this to be expected? How long should the 'heal network' take to complete? Should I just router reload or server reboot at this point?
I have been playing around in the advanced zwave section, but haven't been able to make much sense of things. When I open the page most of the controls are blocked. I am attaching an screenshot. I was able to get to the blocked controls by removing the blocking elements using "inspect element" in chrome. After that I tried to do a "heal network". Doing this made the ZWave process start using close to 100% CPU and it has been doing that for over a day. Is this to be expected? How long should the 'heal network' take to complete? Should I just router reload or server reboot at this point?
19
Users / Re: zwave network lockups/delays
« on: July 22, 2014, 11:50:34 pm »
I am on 1004, but if I do a fresh install I will be using 1204.
The only way I could get the unresponsive light to do anything was to kill power to it. After I restored power I was able to use the inclusion remote to remove it and readd it. The light appeared to be readded just fine. A new light appeared in my device tree. However, it still is not responding to commands... All the other lights in the room, respond as expected, but that one does not. I've tried using both scenarios to operate the light as well as using the "Send Command to Device" pop up on the web interface. Neither produces any response from the light.
Another question, when adding in a multipole light, should I only include the master switch using the inclusion remote, or should the include also be done on the remote switches as well?
I think of I've done it both ways and both ways seemed to have worked, but now I am having issues and wondering if maybe I did something wrong...
The only way I could get the unresponsive light to do anything was to kill power to it. After I restored power I was able to use the inclusion remote to remove it and readd it. The light appeared to be readded just fine. A new light appeared in my device tree. However, it still is not responding to commands... All the other lights in the room, respond as expected, but that one does not. I've tried using both scenarios to operate the light as well as using the "Send Command to Device" pop up on the web interface. Neither produces any response from the light.
Another question, when adding in a multipole light, should I only include the master switch using the inclusion remote, or should the include also be done on the remote switches as well?
I think of I've done it both ways and both ways seemed to have worked, but now I am having issues and wondering if maybe I did something wrong...
20
Users / Re: zwave network lockups/delays
« on: July 22, 2014, 10:11:44 pm »
I am using an inclusion remote.
http://www.amazon.com/gp/product/B007J26PIS/ref=wms_ohs_product?ie=UTF8&psc=1
Everything seemed to be going fine at first. But the more lights I add and the further I get away from the usb zwave controller the more issues I am having.
I now have one light that stopped responding completely. I tried to manually remove it and readd it to the network, but it didn't work with the inclusion remote. I then just deleted the device from the tree and then tried to readd it, still not working... The switch functions as expected, but all the zwave functionality does not work anymore.
I kind of want to start from scratch with a fresh linuxmce install and see if I could have some better luck. What is the best way of doing that? Do I need to go through with the inclusion remote and remove all the devices? Should I reset the zwave controller first? Can anyone help me with the order of operations for tearing down and rebuilding my zwave network?
http://www.amazon.com/gp/product/B007J26PIS/ref=wms_ohs_product?ie=UTF8&psc=1
Everything seemed to be going fine at first. But the more lights I add and the further I get away from the usb zwave controller the more issues I am having.
I now have one light that stopped responding completely. I tried to manually remove it and readd it to the network, but it didn't work with the inclusion remote. I then just deleted the device from the tree and then tried to readd it, still not working... The switch functions as expected, but all the zwave functionality does not work anymore.
I kind of want to start from scratch with a fresh linuxmce install and see if I could have some better luck. What is the best way of doing that? Do I need to go through with the inclusion remote and remove all the devices? Should I reset the zwave controller first? Can anyone help me with the order of operations for tearing down and rebuilding my zwave network?
21
Users / Re: gc100 and rs232 control
« on: June 13, 2014, 10:36:39 pm »
I had this working for months and now all of a sudden it has stopped working...
I am able to send the receiver commands with success if I use /usr/pluto/bin/TestSerialPort
but the commands no longer work if I use MessageSend
I'm not sure what could have happened. The COM port on device is still defined correctly. The setup appears to be unchanged from what I can tell...
Here is the output in the DCERouter log when I attempt to turn off the receiver using MessageSend
08 06/13/14 16:31:01.131 Received Message from 0 (unknown / ) to 52 (YSP5100 / Home Theater), type 1 id 193 Command:Off, retry none, parameters: <0x70176b40>
08 06/13/14 16:31:01.131 Parameter 97(PK_Pipe): -1 <0x70176b40>
05 06/13/14 16:31:01.181 Socket::ReceiveData 0xb4cca670 failed, bytes left 0 start: 5410000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 163 Incoming_Conn Socket 163 ::ffff:192.168.60.222 <0x70176b40>
05 06/13/14 16:31:01.181 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 163 ::ffff:192.168.60.222 <0x70176b40>
05 06/13/14 16:31:01.181 TCPIP: Closing connection to -1003 (Router Dev #0) 0xb4cca670 m_Socket: -1 <0x70176b40>
05 06/13/14 16:31:01.181 Router::RemoveAndDeleteSocket 0xb4cca670 -1003 <0x70176b40>
I am able to send the receiver commands with success if I use /usr/pluto/bin/TestSerialPort
but the commands no longer work if I use MessageSend
I'm not sure what could have happened. The COM port on device is still defined correctly. The setup appears to be unchanged from what I can tell...
Here is the output in the DCERouter log when I attempt to turn off the receiver using MessageSend
08 06/13/14 16:31:01.131 Received Message from 0 (unknown / ) to 52 (YSP5100 / Home Theater), type 1 id 193 Command:Off, retry none, parameters: <0x70176b40>
08 06/13/14 16:31:01.131 Parameter 97(PK_Pipe): -1 <0x70176b40>
05 06/13/14 16:31:01.181 Socket::ReceiveData 0xb4cca670 failed, bytes left 0 start: 5410000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 163 Incoming_Conn Socket 163 ::ffff:192.168.60.222 <0x70176b40>
05 06/13/14 16:31:01.181 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 163 ::ffff:192.168.60.222 <0x70176b40>
05 06/13/14 16:31:01.181 TCPIP: Closing connection to -1003 (Router Dev #0) 0xb4cca670 m_Socket: -1 <0x70176b40>
05 06/13/14 16:31:01.181 Router::RemoveAndDeleteSocket 0xb4cca670 -1003 <0x70176b40>
22
Users / zwave network lockups/delays
« on: June 13, 2014, 12:56:34 am »
I've added a bunch of leviton zwave switches and sometimes when commands are sent, one of the switches does not respond immediatly. There is a delay from anywhere between a couple seconds to a couple minutes. During this time the rest of the zwave switches are unresponsive. When the unresponsive switch eventually responds , the rest of the zwave commands that had been issues that weren't getting through all happen in rapid succession.
Anyone have experiences like this? Any solutions?
Anyone have experiences like this? Any solutions?
23
Users / should zwave light status update when switches are operated manually?
« on: May 02, 2014, 08:07:32 pm »
If I control my zwave switches using orbiters the status (as shown in the advanced device page for the light, and on my floorplans) correctly updates
however if I use the light switches manually the status does not change, it does not appear that the zwave switches send status updates back to linuxmce... is that expected behavior? Should linuxmce update the status when a light switch is operated manually?
however if I use the light switches manually the status does not change, it does not appear that the zwave switches send status updates back to linuxmce... is that expected behavior? Should linuxmce update the status when a light switch is operated manually?
24
Users / Re: using a script to launch scenarios
« on: April 24, 2014, 07:43:23 am »
figured it out myself... simple recipe
svn checkout http://svn.linuxmce.org/svn/trunk/src/
cd src/MessageSend
make
in case anyone else is interested....
thanks again for all the help... and the smiles
svn checkout http://svn.linuxmce.org/svn/trunk/src/
cd src/MessageSend
make
in case anyone else is interested....
thanks again for all the help... and the smiles
25
Users / Re: using a script to launch scenarios
« on: April 24, 2014, 07:21:56 am »
I'd like to be able to run MessageSend from another linux host. I tried to just copy the binary to the other linux host, but when I try to run it I get:
./MessageSend
-bash: ./MessageSend: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
Can I compile this on the other linux host without too much difficulty?
Right now I am using ssh keys to execute the MessageSend commands on the linuxmce core, but there is a delay while the ssh login takes place.... it would be nice to have the scenarios execute faster...
./MessageSend
-bash: ./MessageSend: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
Can I compile this on the other linux host without too much difficulty?
Right now I am using ssh keys to execute the MessageSend commands on the linuxmce core, but there is a delay while the ssh login takes place.... it would be nice to have the scenarios execute faster...
26
Users / Re: using a script to launch scenarios
« on: April 23, 2014, 04:50:36 pm »
yay! thank you so much posde
smile I did...
smile I did...
27
Users / Re: using a script to launch scenarios
« on: April 23, 2014, 08:10:59 am »
I'm having a hard time figuring out what the "Execute Command Group message of the DCERouter device" is...
I have found the PK_CommandGroup for all of the items in the CommandGroup table I am interested in.
There are so many tables dealing with devices/commands/command_groups, it is hard to figure out how to connect them all together.
I know that my DCERouter is device 2, but I am not sure how to get a list of the commands it is capable of and their IDs.
I have been able to successfully turn individual lights on/off using MessageSend using the information in dcerouter.log.. I just can't figure out how to execute the command groups.
Any help would be appreciated. Thank you very much for the assistance provided so far.
I have found the PK_CommandGroup for all of the items in the CommandGroup table I am interested in.
There are so many tables dealing with devices/commands/command_groups, it is hard to figure out how to connect them all together.
I know that my DCERouter is device 2, but I am not sure how to get a list of the commands it is capable of and their IDs.
I have been able to successfully turn individual lights on/off using MessageSend using the information in dcerouter.log.. I just can't figure out how to execute the command groups.
Any help would be appreciated. Thank you very much for the assistance provided so far.
28
Users / Re: using a script to launch scenarios
« on: April 17, 2014, 08:06:12 am »
here is what I see when I click on one of my lighting scenarios in my web orbiter
it just shows the individual messages to each device, it doesn't show what command group was executed...
will I have to send messages to each device individually?
maybe I need to increase the verbosity of my logs in order to see command group information?
DCERouter.log
08 04/17/14 2:00:21.315 Received Message from 56 (myweb2orbiter / ) to 79 (Ceiling Lights / Home Theater), type 1 id 184 Command:Set Level, retry none, parameters: <0x7a18ab40>
08 04/17/14 2:00:21.315 Parameter 76(Level): 45 <0x7a18ab40>
08 04/17/14 2:00:21.317 Received Message from 56 (myweb2orbiter / ) to 78 (Daybed Lights / Home Theater), type 1 id 184 Command:Set Level, retry none, parameters: <0x7a18ab40>
08 04/17/14 2:00:21.317 Parameter 76(Level): 45 <0x7a18ab40>
08 04/17/14 2:00:21.319 Received Message from 56 (myweb2orbiter / ) to 81 (Lamp / Home Theater), type 1 id 184 Command:Set Level, retry none, parameters: <0x7a18ab40>
08 04/17/14 2:00:21.320 Parameter 76(Level): 50 <0x7a18ab40>
08 04/17/14 2:00:21.321 Received Message from 56 (myweb2orbiter / ) to 80 (Window Lights / Home Theater), type 1 id 184 Command:Set Level, retry none, parameters: <0x7a18ab40>
08 04/17/14 2:00:21.321 Parameter 76(Level): 45 <0x7a18ab40>
it just shows the individual messages to each device, it doesn't show what command group was executed...
will I have to send messages to each device individually?
maybe I need to increase the verbosity of my logs in order to see command group information?
DCERouter.log
08 04/17/14 2:00:21.315 Received Message from 56 (myweb2orbiter / ) to 79 (Ceiling Lights / Home Theater), type 1 id 184 Command:Set Level, retry none, parameters: <0x7a18ab40>
08 04/17/14 2:00:21.315 Parameter 76(Level): 45 <0x7a18ab40>
08 04/17/14 2:00:21.317 Received Message from 56 (myweb2orbiter / ) to 78 (Daybed Lights / Home Theater), type 1 id 184 Command:Set Level, retry none, parameters: <0x7a18ab40>
08 04/17/14 2:00:21.317 Parameter 76(Level): 45 <0x7a18ab40>
08 04/17/14 2:00:21.319 Received Message from 56 (myweb2orbiter / ) to 81 (Lamp / Home Theater), type 1 id 184 Command:Set Level, retry none, parameters: <0x7a18ab40>
08 04/17/14 2:00:21.320 Parameter 76(Level): 50 <0x7a18ab40>
08 04/17/14 2:00:21.321 Received Message from 56 (myweb2orbiter / ) to 80 (Window Lights / Home Theater), type 1 id 184 Command:Set Level, retry none, parameters: <0x7a18ab40>
08 04/17/14 2:00:21.321 Parameter 76(Level): 45 <0x7a18ab40>
29
Users / using a script to launch scenarios
« on: April 15, 2014, 10:02:35 am »
I'd like to be able to trigger my predefined lighting and media scenarios with external scripts
I've read a bit about /usr/pluto/bin/MessageSend
but I'm not sure if that is what I am looking for or if that can only be used to update status rather than make the events happen
can anyone offer me any advice on how this is best accomplished?
I've read a bit about /usr/pluto/bin/MessageSend
but I'm not sure if that is what I am looking for or if that can only be used to update status rather than make the events happen
can anyone offer me any advice on how this is best accomplished?
30
Users / Re: gc100 and rs232 control
« on: January 28, 2014, 09:58:21 pm »
well I've started all over again with a fresh install of the latest 12.04 dvd image and now I have an extra PC to use as a media director in the room I am trying to control the AV equipment in.
A scenario now appears for my cable box on the orbiter screen so that is progress. I am guessing that is because I now have a dedicated media director in the room. Clicking on it just turns my orbiter screen black on my tv and the cable box input is not selected on my receiver as hoped.
I believe I have identified the problem though
after launching the scenario I see this
cat /var/log/pluto/socat_ttyS_48_0.log
2014/01/28 15:38:07.227962 length=8 from=586 to=593
.30110F.> 2014/01/28 15:38:07.427839 length=8 from=594 to=601
.301210.> 2014/01/28 15:38:16.232581 length=8 from=602 to=609
.30110E.> 2014/01/28 15:38:16.465356 length=8 from=610 to=617
.30120F.< 2014/01/28 15:41:20.038248 length=21 from=24 to=44
x02x00x37x38x37x45x03< 2014/01/28 15:41:27.066101 length=21 from=45 to=65
x02x00x37x38x44x30x03< 2014/01/28 15:41:29.079447 length=21 from=66 to=86
x02x00x37x38x37x45x03< 2014/01/28 15:41:36.098627 length=21 from=87 to=107
x02x00x37x38x32x41x03
My scenario is the output from 15:41...
It appears I am doing something wrong with the ruby commands. Earlier in the output you can see the results of sending commands with /usr/pluto/bin/TestSerialPort and you can see they look much different.
I am attempting to use ruby snippets like the following in the device template for my receiver:
conn_.Send("x02x00x37x38x37x45x03")
And as you can see they are not producing well formed output. Can anyone help me with the ruby?
A scenario now appears for my cable box on the orbiter screen so that is progress. I am guessing that is because I now have a dedicated media director in the room. Clicking on it just turns my orbiter screen black on my tv and the cable box input is not selected on my receiver as hoped.
I believe I have identified the problem though
after launching the scenario I see this
cat /var/log/pluto/socat_ttyS_48_0.log
2014/01/28 15:38:07.227962 length=8 from=586 to=593
.30110F.> 2014/01/28 15:38:07.427839 length=8 from=594 to=601
.301210.> 2014/01/28 15:38:16.232581 length=8 from=602 to=609
.30110E.> 2014/01/28 15:38:16.465356 length=8 from=610 to=617
.30120F.< 2014/01/28 15:41:20.038248 length=21 from=24 to=44
x02x00x37x38x37x45x03< 2014/01/28 15:41:27.066101 length=21 from=45 to=65
x02x00x37x38x44x30x03< 2014/01/28 15:41:29.079447 length=21 from=66 to=86
x02x00x37x38x37x45x03< 2014/01/28 15:41:36.098627 length=21 from=87 to=107
x02x00x37x38x32x41x03
My scenario is the output from 15:41...
It appears I am doing something wrong with the ruby commands. Earlier in the output you can see the results of sending commands with /usr/pluto/bin/TestSerialPort and you can see they look much different.
I am attempting to use ruby snippets like the following in the device template for my receiver:
conn_.Send("x02x00x37x38x37x45x03")
And as you can see they are not producing well formed output. Can anyone help me with the ruby?