-
|
What is the syntax for configuring the path to a serial USB - Modbus adaptor?
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 9 replies
-
|
Hi, That is the correct syntax. You can find the correct device and it's path from settings->system->hardware->3 dots->all hardware, then click on the correct device and the device path is shown |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, but it says exactly the same as I wrote /dev/ttyUSB0 (which has also worked flawlessly when using modbus configured directly in configuration.yaml) ... what could cause the "Unknown error occured"? |
Beta Was this translation helpful? Give feedback.
-
|
Hi, are you running 2023.2? It might have something to do with the latest changes. I dont have the setup/time to test it right now. If you turn on debug logging on, is there any hints in the logs? |
Beta Was this translation helpful? Give feedback.
-
|
Only thing that comes to mind is that your device is busy. Make sure you don't have anything remaining in your config that uses that device. |
Beta Was this translation helpful? Give feedback.
-
|
I experience the same when trying to add with Modbus TCP. Running the latest 2023.2.1.
|
Beta Was this translation helpful? Give feedback.
-
|
This issue should now be fixed. |
Beta Was this translation helpful? Give feedback.
-
|
I had this issue as well. Now different error. "Invalid Response from Device" HA verson: I am using WS-17286 RS485 USB converter. Log message from HA:Logger: homeassistant.util.async_ Detected blocking call to sleep inside the event loop. This is causing stability issues. Please report issue to the custom integration author for nilan doing blocking calls at custom_components/nilan/config_flow.py, line 59: result = client.read_holding_registers(Step 1: Configuration information entered. Step 2: After submit. Step 3: HA logs |
Beta Was this translation helpful? Give feedback.
-
|
Hi, this is probably caused by not using asyncronous function calls, but should not prevent the device to be added. I suspect you have hardware issues in your setup. Can you test if it works with qmodmaster etc.? |
Beta Was this translation helpful? Give feedback.
-
|
Should have checked wiring first :) Fixed that and all is well! |
Beta Was this translation helpful? Give feedback.
-
|
Excellent, also working here now. Guess it's not a discussion topic, but should have been an issue. Thanks for the quick resolution @veista |
Beta Was this translation helpful? Give feedback.
Hi,
That is the correct syntax. You can find the correct device and it's path from settings->system->hardware->3 dots->all hardware, then click on the correct device and the device path is shown