Topics tagged with mqtt

Persistence DB file not created with mosquitto mqqt broker

DocHardinger — Thu, 27 Jun 2024 07:54:38 GMT

I now just integrated the the mosquitto 2.0.17 package inside the firmware and removed the Mosquitto 2.0.18 package from the profile file. The i install the package after booting with the new firmware. So i just hope mosquitto will be fixed in the feature and i just can use the standard package again. If they didnt fix it i will go your way. Thx for your help, its a nice experience to get answers really soon in the onion community!

Help for project

jossvall — Wed, 07 Jul 2021 16:17:43 GMT

@Franmcm said in Help for project: omega 2+ Hi Franmcm, the omega2 + is an excellent choice for your hardware and software requirements. If you have used raspberry you will not have problems with omega2 +.

MQTT Broker ssl

Lnx Prof — Sat, 23 May 2020 23:27:00 GMT

I'm using golang, for MQTT over ssl. The solution in our code was to use tcps for the connector and port 8333. Granted, we're using certificates already in the ca-bundle (Amazon) for the upstream message broker, so we don't need to finagle self-signed certs. What language are you using?

How to Install Mosquitto MQTT Broker on Omega2+?

György Farkas — Sun, 08 Dec 2019 11:45:04 GMT

@Alexandr-Didenko "Naturally" you didn't say anything about your Omega2+'s firmware (as usual;) Omega Firmware Changelog So - for example on a vanilla v0.2.0-b197 ... v0.3.2 b232 firmware - mosquitto has already installed. Run a top command even on your freshly installed Omega2+ please. # Omega2+ with v0.3.2 b232 firmware root@Omega-5BE1:/# opkg list-installed | grep -i mosquitto libmosquitto-ssl - 1.5.8-2 mosquitto-client-ssl - 1.5.8-2 mosquitto-ssl - 1.5.8-2 root@Omega-5BE1:/# opkg info mosquitto-ssl Package: mosquitto-ssl Version: 1.5.9-2 Depends: libc, librt, libuuid, libopenssl, libwebsockets-openssl Provides: mosquitto Status: unknown ok not-installed Section: net Architecture: mipsel_24kc Size: 76962 Filename: mosquitto-ssl_1.5.9-2_mipsel_24kc.ipk Description: Mosquitto is an open source (BSD licensed) message broker that implements the MQTT protocol version 3.1 and 3.1.1. MQTT provides a lightweight method of carrying out messaging using a publish/subscribe model. This package also includes some basic support for configuring via UCI This package is built with SSL support. TLS-PSK will be included (in both the client and broker) if OpenSSL is built with TLS-PSK support. Package: mosquitto-ssl Version: 1.5.8-2 Depends: libc, librt, libuuid, libopenssl, libwebsockets-openssl Provides: mosquitto Status: install user installed Architecture: mipsel_24kc Conffiles: /etc/mosquitto/mosquitto.conf cad5c6ae4ecf25e2709e88f2b92d75905ac4aedc622df6e9a536238c0b047856 /etc/config/mosquitto eaa6b71fbd8e5f7142d949432374017e4cb5d01cf5039b9cd4a65f8953126521 Installed-Time: 1566829837 root@Omega-5BE1:/# mosquitto -h mosquitto version 1.5.8 mosquitto is an MQTT v3.1.1 broker. Usage: mosquitto [-c config_file] [-d] [-h] [-p port] -c : specify the broker config file. -d : put the broker into the background after starting. -h : display this help. -p : start the broker listening on the specified port. Not recommended in conjunction with the -c option. -v : verbose mode - enable all logging types. This overrides any logging options given in the config file. See http://mosquitto.org/ for more information.

How to monitor network connectivity?

Daniel OBrien — Wed, 13 Feb 2019 18:25:28 GMT

I'm playing with the new Omgea2S+ (Pro) board and I have it tethered to my cell phone for network connectivity. I'm not using the web interface at this moment, but doing everything over the USB serial connection on my computer through Teraterm. (it's like putty)

I've noticed that when I walk away from my desk with my phone, the board loses network and the blue light goes out. When I come back with my phone, the blue light comes back on and a message gets written to the terminal: [17932.593554] Interface apcli0 link up! (WPA2PSK AES)

I said to myself, that's neat! And tried to do it while sitting at my desk by turning off my wifi hotspot. When I turn off my hotspot, the blue light goes out like normal, when I turn on my hotspot, I still get the "link up!" message, but the blue light doesn't come back on. Only when I walk far enough away to the point where it loses signal and then coming back in range does the blue light come back on. What process is controlling the blue LED?

I checked the logs: readlog -e link
and I see
Tue Feb 12 15:54:57 2019 daemon.notice netifd: Network device 'apcli0' link is down
Tue Feb 12 15:54:57 2019 daemon.notice netifd: Interface 'wwan' has link connectivity loss
Tue Feb 12 15:54:58 2019 daemon.notice netifd: Network device 'apcli0' link is up
Tue Feb 12 15:54:58 2019 daemon.notice netifd: Interface 'wwan' has link connectivity

so it must be netifd doing the detection? but something else is controlling the notification led, maybe?

And seeing all of this made me want to create a script that monitors the network or a script that ties into the already running process that monitors the network, to keep track of when it's up and when it's down. When it's up, it could send a payload over MQTT with the times of "up" and "down" events, it could also send other cached data, (temp, location, photos) once there is a network connection again.

I could use this in my car, geo-tagging photos taken while driving, caching everything locally, then when I pull into the garage, it offloads everything once the network connection is reestablished.

DHCP Options fields

Peter Buelow — Thu, 17 Jan 2019 13:29:46 GMT

Is there a way to get at DHCP option content once booted? I'm looking around etc and whatnot, but am not able to find anything specific? I'm trying to pass an MQTT server address via DHCP so I can "discover" it.

Or, another possibility, how do I get the Onion to resolve .local addresses? If this is a problem local to me, so be it, but I can resolve mosquitto.local on my other linux and Mac boxes, but not my Onions. That would also allow me to solve the problem quickly.

How to create myomega.local and bind to DHCP IP ?

Peter Buelow — Thu, 17 Jan 2019 16:18:43 GMT

Did you ever figure this out? I think if you just want a server running, install the latest firmware, and you have one running. Connect your omega to a local wifi network, and you have a .local available address on your subnet. I do this as I use an Omega2 as my MQTT server for my local network. I changed my hostname to mosquitto and now through my network via the web console app and I can connect to this server using mosquitto.local from other hosts. It doesn't take a lot of setup. Or, was your question related to something else?

Omega Onion connecting to Cloud Cloud IoT

Daz Wilkin — Wed, 30 May 2018 03:09:31 GMT

@Lazar-Demin -- Thanks for the shout-out! I didn't receive an email when you posted to this topic Yes, I'll revise the post to move the working content to the top. So, may we have Google Cloud Platform added to your Connecting to Cloud Platforms? Onioneer, yes!

Losant + Onion Omega2 Single command not connecting....

k t — Tue, 21 Nov 2017 14:54:36 GMT

Hi.

I have succesfully entered the device id, access id & access key.

However when I run the subscribe command. The losant is not changing its status.

"Awaiting first connection to Losant .."

@Lazar-Demin I dont think it is connecting to the mqtt ...

paho-mqtt python

Lazar Demin — Wed, 23 Aug 2017 21:48:29 GMT

@k-t The fix for this is in our Docs! See https://docs.onion.io/omega2-docs/installing-and-using-python.html#using-pip-to-install-python-modules Specifically look at the section entitled: Fixing the Setup Tools Issue

MQTT stupid beginner question (react on subscription)

Joe Strout — Mon, 30 Oct 2017 15:17:51 GMT

I've just gotten my Omega 2 board today, and I'm thinking along very similar lines — I want my Onion boards to either send MQTT messages when something happens to their connected hardware, or do something with that hardware according to MQTT messages received. Like you (Sebastian), I see no point in running an MQTT broker on the device — the broker will be elsewhere; these are edge devices that should merely be MQTT clients. I see you solved it by using some clever files and shell scripting. But did you consider using Python? From other threads, it looks like paho-mqtt can be installed for python, which should make it pretty easy (and possibly more efficient) to subscribe to topics and do stuff in response (or conversely, to publish MQTT messages in reaction to anything you can sense in Python). Just wondering if I am somehow barking up the wrong tree, or whether this is a sensible way to do it.

Error 12 out of memory pip install paho_mqtt

Jarek Zgoda — Tue, 16 May 2017 09:26:39 GMT

Many others fail the same way, it's just not enough juice. If the package does not have C code to compile you may try to just use it "as is" from directory in PYTHONPATH.

MQTT relay [MQTT] "Omega2"

Lazar Demin — Tue, 15 Aug 2017 16:18:13 GMT

@Mar-Adrian-Belen Our Omega2 Kits are a good place to start learning electronics: https://onion.io/kits/ Note that this is an Advanced Project and can be dangerous if not handled and wired properly. Proceed at your own risk. However, if the instructions are followed precisely and carefully, it is definitely doable.

Omega2 overclocking MT7688, heatsink

Athar Mian — Thu, 26 Jan 2017 14:44:39 GMT

Can the MT7688 be overclocked and by how much?
Would a cheap self adhesive Ali Express heatsink prevent overheating?

Would overclocking need any special drivers, and what are benefits, e.g., better processing speeds?

MQTT

Claus Kühnel — Wed, 01 Feb 2017 17:19:35 GMT

@luz Thanks for correction.

Control of mosquitto/MQTT

Kit Bishop — Tue, 15 Mar 2016 09:29:05 GMT

@mark-doutre Thanks - found that. Though I think it would still be good if there was a more direct method of stopping it. Regarding the running of the broker on the Omega, I agree with your comment. So far I have just been playing with MQTT and having a local broker under one's own control is a valuable part of getting to understand it all. In the real world, using a separate broker somewhere else is probably the way to go. Any way, thanks for your interest and comments

For those interested. Working MQTT/Rest broker in Node 0.10.5

Boken Lin — Sun, 06 Dec 2015 20:44:17 GMT

@Bart-Peperkamp Nice! Thanks for sharing!