Yes that is correct. Can you share your mqtt config from configuration.yaml ?
As per instructions for the latest mosquitto broker theres none, ive used this before to no avail though:
mqtt:
broker: 192.168.178.79
port: 1883
discovery: true
discovery_prefix: ha
client_id: homeassistant
username: MQTT
password: mypw
Thank you. Change “discovery_prefix” to “homeassistant” or in Ariela change discovery topic to “ha” and should work just fine
Did that already a million times - no change
I really tried everything i could possibly think of.
Could something entirely different hinder discovery ? Like my router or something ? Im feeling like i have exhausted every single option i could possibly find via google
Please try this.
- change the discovery_prefix like i told before
- restart Home Assistant
- restart Ariela
- re-register the mqtt sensors
- check in developer tools from HA if new entity appear
Also, you may wanna check the HA logs, the discovered items should appear there too.
I did as instructed and unfortunately nothing changed -
As soon as im trying to add
mqtt
to the config errors start to appear in the logs:
2019-07-30 08:00:40 ERROR (MainThread) [hbmqtt.broker] Broker startup failed: [Errno 98] error while attempting to bind on address (‘0.0.0.0’, 1883): address in use
2019-07-30 08:00:40 ERROR (MainThread) [homeassistant.components.mqtt.server] Error initializing MQTT server
Traceback (most recent call last):
File “uvloop/loop.pyx”, line 1112, in uvloop.loop.Loop._create_server
File “uvloop/handles/streamserver.pyx”, line 58, in uvloop.loop.UVStreamServer.listen
File “uvloop/handles/streamserver.pyx”, line 95, in uvloop.loop.UVStreamServer._fatal_error
OSError: [Errno 98] Address in use
I dont think one is supposed to add mqtt to the cfgyaml anymore with the latest hassio / mosquitto plugin.
I know this is well out of your scope, so many thanks for helping me anyway ! Your app is awesome !
( I got some small error with the cover entity where i couldnt press all buttons at all times but i switched over to the “web” view which fixed it )
Seems that another mqtt broker instance is running on your system. Could you try a system restart?
I rebooted it just now, again with no change -
Interesting bit is this warning:
Log Details (WARNING)
Tue Jul 30 2019 08:57:48 GMT+0200 (Mitteleuropäische Sommerzeit)
Data in your config entry is going to override your configuration.yaml: {‘broker’: ‘core-mosquitto’, ‘discovery’: True, ‘password’: ‘xxx’, ‘port’: 1883, ‘protocol’: ‘3.1.1’, ‘username’: ‘homeassistant’}
So the latest mosquitto plugin writes its own config which superceeds the cfg.yaml entries i suppose.
With the plugin discovery is enabled with a checkbox when i add it to integrations. It still doesnt work unfortunately.
With this i cannot help since i do not have enough knowledge about it. Still you can add the mqtt sensors manually in the configuration.yaml
Ill investigate further, it might just be a problem with the latest mosquitto plugin, thanks !
Ok, please write here the solution if you find one, since it can help other users too. Thank you.
Excellent work!
It works great
due to the new update the app is very slow
What do you mean by very slow?
Can a boolean_input be add to be used as a widget? I have several boolean_inputs that I use as indicators and would like to be able to put them as widgets on my wifes phone.
Thanks
It can be added but clicking it will have no effect. I will add this to my todo list
I sent you an email
Hello,
Version 1.3.5.6 is out.
What’s new:
Version 1.3.5.6
Release date: 2 August 2019
- NEW: added proximity sensor
- NEW: added accelerometer sensor (state of the sensor will be device orientation)
- NEW: added distance setting between GPS locations
- Fixed camera streaming issue
- Fixed crash app when sending toggle requests
- Updated google libraries
Please test it and let me know how it goes. Thank you.
On my girlfriend’s Moto G5S sometimes the app gets stuck at the loading screen (after the Ariela logo slides out of view).
I suspect it due to wifi disconnect and reconnect though I am not 100% sure, I already enabled auto reconnection but it doesn’t help.
The only way to get rid of it is force close the app and start it again. Problem is, it’s hard to reproduce, so giving debug logs is difficult at the moment… Any ideas?
Please try to send the logs, maybe it catches something useful. Thank you.