[domuslink-developers] heyuenginev12 branch

[Brad]

I have updated some more of the changes for V12. This branch has the
changes for verifying the heyu engine is running for domus.Link.
Previously domus.Link required the start_engine AUTO directive in the
heyu config file. With the advent of V1.2 and standard heyu config
parsing, this may not be the case. domus.Link checks for the engine
and if not brings up the start heyu screen. If only the relay is
running it will ask to start and only start the heyu engine. In other
cases it will start both the relay and engine if not auto started.\
In another related item to heyu config compatibility, I added the
detection of a schedule file not being defined. domus.Link required
this as well. Now domus.Link will operate without a schedule file and
has the ability to add it in the heyu config.
Other updates are for file writing error handling and also php header
redirection handling cleanup. There are some other stability items as
well that I found and updated.
These enhancements will help with domus.Link compatibility with any
heyu installation.

Test it out.

Brad

--
You received this message because you are subscribed to the Google Groups "domuslink-developers" group.
To post to this group, send an email to domuslink-...@googlegroups.com.
To unsubscribe from this group, send email to domuslink-develo...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/domuslink-developers?hl=en-GB.

[Cyril Duveau]

Hi,

Just testing it (r744). It does not see Heyu running while it should:
3121 ? Ss 0:00 heyu_relay bin/heyu -4 start
3123 ? Ss 0:00 heyu_engine in/heyu -4 start
3127 ? Ss 0:00 heyu_engine in/heyu -4 engine

But then I click on "start", I get:
Array
(
[0] => heyu_engine is running - use 'heyu restart' to reconfigure
)

Any clue?
Cyril

[Brad]

Yep, I found that one already and have fix. Just testing some other
things that I broke and am fixing before I commit.

Brad

[Brad]

Many things broken when I changed error handling to exceptions. Fixed
ones that I could find.

Many errors in the web server log for PHP Notice, Parse and Warnings.
Fixed as many as I could find.

Should be very error tolerant and if a real error is found it should
put up the 'error' page.

Test as many items and configurations as possible.

heyuenginev12 r746.

Brad

[Brad]

Oh, and please review your apache error log for the PHP error issues
and post them here for me.

Brad

[Philippe Carlier]

Hi Brad,

I've just deployed heyuenginev12 branch.

First time:
    I got a right error.
/var/www/domus.Link/db/aliasmap not found or not rewritable !
    So, i fix right ...  and hit F5 to reload page. Problem seems to be still present (in fact, when you're forwarded to an error page, you stay on error page when you click F5 ...).
    You must click home for reload and skip error ...

Second time :
    I got and error on uploading sched file. I try to reproduce it...
  
Now, it's okay,

Some questions :
* is there an installation guide ?
* is there a backup mechanism before migration ?

Philippe


Domus display

[Cyril Duveau]

Le samedi 15 mai 2010 à 09:48 +0200, Philippe Carlier a écrit :
> Some questions :
> * is there an installation guide ?

Yep, Brad is keeping the doc/INSTALL file updated, we need to remember
to read it... (I made the same error earlier).

Cyril

[Brad]

I think with the many changes that have been done to domus.Link setup,
we should implement Philippe's request of a diagnostic page. He
entered issue 33 a while back to ask for detecting these issues. A lot
of the work is already in domus for the feature as you see from the
errors you get, but detecting them on startup would be better.

Brad

[Cyril Duveau]

Hi Brad,


Error log from today's games:
==================
[Sat May 15 16:16:03 2010] [error] [client 127.0.0.1] PHP Notice:
Undefined index: setupverify
in /home/cyril/public_html/domus.Link/utility/setupverify.php on line
36, referer: http://domus.icaunais.homelinux.net/index.php
[Sat May 15 16:17:09 2010] [error] [client 127.0.0.1] PHP Notice:
Undefined index: setupverify
in /home/cyril/public_html/domus.Link/utility/setupverify.php on line
36, referer: http://domus.icaunais.homelinux.net/login.php?from=index
[Sat May 15 16:17:46 2010] [error] [client 127.0.0.1] PHP Notice:
Undefined index: directive
in /home/cyril/public_html/domus.Link/theme/default/tpl/heyuconf_view.tpl on line 8, referer: http://domus.icaunais.homelinux.net/admin/utility.php?action=execute
[Sat May 15 16:17:46 2010] [error] [client 127.0.0.1] PHP Notice:
Undefined index: comment
in /home/cyril/public_html/domus.Link/theme/default/tpl/heyuconf_view.tpl on line 10, referer: http://domus.icaunais.homelinux.net/admin/utility.php?action=execute
[Sat May 15 16:17:46 2010] [error] [client 127.0.0.1] PHP Notice:
Undefined index: value
in /home/cyril/public_html/domus.Link/theme/default/tpl/heyuconf_view.tpl on line 12, referer: http://domus.icaunais.homelinux.net/admin/utility.php?action=execute
[Sat May 15 16:18:02 2010] [error] [client 127.0.0.1] PHP Notice:
Undefined offset: 0
in /home/cyril/public_html/domus.Link/lib/func/cmd.func.php on line 42,
referer: http://domus.icaunais.homelinux.net/admin/frontend.php
[Sat May 15 16:18:02 2010] [error] [client 127.0.0.1] PHP Fatal error:
Uncaught exception 'Exception'
in /home/cyril/public_html/domus.Link/lib/func/cmd.func.php:42\nStack
trace:\n#0 /home/cyril/public_html/domus.Link/lib/func/cmd.func.php(99):
execute_cmd('/usr/local/bin/...')\n#1 /home/cyril/public_html/domus.Link/index.php(33): heyu_ctrl('stop')\n#2 {main}\n thrown in /home/cyril/public_html/domus.Link/lib/func/cmd.func.php on line 42, referer: http://domus.icaunais.homelinux.net/admin/frontend.php
[Sat May 15 16:18:02 2010] [error] [client 127.0.0.1] File does not
exist: /home/cyril/public_html/domus/favicon.ico
[Sat May 15 16:18:05 2010] [error] [client 127.0.0.1] File does not
exist: /home/cyril/public_html/domus/favicon.ico
[Sat May 15 16:19:20 2010] [error] [client 127.0.0.1] PHP Notice:
Undefined index: setupverify
in /home/cyril/public_html/domus.Link/utility/setupverify.php on line
36, referer: http://domus.icaunais.homelinux.net/index.php
[Sat May 15 16:22:30 2010] [error] [client 127.0.0.1] PHP Notice:
Undefined index: setupverify
in /home/cyril/public_html/domus.Link/utility/setupverify.php on line
36, referer: http://domus.icaunais.homelinux.net/index.php
[Sat May 15 16:22:32 2010] [error] [client 127.0.0.1] PHP Notice:
Undefined index: directive
in /home/cyril/public_html/domus.Link/theme/default/tpl/heyuconf_view.tpl on line 8, referer: http://domus.icaunais.homelinux.net/index.php
[Sat May 15 16:22:32 2010] [error] [client 127.0.0.1] PHP Notice:
Undefined index: comment
in /home/cyril/public_html/domus.Link/theme/default/tpl/heyuconf_view.tpl on line 10, referer: http://domus.icaunais.homelinux.net/index.php
[Sat May 15 16:22:32 2010] [error] [client 127.0.0.1] PHP Notice:
Undefined index: value
in /home/cyril/public_html/domus.Link/theme/default/tpl/heyuconf_view.tpl on line 12, referer: http://domus.icaunais.homelinux.net/index.php
[Sat May 15 16:22:39 2010] [error] [client 127.0.0.1] PHP Notice:
Undefined index: directive
in /home/cyril/public_html/domus.Link/theme/default/tpl/heyuconf_edit.tpl on line 17, referer: http://domus.icaunais.homelinux.net/admin/heyu.php
[Sat May 15 16:22:39 2010] [error] [client 127.0.0.1] PHP Notice:
Undefined index: comment
in /home/cyril/public_html/domus.Link/theme/default/tpl/heyuconf_edit.tpl on line 19, referer: http://domus.icaunais.homelinux.net/admin/heyu.php
[Sat May 15 16:22:39 2010] [error] [client 127.0.0.1] PHP Notice:
Undefined index: value
in /home/cyril/public_html/domus.Link/theme/default/tpl/heyuconf_edit.tpl on line 21, referer: http://domus.icaunais.homelinux.net/admin/heyu.php
[Sat May 15 16:22:55 2010] [error] [client 127.0.0.1] PHP Notice:
Undefined index: directive
in /home/cyril/public_html/domus.Link/theme/default/tpl/heyuconf_view.tpl on line 8, referer: http://domus.icaunais.homelinux.net/admin/heyu.php?action=edit
[Sat May 15 16:22:55 2010] [error] [client 127.0.0.1] PHP Notice:
Undefined index: comment
in /home/cyril/public_html/domus.Link/theme/default/tpl/heyuconf_view.tpl on line 10, referer: http://domus.icaunais.homelinux.net/admin/heyu.php?action=edit
[Sat May 15 16:22:55 2010] [error] [client 127.0.0.1] PHP Notice:
Undefined index: value
in /home/cyril/public_html/domus.Link/theme/default/tpl/heyuconf_view.tpl on line 12, referer: http://domus.icaunais.homelinux.net/admin/heyu.php?action=edit
[Sat May 15 19:49:57 2010] [error] [client 127.0.0.1] PHP Notice:
Undefined index: setupverify
in /home/cyril/public_html/domus.Link/utility/setupverify.php on line
36, referer: http://domus.icaunais.homelinux.net/index.php?page=home
=================

Cyril

[Brad]

Since we are still in development, I did not update the other language
files. Most of the errors are your system trying to get the French
translation for most of the new headings. I did see one item in the
log for an uncaught exception when executing heyu ctrl. I added the
error capture and display for that.

Try the latest from the branch.

Brad

> For more options,...
>
> read more »

[Brandt Daniels]

r750:

1. On the main screen I see undefined, I think '[undefined]' is not suppose to be visible:
Current heyu configuration is: [undefined] in directory /volume1/opt/etc/heyu/


2. Tried to edit the aliasmap manually to get a new alias I added up near the top faster than clicking up a 100 times and it caused a pg_grep error for line 192 somewhere..sorry forgot to copy and paste the error, but I had to restart apache to fix it. Maybe this can be caught by dL...Or automatically resort them by HU upon adding a new alias ;)


3. For the heyu status 'reload' in the footer bar to say 'restart' to better reflect the actual command.

4. When clicking heyu stop:
Exec: heyu stop
I could not kill heyu.aux.ttyUSB1 (pid = 23963)
then trying to restart:
Fatal error: Uncaught exception 'Exception' with message 'State engine is not running.' in /volume1/web/heyuenginev12/lib/func/cmd.func.php:42 Stack trace: #0 /volume1/web/heyuenginev12/lib/func/cmd.func.php(197): execute_cmd('/volume1/opt/bi...') #1 /volume1/web/heyuenginev12/lib/classes/location.class.php(145): on_state('A13') #2 /volume1/web/heyuenginev12/lib/classes/location.class.php(98): location->buildModuleTable(Object(Alias)) #3 /volume1/web/heyuenginev12/lib/classes/location.class.php(64): location->buildLocationTable('Entryway', Array, 'localized') #4 /volume1/web/heyuenginev12/index.php(85): location->buildLocations('', 'localized') #5 {main} thrown in /volume1/web/heyuenginev12/lib/func/cmd.func.php on line 42


Sorry, can't find where they put the apache logs on the NAS that i'm running heyu on...
DiskStation> cd /usr/syno/apache/
DiskStation> ls
bin      conf     modules


-Brandt

[Brad]

1 - I put that in string in when I can't find a section directive.
Maybe it should read [notitle].

2 - Need to test this more. Please provide the steps you performed and
the state of the system.

3 - Even though the heyu command is restart, it does not stop and
restart, it actually re-reads the config files. Hnece - reload.

4 - I believe this is due to heyu being started outside of domus.Link.
When that happens different user ids are present on the process.
domus.Link is tied to the web server user and can only control
processes started under that user. I assume you where doing some
command line updates and used it to stop and restart. Due to the
process permission constructs in Linux, there is not a secure way
around this and I do not want to implement a chroot to handle this as
it is a bad thing for a web app.
Start and stops should be done from domus if you want it to have
control.

Brad

On May 15, 5:35 pm, Brandt Daniels <brandtdani...@gmail.com> wrote:
> r750:
>
> 1. On the main screen I see undefined, I think '[undefined]' is not
> suppose to be visible:
> Current heyu configuration is: [undefined] in directory
> /volume1/opt/etc/heyu/
>
> 2. Tried to edit the aliasmap manually to get a new alias I added up
> near the top faster than clicking up a 100 times and it caused a pg_grep
> error for line 192 somewhere..sorry forgot to copy and paste the error,
> but I had to restart apache to fix it. Maybe this can be caught by
> dL...Or automatically resort them by HU upon adding a new alias ;)
>
> 3. For the heyu status 'reload' in the footer bar to say 'restart' to
> better reflect the actual command.
>
> 4. When clicking heyu stop:
> Exec: heyu stop
> I could not kill heyu.aux.ttyUSB1 (pid = 23963)
> then trying to restart:

> *Fatal error*: Uncaught exception 'Exception' with message 'State engine

> is not running.' in /volume1/web/heyuenginev12/lib/func/cmd.func.php:42
> Stack trace: #0 /volume1/web/heyuenginev12/lib/func/cmd.func.php(197):
> execute_cmd('/volume1/opt/bi...') #1
> /volume1/web/heyuenginev12/lib/classes/location.class.php(145):
> on_state('A13') #2
> /volume1/web/heyuenginev12/lib/classes/location.class.php(98):
> location->buildModuleTable(Object(Alias)) #3
> /volume1/web/heyuenginev12/lib/classes/location.class.php(64):
> location->buildLocationTable('Entryway', Array, 'localized') #4
> /volume1/web/heyuenginev12/index.php(85): location->buildLocations('',
> 'localized') #5 {main} thrown in

> */volume1/web/heyuenginev12/lib/func/cmd.func.php* on line *42*

[Brandt Daniels]

On 5/16/10 7:45 AM, Brad wrote:
> 1 - I put that in string in when I can't find a section directive.
> Maybe it should read [notitle].
>

Can we just have nothing appear when it is undefined? If not, I think
undefined is better than notitle.

> 2 - Need to test this more. Please provide the steps you performed and
> the state of the system.
>

I was on the alias edit page, and was moving an item up from the bottom
of the list, and got frusterated at how long it takes so I just tried to
edit the aliasmap manually and after saving the file, i clicked on the
alias page again, but it didn't change anything, so I clicked up on the
object again, and thats when i got the error.

> 3 - Even though the heyu command is restart, it does not stop and
> restart, it actually re-reads the config files. Hnece - reload.
>

So clicking reload in dL causes two things? Heyu restart, and dL reload
config?

> 4 - I believe this is due to heyu being started outside of domus.Link.
> When that happens different user ids are present on the process.
> domus.Link is tied to the web server user and can only control
> processes started under that user. I assume you where doing some
> command line updates and used it to stop and restart. Due to the
> process permission constructs in Linux, there is not a secure way
> around this and I do not want to implement a chroot to handle this as
> it is a bad thing for a web app.
> Start and stops should be done from domus if you want it to have
> control.
>

Starting it through dL doesn't seem to start heyu_aux:

DiskStation> ps aux | grep -i heyu
11872 root 612 S heyu_relay
11874 root 972 S heyu_engine
11875 root 684 S heyu_aux t
26804 root 328 S grep -i heyu
DiskStation> heyu stop
DiskStation> ps aux | grep -i heyu
26807 root 320 S grep -i heyu
(Started heyu through dL here)
DiskStation> ps aux | grep -i heyu
26822 nobody 552 S heyu_relay t/bin/heyu -c
/volume1/opt/etc/heyu/x10.co
26824 nobody 748 S heyu_engine /bin/heyu -c
/volume1/opt/etc/heyu/x10.co
(Stopped heyu through dL here)
DiskStation> ps aux | grep -i heyu
DiskStation> heyu start
starting heyu_relay
starting heyu_engine
starting heyu_aux

[Brad]

1 - We can go back to blank.

2 - Still don't see how you can get an error doing this. Please give
me the filenames you touched and the state of the system, i.e. heyu
running, a browser up and loaded with Dl while editing...etc.

3 - reload only does the heyu restart command. man heyu for more info.

4 - Do you have 'start_engine auto' in your config file? If you do,
the aux process should be started automatically and if it doesn't in
this case it's not an issue with domus as we just call heyu start.
Otherwise if you don't have the engine auto started, domus does not
look for the aux process yet.

[Brandt Daniels]

On 5/17/10 6:49 AM, Brad wrote:
> 1 - We can go back to blank.
>
> 2 - Still don't see how you can get an error doing this. Please give
> me the filenames you touched and the state of the system, i.e. heyu
> running, a browser up and loaded with Dl while editing...etc.
>

Ah, I can manually edit the order of the aliases by editing x10.conf not
db/aliasmap :P

> 3 - reload only does the heyu restart command. man heyu for more info.
>
> 4 - Do you have 'start_engine auto' in your config file? If you do,
> the aux process should be started automatically and if it doesn't in
> this case it's not an issue with domus as we just call heyu start.
> Otherwise if you don't have the engine auto started, domus does not
> look for the aux process yet.
>

Yes:
START_ENGINE AUTO

[Brad]

I see, aliasmap won't get you anywhere since it is used as seed.
Modifications happen to it only when edited through the interface. You
still shouldn't get any errors if it matches an alias in the config
file otherwise you just get an other/unknown combo. Anyway I hope that
is good.

Well, since you have the auto on the engine, the aux should start as
per the heyu documentation. Don't understand why it wouldn't. Did you
have a bad state with part of heyu started on the command line user
and part as the web server user? Always good to kill it all and start
from domus.

Brad

[Brandt Daniels]

Putting a comment in the config file causes an error:

# Alias
# Alias directives
etc...

Exec: Load Cache
Error loading /volume1/opt/etc/heyu/x10.conf - line , Alias line does not have enough elements [Alias]

[Brad]

Thanks, got a fix for that one in the works. This can happen in the
schedule file as well.

Please, keep mangling the file too see what bad things are not caught.
We'll get the release to be very stable and hopefully more users on
domus as they will have a better experience.

Brad

[Brad]

Fix applied for the comment issue with a directive for aliases (not
other directives as we do not decode those) and the schedule file
operators.

heyuenginev12 r751

Brad

[Brandt Daniels]

Thanks that works now.

However, I'm still having trouble with heyu_aux when starting/restarting
heyu via dL (and yes I have the directive start_engine auto in my config):

via dL:

DiskStation> ps aux | grep -i heyu

28952 nobody 916 S heyu_relay t/bin/heyu -c
/volume1/opt/etc/heyu/x10.co
28954 nobody 1104 S heyu_engine /bin/heyu -c
/volume1/opt/etc/heyu/x10.co

via command line:
DiskStation> heyu stop

DiskStation> heyu start
starting heyu_relay
starting heyu_engine
starting heyu_aux

DiskStation> ps aux | grep -i heyu

29324 root 552 S heyu_relay
29326 root 756 S heyu_engine
29327 root 580 S heyu_aux t

[Brad]

Do you have heyu logging enabled to a file? If so check it. You might
have permissions problem with the webserver user opening the usb port
to your RFXCOMM that I believe you use.

Brad

[Brandt Daniels]

Yes it is logged to a file. All that was in it is:

05/18 20:44:09 Engine started


I have a w800usb btw.

-Brandt

[Brad]

Check the syslog as well. Have you ever been able to have the aux
start with any version of domus?

> ...
>
> read more »

[Brandt]

Nothing in any logs...never thoroughly tested this before

[Brad]

Well, it looks like you will need to look into that deeper. Since you
can start with a root user but not another is a red flag for
permissions on the device access.

As far as domus, this is not it's issue.

Well, if we are pretty far with tests for this branch (I did a some
more testing last night as well) I will get this into the prev12
branch so I can start on the next feature.

Brad

[Brandt Daniels]

Here are my perms for the hd11a and the w800usb

crw-rw-rw-    1 root     root     188,   0 May 19 08:27 ttyUSB0
crw-r--r--    1 root     root     188,   1 May  2 17:32 ttyUSB1

[Brandt Daniels]

r752 seems to have trouble with blank lines between directives:

Exec: Load Cache
Error loading /volume1/opt/etc/heyu/x10.conf - line 34, Directive line has too few elements, must be 2 or greater - []


RCS_DECODE [H]
ACK_HAILS NO
AUTOFETCH YES
ARM_MAX_DELAY 180

#DATE_FORMAT directive
#LOGDATE_YEAR directive
#TAILPATH directive


I list all available directives and comment out the ones I don't need. That way I don't forget about my available options.

[Brandt Daniels]

Here is another:

Exec: Load Cache
Error loading /volume1/opt/etc/heyu/x10.conf - line 103, Directive line has too few elements, must be 2 or greater - []


#POWERFAIL_UPDATE directive
#AUTO_WAIT directive
(line 103)
# Alias directives

# A - Audio, Announcements, Alarms

[Brandt Daniels]

removing the blank line just makes it complain about the next blank line. r752 is pretty much unusable for me.

-Brandt

[Brad]

I will revert that last change as it causes more issues and is not
really needed yet.

As far as the usb stuff, I don't have any usb devices for heyu so I
can't help you. Please do some google research on usb handling in
Linux. It is not straight forward like serial ports. The kernel module
has some very specific constructs for usb access.


Brad

On May 19, 11:19 am, Brandt Daniels <brandtdani...@gmail.com> wrote:
> removing the blank line just makes it complain about the next blank line.
> r752 is pretty much unusable for me.
>
> -Brandt
>

> On Wed, May 19, 2010 at 9:16 AM, Brandt Daniels <brandtdani...@gmail.com>wrote:
>
> > Here is another:
>
> > Exec: Load Cache
> > Error loading /volume1/opt/etc/heyu/x10.conf - line 103, Directive line has
> > too few elements, must be 2 or greater - []
>
> > #POWERFAIL_UPDATE directive
> > #AUTO_WAIT directive
> > (line 103)
> > # Alias directives
>
> > # A - Audio, Announcements, Alarms
>

> > On Wed, May 19, 2010 at 9:13 AM, Brandt Daniels <brandtdani...@gmail.com>wrote:
>
> >> r752 seems to have trouble with blank lines between directives:
>
> >> Exec: Load Cache
> >> Error loading /volume1/opt/etc/heyu/x10.conf - line 34, Directive line has
> >> too few elements, must be 2 or greater - []
>
> >> RCS_DECODE [H]
> >> ACK_HAILS NO
> >> AUTOFETCH YES
> >> ARM_MAX_DELAY 180
>
> >> #DATE_FORMAT directive
> >> #LOGDATE_YEAR directive
> >> #TAILPATH directive
>
> >> I list all available directives and comment out the ones I don't need.
> >> That way I don't forget about my available options.
>

> >> On Wed, May 19, 2010 at 8:48 AM, Brandt Daniels <brandtdani...@gmail.com>wrote:
>
> >>> Here are my perms for the hd11a and the w800usb
>
> >>> crw-rw-rw-    1 root     root     188,   0 May 19 08:27 ttyUSB0
> >>> crw-r--r--    1 root     root     188,   1 May  2 17:32 ttyUSB1
>

[Cyril Duveau]

Brandt,

Maybe you need to give write access to ttyUSB1?

Cyril

[Brandt Daniels]

I don't understand why anything would need to write to a receive only device...

[Cyril Duveau]

Some RFXCOM devices can send data, just give it a try ;)

[Brandt Daniels]

ok r753 works again

and adding "og+w" to ttyUSB1 allowed the webserver to start heyu_aux

crw-rw-rw-    1 root     root     188,   0 May 19 13:36 ttyUSB0
crw-rw-rw-    1 root     root     188,   1 May  2 17:32 ttyUSB1

DiskStation> ps aux | grep -i heyu

22974 nobody      552 S   heyu_relay t/bin/heyu -c /volume1/opt/etc/heyu/x10.co
22976 nobody      748 S   heyu_engine /bin/heyu -c /volume1/opt/etc/heyu/x10.co
22977 nobody      580 S   heyu_aux opt/bin/heyu -c /volume1/opt/etc/heyu/x10.co

[Brandt Daniels]

Please check Issue 44: http://code.google.com/p/domuslink/issues/detail?id=44 before merging.


-Brandt

[Brad]

I'll put in a check to see if it is running when you click stop and it
is already stopped. Heyu exits with an error code when it is already
stopped but doesn't put any text out.

On May 19, 4:28 pm, Brandt Daniels <brandtdani...@gmail.com> wrote:
> Please check Issue 44:http://code.google.com/p/domuslink/issues/detail?id=44before merging.
>
> -Brandt

>
> On Wed, May 19, 2010 at 2:23 PM, Brandt Daniels <brandtdani...@gmail.com>wrote:
>
> > ok r753 works again
>
> > and adding "og+w" to ttyUSB1 allowed the webserver to start heyu_aux
>
> > crw-rw-rw-    1 root     root     188,   0 May 19 13:36 ttyUSB0
> > crw-rw-rw-    1 root     root     188,   1 May  2 17:32 ttyUSB1
>
> > DiskStation> ps aux | grep -i heyu
> > 22974 nobody      552 S   heyu_relay t/bin/heyu -c /volume1/opt/etc/heyu/
> > x10.co
> > 22976 nobody      748 S   heyu_engine /bin/heyu -c /volume1/opt/etc/heyu/
> > x10.co
> > 22977 nobody      580 S   heyu_aux opt/bin/heyu -c /volume1/opt/etc/heyu/
> > x10.co
>

> > On Wed, May 19, 2010 at 10:29 AM, Cyril Duveau <linux4cy...@free.fr>wrote:
>
> >> Some RFXCOM devices can send data, just give it a try ;)
>
> >> Le mercredi 19 mai 2010 à 09:47 -0700, Brandt Daniels a écrit :
> >> > I don't understand why anything would need to write to a receive only
> >> > device...
>

> >> > On Wed, May 19, 2010 at 9:28 AM, Cyril Duveau <linux4cy...@free.fr>

> >> > wrote:
> >> >         Brandt,
>
> >> >         Maybe you need to give write access to ttyUSB1?
>
> >> >         Cyril
>
> >> >         Le mercredi 19 mai 2010 à 08:48 -0700, Brandt Daniels a
> >> >         écrit :
>
> >> >         > Here are my perms for the hd11a and the w800usb
>
> >> >         > crw-rw-rw-    1 root     root     188,   0 May 19 08:27
> >> >         ttyUSB0
> >> >         > crw-r--r--    1 root     root     188,   1 May  2 17:32
> >> >         ttyUSB1
>

> >> >         > On Wed, May 19, 2010 at 6:28 AM, Brad <crush...@yahoo.com>

> ...
>
> read more »

[Brad]

Fixed issue 44.

Merged and ended branch. Changes are now on prev12.

This thread is done.

Brad