I’m trying to use a nanoCUL(433) on my Raspi2 running openHABian with OH2.2.
The system was using a CUL(866) as device “ttyACM0” with no problems. Now I tried it with the nanoCUL as device “ttyUSB0” without success.
I checked with minicom that the device is correct and that the nanoCUL is sending the commands.
I put in the correct device definition into the culintertechno.cfg
I changed the file /etc/default/openhab2 to include:
In the logs (with DEBUG set for org.openhab.io.transport.cul) I get:
When starting OH
2018-01-02 21:59:34.558 [DEBUG] [io.transport.cul.internal.CULManager] - Registering class org.openhab.io.transport.cul.internal.network.CULNetworkHandlerImpl for device type network
2018-01-02 21:59:34.566 [DEBUG] [org.openhab.io.transport.cul ] - BundleEvent STARTED - org.openhab.io.transport.cul
2018-01-02 21:59:34.639 [WARN ] [io.transport.cul.CULLifecycleManager] - CUL config is NULL, doing nothing
2018-01-02 21:59:34.653 [DEBUG] [io.transport.cul.internal.CULManager] - Trying to open device serial:/dev/ttyUSB0 in mode SLOW_RF
2018-01-02 21:59:34.656 [DEBUG] [io.transport.cul.internal.CULManager] - Searching class for device type serial
2018-01-02 21:59:34.690 [DEBUG] [internal.serial.CULSerialHandlerImpl] - Opening serial CUL connection for /dev/ttyUSB0
No joy so far.
I checked this Raspi2 with my other CUL (which is connected as ttyACM0) and this one is working, but still nothing is send nor recieved by the nanoCUL connected at ttyUSB0.
The noticable difference in the logs is that the ttyACM0 connnected CUL reports its credit report back to openHAB.
And to make it clear again, the nanoCUL is working on the system when using it through minicom (which is closed while trying to send with openhHAB).
OThe test without the EXTRA_JAVA_OPTS failed also, however after putting them back in And doing a system restart it finally worked.
To sum it up I have changed the serial settings through the openhabian config tool (selection 35) using the first (disable console) and third ( Add common serial ports…). I manually added the ttyUSB0 also to etc/default/openhab2.
Do not forget to do a complete restart!
I am curious, could you check for me what the ttyUSB0’s group/access rights are now that it is working?
I wonder if “-Dgnu.io.rxtx.SerialPorts=/dev/ttyUSB0” and a reboot changed the rights?
If so, I might try the /dev/serial/by-id method too.
No, the group settings did not change at all!
Actually, I’m not sure anymore why it worked at last, since I’m trying to move the nanoCUL to my productive system (Raspi3) and am observing the same problem again.
Found it by comparing my Raspi2(working) with the Raspi3(not working), after removing the disabeling of BT (probably done using openhabian-config and doing all selections under selection 35) AND a restart it finally worked.
One thing remained, although not needed for me, I could only get one stick to work while NO other was connected. How can you work with two CUL-sticks?
but how to make the CUL display anything?
I can open the serial, that is no problem, but do I need to give it a command to then make it spit out what is it receive to me?
You wanted the recieved messages to be displayed, of course you need to send something while trying to recieve. In your case: RING TO BELL. But please silently, I want to sleep now!