MQQT 4 and samba share 8 upgrade help

I have recently upgraded MQTT and have seemed to lost all my switches.

Here are my settings:
{
“logins”: [],
“anonymous”: true,
“customize”: {
“active”: false,
“folder”: “mosquitto”
},
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”
}

and here is the error:
[INFO] Setup mosquitto configuration
[WARN] SSL not enabled - No valid certs found!
[INFO] No local user available
[INFO] Initialize Hass.io Add-on services
[INFO] Initialize Home Assistant discovery
[INFO] Start Mosquitto daemon
1541868933: mosquitto version 1.4.15 (build date 2018-03-04 15:35:59+0000) starting
1541868933: Config loaded from /etc/mosquitto.conf.
1541868933: *** auth-plug: startup
1541868933: ** Configured order: http
1541868933: Opening ipv4 listen socket on port 1883.
1541868933: Opening ipv6 listen socket on port 1883.
1541868933: Opening websockets listen socket on port 1884.
1541868933: Warning: Mosquitto should not be run as root/administrator.
1541868933: New connection from 192.168.0.105 on port 1883.
[ERROR] Auth error with agengr16
1541868934: Socket error on client <unknown>, disconnecting.
1541868934: New connection from 192.168.0.101 on port 1883.
[ERROR] Auth error with agengr16
1541868935: Socket error on client <unknown>, disconnecting.
1541868935: New connection from 192.168.0.122 on port 1883.
[ERROR] Auth error with agengr16
1541868937: Socket error on client <unknown>, disconnecting.
1541868939: New connection from 192.168.0.105 on port 1883.
[ERROR] Auth error with agengr16
1541868940: Socket error on client <unknown>, disconnecting.
1541868940: New connection from 192.168.0.102 on port 1883.
1541868940: New connection from 192.168.0.101 on port 1883.
[ERROR] Auth error with agengr16
1541868942: Socket error on client <unknown>, disconnecting.
[ERROR] Auth error with agengr16
1541868943: Socket error on client <unknown>, disconnecting.
1541868943: New connection from 192.168.0.122 on port 1883.
[ERROR] Auth error with agengr16
1541868944: Socket error on client <unknown>, disconnecting.
1541868945: New connection from 192.168.0.105 on port 1883.
[ERROR] Auth error with agengr16
1541868947: Socket error on client <unknown>, disconnecting.
1541868948: New connection from 192.168.0.101 on port 1883.
[ERROR] Auth error with agengr16
1541868949: Socket error on client <unknown>, disconnecting.
1541868949: New connection from 192.168.0.122 on port 1883.
[ERROR] Auth error with agengr16
1541868950: Socket error on client <unknown>, disconnecting.

Also upgraded Samba Share and it is no longer available on windows 10:
Here is my settings:
{
“workgroup”: “WORKGROUP”,
“username”: “”,
“password”: “”,
“interface”: “eth0”,
“allow_hosts”: [
“10.0.0.0/8”,
“172.16.0.0/12”,
“192.168.0.0/16”
]
}

Log:
[ERROR] No valid login data inside options!

Any help would be appreciated. This is frustrating…

On samba, guest access is no longer supported so you need to put a username and password in your samba configuration. You will need to use that login password on your windows 10 client and tell windows to always use that login. (yes, I know) :slight_smile:
On mqtt my suspicion is the same, I think you need to put a username and password in even though you stated anonymous true. I did that and mqtt started behaving again. (but I had to change some client mqtt’s login to match (like phones using owntracks).

Thanks for the information. I did the same for both, but my switches are not showing up on MQTT. On SambaShare, windows 10 is still not seeing hassio anywhere on it.

Here is the log on samba share:
[INFO] Read hostname: hassio
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
No builtin backend found, trying to load plugin
tdbsam_open: Converting version 0.0 database to version 4.0.
tdbsam_convert_backup: updated /var/lib/samba/private/passdb.tdb file.
tdb(/var/lib/samba/winbindd_idmap.tdb): tdb_open_ex: could not open file /var/lib/samba/winbindd_idmap.tdb: No such file or directory
tdb(/var/lib/samba/account_policy.tdb): tdb_open_ex: could not open file /var/lib/samba/account_policy.tdb: No such file or directory
account_policy_get: tdb_fetch_uint32_t failed for type 1 (min password length), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 2 (password history), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 3 (user must logon to change password), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 4 (maximum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 5 (minimum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 6 (lockout duration), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 7 (reset count minutes), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 8 (bad lockout attempt), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 9 (disconnect time), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 10 (refuse machine password change), returning 0
Added user agengr16.
nmbd version 4.8.4 started.
Copyright Andrew Tridgell and the Samba Team 1992-2018
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
added interface eth0 ip=192.168.0.100 bcast=192.168.0.255 netmask=255.255.255.0
making subnet name:192.168.0.100 Broadcast address:192.168.0.255 Subnet mask:255.255.255.0
making subnet name:UNICAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0
making subnet name:REMOTE_BROADCAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0
load_lmhosts_file: Can’t open lmhosts file /etc/samba/lmhosts. Error was No such file or directory
daemon_ready: STATUS=daemon ‘nmbd’ finished starting up and ready to serve connections
smbd version 4.8.4 started.
Copyright Andrew Tridgell and the Samba Team 1992-2018
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Processing section “[config]”
Processing section “[addons]”
Processing section “[ssl]”
Processing section “[share]”
Processing section “[backup]”
added interface eth0 ip=192.168.0.100 bcast=192.168.0.255 netmask=255.255.255.0
INFO: Profiling support unavailable in this build.
No builtin backend found, trying to load plugin
tdb(/var/lib/samba/registry.tdb): tdb_open_ex: could not open file /var/lib/samba/registry.tdb: No such file or directory
daemon_ready: STATUS=daemon ‘smbd’ finished starting up and ready to serve connections
waiting for connections

Hi, can you explain the changes you made for the phones with owntracks

First I set up an HA user account that matched what I put into my mqtt configuration file:

{
  "logins": [
    {
      "username": "mqtt",
      "password": "**********"
    }
  ],
  "anonymous": true,
  "customize": {
    "active": false,
    "folder": "mosquitto"
  },
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem"
}

Then I went to each phone, fired up owntrack app, went to hamburger / preferences / connection / identification and set user name to mqtt with password, put in my name (richard), tracker id of rc and…
soon saw a known-devices.yaml containing a device named mqtt_richard. With after modifying that entry to contain my phone’s mac address… became the entity that tracked me.

Thank you, I was using bridge between cloudmqtt and mosquitto, but with the update I’m very confused how to make it work again

Ok, I got samba share to work it was a setting in windows 10 program features that wasn’t set correctly…
SMB1.0 not set up right in windows.