maxwellhadley / node-red-contrib-rfxcom

node-RED nodes to access an RFXtrx433 transceiver
BSD 2-Clause "Simplified" License
22 stars 13 forks source link

rfxcom is connected to device but not working on node-red #58

Closed lpt2007 closed 6 years ago

lpt2007 commented 6 years ago

Now I have another problem:

I see my rfxcom but in node red show disconnected. Port is set to /dev/ttyUSB0.

[ 2.134489] usb 1-1.5: new full-speed USB device number 4 using dwc_otg [ 2.259199] usb 1-1.5: New USB device found, idVendor=0403, idProduct=6001 [ 2.259210] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2.259216] usb 1-1.5: Product: RFXtrx433 [ 2.259222] usb 1-1.5: Manufacturer: RFXCOM [ 2.259228] usb 1-1.5: SerialNumber: A1XFL0Y9 [ 4.431352] usbcore: registered new interface driver brcmfmac [ 5.581569] usbcore: registered new interface driver usbserial [ 5.581670] usbcore: registered new interface driver usbserial_generic [ 5.581755] usbserial: USB Serial support registered for generic [ 5.614937] usbcore: registered new interface driver ftdi_sio [ 5.615046] usbserial: USB Serial support registered for FTDI USB Serial Device [ 5.615331] ftdi_sio 1-1.5:1.0: FTDI USB Serial Device converter detected [ 5.615537] usb 1-1.5: Detected FT232RL [ 5.616439] usb 1-1.5: FTDI USB Serial Device converter now attached to ttyUSB0

maxwellhadley commented 6 years ago

You haven't sent the Node-RED log output, but I suspect the user running Node-RED is not a member of the dialout group so doesn't have the appropriate permissions to access the port. In Node-RED, go to the config dialog for the RFXCOM device, i.e. where you enter the device path, and enable debug output using the checkbox (recently added). Then have a look at the [rfxcom] debug messages on Node-RED's console output

lpt2007 commented 6 years ago

Where [rfxcom] debug messages should apear? Under the debug in top right corner?

If this is the right place, there is nothing.

bdw only user on my sistem is root in the group root.

root@hassio:/# users root

root@hassio:/# groups root root

maxwellhadley commented 6 years ago

If you start Node-RED from the command line, debug messages and other console output will appear on the terminal window. If it is started as a daemon or service of some sort, they will go to a log file somewhere. Exactly where depends on which mechanism the OS is using. The messages don't appear on the debug panel, because they come from the node-rfxcom package which does not know anything about Node-RED.

I have never used Docker, so I don't know where these messages might be ending up - possibly /var/log, or /usr/share/logs or somewhere like that, but that is just a guess. Try asking on the Node-RED forum, as it's more of a general question. https://discourse.nodered.org

lpt2007 commented 6 years ago

I slove the problem.

Solution is there: https://github.com/hassio-addons/addon-node-red/issues/10

Thanks a lot for your help.

maxwellhadley commented 6 years ago

Glad you got it working!