Upgrade pain

[Guest]

Originally posted by: <email address deleted>

WTF?

2012.01.23 04:18:27 3: CUN device opened
2012.01.23 04:18:27 1: CUL: Cannot define multiple CULs with identical first two digits (3E)
2012.01.23 04:18:27 1: define: CUL: Cannot define multiple CULs with identical first two digits (3E)
2012.01.23 04:18:27 3: Please define CUL first
2012.01.23 04:18:27 3: Please define CUL first

This worked for a rather ancient version (dated back to 2010) quite well, why isn't this supported anymore?!
-kai

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[rudolfkoenig]

                                                   

Pls dont be rude. The check was introduced to avoid multiple CULs answering the same FHT

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Guest]

Originally posted by: <email address deleted>

On 23.01.2012 09:12, Rudolf Koenig wrote:
> Pls dont be rude. The check was introduced to avoid multiple CULs answering the same FHT

Sorry for that. But a warning message would have been sufficient in
this case, epecially as it's not clear at that point if any FHT will
be used at all. This issue isn't listed in commandref.html either.
Breaking installations in this way is not really nice. (It's bad enough
to have to replace THE fhem machine in the middle of the night due to
a failing USB memory drive. Being subjected to odd error messages when
moving over the configuration does not really help )

Another issue: define initialUsbCheck notify global:INITIALIZED usb create
(which comes as a default) grabbed my USB2Serial converter that is attached
to my LCD -- multiple times:

2012.01.23 04:36:25 3: Opening CUL device /dev/ttyACM0
2012.01.23 04:36:26 3: Opening CUL_0 device /dev/ttyACM0
2012.01.23 04:36:26 3: Opening TCM310 device /dev/ttyUSB0
2012.01.23 04:36:26 3: Opening TCM120 device /dev/ttyUSB0
2012.01.23 04:36:26 3: Opening FHZ device /dev/ttyUSB0

This, of course, led to multiple issues (/dev/busware_cul dis- and reappering,
no access to the TV's serial interface for the module in question); I'm a bit
at loss why this happened, as on my development netbook, FHEM recognizes that
a device is already in use by, in my case, CUL433 and/or that it's not a CUL.

Above is from a Linux 3-based Debian Wheezy running on a PogoPlug Pink; pre-
viously I was running Debian Squeeze there, with an FHEM from 2010; could this
be ARM/Linux 3-related?
-kai

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com