Closed gijbelsy closed 4 years ago
Some suggestions to go on:
2018-10-30 23:55:35,084 INFO: Authenticating: username
2018-10-30 23:55:35,113 INFO: Succesfully connected to MQTT broker.
user
and pwd
in the config file?mosquitto_pub -u username -P password -t 'enocean/switch1/temp' -m 21
I don't see any information about the mqtt connection in the --debug output. Only when I uncomment just the user (or pwd) field in the config file, --debug promts me that there is a config error (so config file is read). I don't use ssl neither pass / username I did some further testing: When I set the parameter mqtt_keepalive = 0 to mqtt_keepalive = 1 it works. Also I need log_learn = 1 otherwise I get the 'teach' command issue. Strange because the switch has a F6-02-02 profile, which is standard.
I don't see any information about the mqtt connection in the --debug output.
If you do not use authentication, you should still see a resulting message whether connection was established successfully or not.
I did some further testing: When I set the parameter mqtt_keepalive = 0 to mqtt_keepalive = 1 it works.
This defines the timeout in seconds, allowed between communications with the broker. It can be turned off by setting the interval to 0.
Potentially your mqtt broker does not support this? What mqtt broker to you use?
Also I need log_learn = 1 otherwise I get the 'teach' command issue. Strange because the switch has a F6-02-02 profile, which is standard.
In my perspective, this is an issue in the enocean library, which this is based on.
What mqtt broker to you use?
Mosquito on Windows server
In my perspective, this is an issue in the enocean library, which this is based on.
Why is this still giving me the teach issue. The F6 02 02 is listed in the EEP.xml?
the debug log shows me
2020-03-16 20:54:15,975 DEBUG: enocean/switch1: Sent MQTT: {"R1": 0, "EB": 0, "R2": 0, "SA": 0, "T21": true, "NU": false}
But the messages are never received by the mqtt broker. I've checked the config, and the mqtt settings seem OK, also MQTT IP address is pingable from device. What can be wrong?