-
Notifications
You must be signed in to change notification settings - Fork 30
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
MQTT standalone #69
Comments
Yeah. I don't want to rely on a "client" to bring its own mqtt-server. |
Same here, I have a mosquitto server running. I wish this module could be a client instead of a server. |
The same here |
I´d also like to use my independent mosquitto server. |
I can support this feature request too! I have to use a dedicated broker because sensor data has to go directly over the broker to an influx db too. |
That is a great feature, how can we support that we have implementation. |
there would be fine when only one server will be need for both cases |
I did look into this topic a little bit just now, and it does not seem to be too easy to completely switch to an existing MQTT broker. There is one big issue, which means that it is not enough to just change the MQTT broker:
From what I know right now, there would be a manual change on ALL tasmota devices, to include the client inside the mqtt topic. I will not look into this further, because I don't think that this is a very good way to go, right now. |
ok thats also fine, when you have the option to do a bridgeing to a other server In my infastructure, at the moment, i have to double the mqtt server, that i have one ony for the sonoff/tasmota and other for the rest |
In all my setups I use a unique module host name in the MQTT topic on all tasmota devices. So there is the ‚client information‘ in the topic. It‘s also necessairy for my sensor database in influxdb. |
could someone help solving this with bridging on the central mosquitto MQTT broker? So the mosquitto could bridge to the sonoff adapter on iobroker? Any help would be appreciated |
I would also very much appreciate adding support for an external mqtt server into this module. I spent hours trying to solve the problem having a mosquitto server bridging to sonoff module. As the module relies on the name of the client connected to create the instances, it pastes everything under the client id of the mosquitto bridge instead the appropriate tasmota devices... |
I'll pile on. External MQTT server as an option would be appreciated. |
I like this to. |
I like this too. To be honest. I think it is not the idea of the MQTT protocol to have many servers for different "vendors"/"types" of IoT devices. I have one server running and this one should handle all my use cases. |
Ok, but its then the "mqtt" or "mqtt-client" adapter not suitable for you? The thing here is that ease of use for unexperienced users ... Also if it would connect to a different mqtt server we would need some kind of "what states to subscrube that are the sonoffs to handle by this adapter" because there will be much more data in it not handleable by this adapter. So: How it could work from your idea? Can someone write such an idea down to discuss? |
Hi Apollon, I am not sure if we are on the same page or if I understand the architecture of the adapter (I kind of new to iobroker). As the Adapter is not a "real" MQTT-Broker it is not possible to listen or subscribe to it with tools like mqtt.fx (at least it does not work for me in my configuration) or other clients from different servers. In that case I can use my tasmota devices only with the iobroker adapter and with nothing else (like nodeRed on a different server). I am not sure how the mqtt or mqtt-client adapters might help at this point. The Tasmota devices will still work only with the sonoff adapter. Or is your recommendation to use mqtt-Client instead of sonoff client? The setup I prefere is to have a sonoff adapter with all the sonoff specific setup (topic etc.) is acting as a client and can subscribe to any mqtt Broker in the network. When i got your issue correct the problem is that you need to know if the messages are sent by a tasmota or sonoff device to know that the messages are relevant. If you use the command "Status 2" you will be able to see that a device is a tasmota device. |
One more vote for using an existing mqtt server. Especially because I do not understand the difference whether this sonoff adapter get the tasmota data by acting as a broker or by acting as a client. The data is the same. Would be great if mobilutz could add some more information what he ment with "mqtt messages from sonoff/tasmota do not include any client information", because all data comes from the /STATE channel? |
+1 for an option to connect to an external broker (instead of hosting an additional one with this adapter). |
I second that, +1 for the option to use an external server like mosquitto. |
No one is stopping you to implement it. |
I would if I could. 😄 I currently lack the time and knowledge. |
great discussion! Also a +1 from my side. From the comments I guess what would be needed to be implemented:
The first three points should not be a big deal, but I am not sure about the critical last one (application logic). Regarding the message handling (MQTT topics) I guess there would not be a big change, as the device name of each tasmota would be different. |
There was also an other discussion with the idea to better start a new "tasmota" adapter which works as generic as mqtt but is able to "handle JSONs ina generic way" ... In fact this would mean that roles and datatypes and such will not be that perfectly set , but the maintenance effort to update all these json structures (that are not standardized at all ) would be gone |
If I got your comment right, the issue is, that tasmota messages e.g. tele/deviceName/STATE contain a json structure. |
In fact I (personally) understood that adapter to try to transform the "a bit standardized messages from sonoff devices" into clean ioBroker structures ... but over time anything became Tasmota and got very divers ... so question is if it makes sens to continue here or to continue clean as new adapter with a more generic purpose ... with the downside that "roles" and such details gets lost ... |
Issues ioBroker#69 and ioBroker#10 show, that there is not enough documentation for the different MQTT speaking Adapters. Here I propose a comparison table that would save some people time and effort looking for the right Adapter. Table can be expanded to hold more info. If there are mistakes I do apologize!
Will it be possible to reuse an existing MQTT broker, rather then be depend on the internal MQTT service inside the adpater? It would be helpful to just specifiy the MQTT IP and port of the existing infrastructure....
The text was updated successfully, but these errors were encountered: