New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gateway Mysensors problem #25768
Comments
Are you configuring it as a tcp gateway? After how many seconds is it ready? |
Please fill in the issue template completely. |
No i have connected it by USB # MySensors
mysensors:
gateways:
- device: '/dev/ttyACM0'
persistence_file: '/config/mysensors.json'
baud_rate: 38400
optimistic: false
persistence: true
version: '2.2' But how i can verify after what time it is ready? After rebot when HA start i try use device with gateway and it works. |
Connect to the gateway with a serial monitor and log the messages. Look for https://www.mysensors.org/download/serial_api_20 If you post the log I'll probably be able to see how long it takes. |
But by pc by Arduino IDE serial Monitor ? |
Yes Arduino IDE serial monitor should work. |
ok today i test it and show you all messages which is show... |
But in sketch i must have setup specific settings to show full info by serial....? |
this is my sketch:
|
|
Ok when come back to home from my work i test it and put in this issue all logs which is show... |
Or maybe add setup as option to config to user can own set timeout....But id not defined will be get deafult time. What you mean ? |
I don't want to add an option for this, but set a good default. |
Why dont want ? |
It increases maintenance and support burden. It increases the risk for bad configuration that may lead to problems which leads to support requests. Options increase the code complexity. Options decrease the flexibility of the code. The user should not have to care about this. |
OK. Wait for my info from serial monitor....thx |
This is all code after run on serial monitor
|
The gateway ready message seems to be sent within 1 second. I think we need logs from home assistant too to figure this out. Please set the logger component to log at debug level for the mysensors component and the mysensors package. https://www.home-assistant.io/components/mysensors/#debug-logging Then restart home assistant with the gateway plugged in. Don't monitor with the serial monitor at the same time. |
It is this ?
This is config logger:
|
Any news ? |
Try using the default baudrate. The Sensebender gateway doesn't run on 8 MHz. # MySensors
mysensors:
gateways:
- device: '/dev/ttyACM0'
persistence_file: '/config/mysensors.json'
version: '2.2' |
Still showing warning:
with this config:
|
And you have any solution? |
Have you checked that you can open a serial connection to the gateway with the correct user on your RPi4, and read the messages from the gateway? It looks like no messages are coming on the serial connection after opening it. |
Yes. I have added to gateway one node cover and normally controll this device. I hear how working relay. |
This is how the log should look after opening the connection to a serial gateway:
If you don't see the debug messages between opening the connection and the gateway says it's ready, there's something wrong with the serial output, or the interpretation of the output from the gateway. You were able to see these messages when connecting the serial monitor on the Arduino IDE to your gateway. My guess is then that something in your environment on the RPi affects the serial connection so the messages don't read as we expect them to. It's not likely that this is something in the code for the mysensors integration. I'm sorry that I can't help more. |
I have many clear config on my rpi4 because I test new rpi4 and have only this gateway on this hassio. I don't know where is a problem... |
I installed again on my SD Card image Hass.io for RPI4. And configure again MySensors Gateway and problem is the same. Nothing changed, Please help. System is clear install and not resolved problem. |
Also i done test on RPI3 and clear install image HassOS and the same problem. In configuration is only config for mysensors.
|
Anybody can help me.... Please |
I would try to run Home Assistant without hass.io on a computer where you know you can connect to the gateway and read from the serial connection to the gateway. If that works, we can rule out both the gateway and Home Assistant from the suspects. |
But can it be on RPI3 B+ with Home Assistant in Hasbian ? |
?? |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
I had a similar issue with my hass via Docker. I wasn't passing the correct serial device (i.e. ttyACM0) through to Home Assistant. I was getting the same log entries you are and it appeared to be working normally. I moved to pi4 recently and when I configured the proper USB serial device the timeout log entries went away. Just something to check in case you haven't already :-) |
I'll close this, since it seems the issue is environment setting specific and not controlled by the mysensors integration. |
Home Assistant release with the issue:
0.97
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io 170
Component/platform:
Description of problem:
Hi
I have this gateway:
https://www.mysensors.org/hardware/sensebender-gateway
and i have connected it to RPI4 with Hass.io
After restart i get info in logs:
But gateway works ok...
Maybe is any chance to add more time to timeout ?
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
The text was updated successfully, but these errors were encountered: