Closed hugofant closed 5 years ago
Looks like you just secured your MQTT connection, as of now McLighting cannot connect to SSL/TLS secured MQTT. Next update will have ability to connect to secured servers.
hmm, why do you think so - isn't port 1883 the unsecure one, and mosquitto log also says:
[INFO] Setup mosquitto configuration
[WARN] SSL not enabled - No valid certs found!
[INFO] No local user available
[INFO] Initialize system configuration.
[INFO] Initialize Hass.io Add-on services
[INFO] Initialize Home Assistant discovery
[INFO] Start Mosquitto daemon
1542721341: mosquitto version 1.4.15 (build date 2018-03-04 15:35:59+0000) starting
My assumption was that you have set hassio correctly with SSL certificates (because you had fullchain.pem and privkey.pem in your settings). Yes 1883 is insecure port for unencrypted communication. If SSL is used, one would need to connect to port 8883.
I have always had issues with hassio, maybe try a minimal PubSubClient example and see if it works?
I re-read your first comment and see that you are able to use other devices with MQTT. Could you try commenting out this line in McLighting.ino
//if (mqtt_user != "" or mqtt_pass != "") amqttClient.setCredentials(mqtt_user, mqtt_pass);
great! works well with this modification....but a short explanation would be nice - as i haven't set the user/password.....why is/was it !="" ? thanks a lot for your help
I'm guessing some value was either put in definitions.h for mqtt_user and/or mqtt_pass or during initial WiFiManager setup. Once that happens, the value is stored in json format on your SPIFFs. Upon reboot McLighting reads from SPIFFs and uses the stored value. In your case, the stored value might be incorrect.
Hi, i'm acutally using the sketch version 2.1.5 and homeassistant 0.82.1 (Hass.io on raspberry) with Mosquitto broker addon 1.4.15. My problem: since the last upgrade of the MosqittoAddon, McLighting is no longer able to connect anonymously - Other ESP8266s (sensors created with esphomeyaml) and also MQTT.fx are working well and are connecting anonymously without any problem....so it seems not to be a problem of the broker. Serial Console says:
and the broker:
definitions.h:
MQTT broker config:
would be thankfull for some hints/ideas