4481hoods Posted June 8 Share Posted June 8 (edited) Ratgdo had been working fine. Did a reinstall and now I get this message: " A Discover or device command was attempted with no MQTT connection established. Wait for the plugin to establish a connection to the MQTT broker before attempting Discover or device commands." Edited June 8 by 4481hoods Quote Link to comment
Goose66 Posted June 8 Share Posted June 8 When do you get the message and do you get it over and over or just the one time? Quote Link to comment
4481hoods Posted June 8 Author Share Posted June 8 When I try to discover it pops up. It will not load the nodes in IOX. MQTT loads just fine and responds and reports the door status Quote Link to comment
Goose66 Posted June 8 Share Posted June 8 Well that is supposed to only happen when you click Discover before giving the plugin time to connect to the MQTT broker after plugin start. If it’s not connecting, then there should be some type of error in the log. Send your log file. But I did something that in hindsight was probably not smart: I coded a new version of the ratgdo plugin that is built on the ESPhome firmware on top of the old MQTT version. I need to finish testing the ESPHome version, roll it out as a separate plugin, and then I will have to revert to old MQTT version before I can fix any errors in that version. Quote Link to comment
4481hoods Posted June 9 Author Share Posted June 9 Here is the log! ratgdo_6-9-2024_73351_AM.zip Quote Link to comment
RMichael Posted June 11 Share Posted June 11 Same Error. What is your timing for the MQTT stand alone version. Quote Link to comment
Goose66 Posted June 11 Share Posted June 11 This turns out to be an issue with the recent IoX firmware upgrade. There was evidently an upgrade from Python 3.9 to 3.11, and with it, and upgrade of the Paho MQTT client library to v 2.0. The Paho MQTT client library upgrade included breaking changes. Why in 2024 would someone roll out breaking changes to a widely used Python library? Who knows, and we're probably lucky if this is the only breaking change. So I need to complete testing of the ESPHome firmware version of ratgdo (probably rolling that out as a separate plugin or different edition) and then I can look into reverting the code back to MQTT version and make changes in the Paho MQTT client library calls. Honestly, though, there may not be any point in it if everybody is ok with upgrading to the ESPHome firmware. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.