search

bbqkees / ems-esp-domoticz-plugin

Domoticz plugin for the EMS Wi-Fi Gateway with Proddy's EMS-ESP firmware
MIT License
7 stars 8 forks source link

Error: (EMS bus Wi-Fi Gateway) No transport, write directive to '<mqtt server here>' ignored #5

Closed hlugt closed 4 years ago

hlugt commented 4 years ago

Hello, I get errors in the domoticz log when enabling the plugin Error: (EMS bus Wi-Fi Gateway) No transport, write directive to 'mqtt-service' ignored. I run Domoticz in a Kubernetes (K3S) cluster, so that is why the mqtt-service. If I change it to the assigned external ip-address, the result is the same (but with the ip instead of mqtt-service ofcourse).

Other mqtt messages work ok (with installed MQTT Client Gateway with LAN interface).

Can you advise on what can be done?

2020-01-25 20:20:53.171 (EMS bus Wi-Fi Gateway) MqttClient::Open
2020-01-25 20:20:53.171 (EMS bus Wi-Fi Gateway) Protocol set to: 'MQTT'.
2020-01-25 20:20:53.171 (EMS bus Wi-Fi Gateway) Transport set to: 'TCP/IP', mqtt-service:1883.
2020-01-25 20:20:53.174 (EMS bus Wi-Fi Gateway) Connect directive received, action initiated successfully.
2020-01-25 20:20:53.224 (EMS bus Wi-Fi Gateway) MqttClient::onConnect
2020-01-25 20:20:53.224 (EMS bus Wi-Fi Gateway) Successful connect to: mqtt-service:1883
2020-01-25 20:20:53.224 (EMS bus Wi-Fi Gateway) MqttClient::Connect
2020-01-25 20:20:53.224 (EMS bus Wi-Fi Gateway) MQTT CONNECT ID: 'Domoticz_1579980053'
2020-01-25 20:20:53.225 (EMS bus Wi-Fi Gateway) Sending 33 bytes of data
2020-01-25 20:20:53.225 (EMS bus Wi-Fi Gateway) 10 1f 00 04 4d 51 54 54 04 02 00 3c 00 13 44 6f 6d 6f 74 69 ....MQTT...<..Domoti
2020-01-25 20:20:53.225 (EMS bus Wi-Fi Gateway) 63 7a 5f 31 35 37 39 39 38 30 30 35 33 .. .. .. .. .. .. .. cz_1579980053
2020-01-25 20:20:53.226 (EMS bus Wi-Fi Gateway) Queued asynchronous read aborted (mqtt-service:1883), [2] End of file.
2020-01-25 20:20:53.275 (EMS bus Wi-Fi Gateway) Received 4 bytes of data
2020-01-25 20:20:53.275 (EMS bus Wi-Fi Gateway) 20 02 00 05 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ....
2020-01-25 20:20:53.276 (EMS bus Wi-Fi Gateway) Disconnect event received for 'mqtt-service:1883'.
2020-01-25 20:20:53.276 (EMS bus Wi-Fi Gateway) onMQTTConnected
2020-01-25 20:20:53.276 (EMS bus Wi-Fi Gateway) MqttClient::Subscribe
2020-01-25 20:20:53.277 (EMS bus Wi-Fi Gateway) MqttClient::onDisonnect Disconnected from: mqtt-service:1883
2020-01-25 20:20:53.277 (EMS bus Wi-Fi Gateway) MqttClient::Close
2020-01-25 20:20:53.277 (EMS bus Wi-Fi Gateway) onMQTTDisconnected
2020-01-25 20:20:53.277 (EMS bus Wi-Fi Gateway) Deallocating connection object 'mqtt-service' (mqtt-service:1883).
2020-01-25 20:20:53.277 Error: (EMS bus Wi-Fi Gateway) No transport, write directive to 'mqtt-service' ignored.
hlugt commented 4 years ago

I noticed by the way that port stays/shows empty in the overview... Is that harmless?

hlugt commented 4 years ago

Hm, also I use a username password on mqtt. That can not be set in the config. Is that the issue? Is it possible to add secure login?

bbqkees commented 4 years ago

The port stays empty in which overview?

Indeed the plugin does not support setting a username or password yet. I will add it add some point but don't know when.

You can try if it works without a username and password and if so, you have found the problem.

hlugt commented 4 years ago

Yeah you are right. Was busy doing that. Or rather trying to get per_listener_settings working in mqtt, so I could have a cluster listener without password and a public with. Alas, do not get that working yet. But to answer your question: yes without user/pass the plugin works.

So solved, basically :-(