Posts made by DocHardinger

@Lazar-Demin yes this helps thx. But we're thinking about using the USB2514B-I/M2 from Microchip do you think there will be problems with this chip and the omega?

And yes a new hardware guide would be really helpful.

Can you give more details? How did you connect the MCP23018?

We´re searching for an alternative USB Hub Controller IC with at least 3 ports which is compatible with the Omega2s. In the Omega Hardware Design Guide the GL850G-OHY37 is used, but this one is old and difficult to obtain. Any ideas or reference designs would be nice.

Thx in advance.

@crispyoz we have already 22.03. running since the beginning and also beeing part of the developing process (means we tested a lot of the new stuff and also doing some adjustements on the firmware in our system). By now we have all stuff running on 22.03. But thinking about switching to 23.05 because of beeing up to date seems better ;-)... were using almost any feature the omega has. If youre interested or for better understanding on how we use the omega you can check https://www.e1nfach.com . So the question is if its a good idea to switch to 23.05.....

Hi,

are there any Omega specific changes in 23.05. vs 22.03?
In the documentation i read about better wifi driver for example. But it hink the same driver is already implemented in 22.03, right? And i think Modemmanager is running in a newer version in 23.05 which also has some bugfixes...

Are there any other benefits with 23.05 for the omega?

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!

@crispyoz said in Ask for password when using serial connection?:

uci set system.@system[0].ttylogin='1' && uci commit system

uci set system.@system[0].ttylogin='1' && uci commit system

This did the trick, Thx sir!

@crispyoz Yes and and some other libraries. Problem is that i need internet connection to install this or all the single packages.

Anyway we will use mosquitto 2.0.17, but im not sure how to integrate this when building the firmware. normally we use the profile file for this but then it takes 2.0.18. So how can we achieve to use 2.0.17 when building the firmware?

@crispyoz yeah its strange i tried your ipk but gets an error because of architecture. When im using the ipk from the source of my last post its working fine. Were using an Omega2+ with custom build firmware.

root@E1NS-d7d3:/tmp# opkg remove mosquitto-ssl
Removing package mosquitto-ssl from root...
Command failed: Not found
Not deleting modified conffile /etc/mosquitto/mosquitto.conf.
Not deleting modified conffile /etc/config/mosquitto.
root@E1NS-d7d3:/tmp# opkg install mosquitto-ssl_2.0.18-r3_mipsel_24kc.ipk
Collected errors:
 * pkg_hash_check_unresolved: cannot find dependency libopenssl3 for mosquitto-ssl
 * pkg_hash_fetch_best_installation_candidate: Packages for mosquitto-ssl found, but incompatible with the architectures configured
 * opkg_install_cmd: Cannot install package mosquitto-ssl.
root@E1NS-d7d3:/tmp#

@crispyoz Tried this but no success because of different architecture. But what i now find out is that version 2.0.15-1 and 2.0.17 of mosquitto is working as expected. Downloaded it from original openwrt packages ( https://archive.openwrt.org/releases/packages-22.03/mipsel_24kc/packages/ ). Version 2.0.18 from same source isnt. So there seems to be a bug inside the mosquitto package.

root@E1NS-d7d3:~# mosquitto -c /etc/mosquitto/mosquitto.conf
1718349698: mosquitto version 2.0.15 starting
1718349698: Config loaded from /etc/mosquitto/mosquitto.conf.
1718349698: Opening ipv4 listen socket on port 1883.
1718349698: Opening websockets listen socket on port 9001.
1718349698: mosquitto version 2.0.15 running
1718349699: New connection from 192.168.1.175:53421 on port 1883.
1718349699: New client connected from 192.168.1.175:53421 as mqtt-explorer (p2, c1, k60, u'pc').
1718349713: Saving in-memory database to /etc/data//mosquitto.db.
1718349817: New connection from 192.168.1.1:57055 on port 1883.
1718349817: New connection from 192.168.1.1:34947 on port 1883.
1718349817: New connection from 192.168.1.1:49321 on port 1883.
1718349817: New client connected from 192.168.1.1:34947 as e1ns_bridge2 (p2, c1, k60).
1718349817: New client connected from 192.168.1.1:57055 as e1ns_automation (p2, c1, k60).
1718349817: New client connected from 192.168.1.1:49321 as e1ns_hardware (p2, c1, k60).
1718349817: Saving in-memory database to /etc/data//mosquitto.db.
1718349818: Saving in-memory database to /etc/data//mosquitto.db.
1718349818: Saving in-memory database to /etc/data//mosquitto.db.
1718349818: Saving in-memory database to /etc/data//mosquitto.db.

i did exact the same but not even getting an error. Same configuration as in my previous post and getting:

root@E1NS-d7d3:~# service mosquitto stop
root@E1NS-d7d3:~# service mosquitto disable
root@E1NS-d7d3:~# mosquitto -c /etc/mosquitto/mosquitto.conf

^Croot@E1NS-d7d3:~# mkdir /etc/data
root@E1NS-d7d3:~# chown mosquitto /etc/data
root@E1NS-d7d3:~# mosquitto -c /etc/mosquitto/mosquitto.conf
root@E1NS-d7d3:~# mosquitto -c /etc/mosquitto/mosquitto.conf

root@ABCD-d7d3:~# mosquitto -c /etc/mosquitto/mosquitto.conf
1718314307: mosquitto version 2.0.18 starting
1718314307: Config loaded from /etc/mosquitto/mosquitto.conf.
1718314307: Opening ipv4 listen socket on port 1883.
1718314307: Opening websockets listen socket on port 9001.
1718314307: mosquitto version 2.0.18 running
1718314307: New connection from 192.168.1.175:50934 on port 1883.

NO database created, also tried your folder.
Can you post your config?

@crispyoz i used the openwrt beta 22.03. original from onion and installed mosquitto with opkg (the ssl version) but still the same issue, i also tried without setting the directory for the db file, but no success.

So i tried the following. But i didnt get any response...Or how is it working with SIGUSR2

CONFIG:

# mqtt over websocket configuration
log_type error
log_type warning
persistence true
persistence_location /etc/mosquitto/
persistence_file mos.db
autosave_on_changes false
autosave_interval 5
pid_file /etc/mosquitto/mosquitto.pid
listener 1883 0.0.0.0
protocol mqtt
allow_anonymous true
listener 9001 0.0.0.0
protocol websockets
allow_anonymous true
check_retain_source true
retain_available true

SHELL:

22353 root      1312 S    -ash
22514 mosquitt  4748 S    mosquitto -c /etc/mosquitto/mosquitto.conf
22541 root         0 IW   [kworker/u2:1-ev]
22556 root      1320 R    ps
28557 root      2664 S    {ntpd} /sbin/ujail -t 5 -n ntpd -U ntp -G ntp -C /etc/capabilities/ntpd.json -c -u -r /bin/ub
28583 ntp       1312 S    /usr/sbin/ntpd -n -N -S /usr/sbin/ntpd-hotplug -p 0.openwrt.pool.ntp.org -p 1.openwrt.pool.nt
root@E1NS-d7d3:~# kill -SIGUSR1 22541
root@E1NS-d7d3:~# kill -SIGUSR1 22514
root@E1NS-d7d3:~# kill -SIGUSR2 22514
root@E1NS-d7d3:~#

@crispyoz Yes were using beta build 22.03.05 with custom build. But i already tried it with standard beta build 22.03.05 from onion. Same issues.

i will try now with the new settings in mosquitto.conf.

Thx for your answer i already tried with Sigusr1 but will try again with also sigusr2 maybe this gives more info. Messages are retained, i can check this by reconnect to the broker without stopping the broker,so this has been working.

Where can i switch on check_retain_source and retain_available? In mosquitto.conf?

The strange thing ist that exakt the same config was working in older version of openwrt/mosquitto...

We are using mosquitto-ssl V2.0.18 in OpenWRT 22.03.5. We having issues with persistence. The persistence db file is never been created.
Permissions are set correctly in /etc/mosquitto directory (Owner is mosquitto:mosquitto). We think in Version 2.0.15 this worked fine. But its hard to downgrade to version 2.0.15 in OpenWRT to test it. There are no error messages in log.

Steps to reproduce:

Starting mosquitto service
Connect to Broker with MQTT Explorer and send a retained message
Closing connection
Stopping mosquitto service
Start mosquitto service
Connect again to broker and the retained message is not published
We are using this configuration file:

log_type all
persistence true
autosave_on_changes false
persistence_location /etc/mosquitto/
autosave_interval 5
# mqtt configuration
listener 1883
protocol mqtt
allow_anonymous true

Ive posted it already on Github mosquitto repo, but may be someone here hace the same problems or someone knows how to solve it. Not sure but maybe this only is an issue on omega2 hardware...

Thx for your answer, still didnt find the time to check if that works. Anyway i will give it a try soon.

Thx for your answer.
You´re right i´m using a terminal connection over rs232 with usb.
The root password is set to onioneer as default. Anyway i tried to set it again with passwd and followed your instructions.
But still i can connect without entering a password. I think this has somethin to do with busybox. See this post: https://forum.archive.openwrt.org/viewtopic.php?id=16900 . But im not sure how to do it on the omega. Or is there another way to ask for password when connecting over serial? Thx for your help.

Hi there,

is it possible to activate password request when connecting over serial connection to the Omega?
I´ve read something about busybox but not sure if this is the right way. Any help is appreciated.

@crispyoz hmm ok, but thats no option for us because it will be used by different customers and for this we need pin verification.