Just disable / enable main sensor and it should appear. I know about this issue and it will be fixed on the next version.
Btw, why not use only Mobile_app sensor? Or you are using a sensor which is only mqtt supported?
sorry…neebie dont understand…you mean i disabble/enable each sensors i want, or “Enable MQTT Sensors”?
do y need to install MQTT broker?
I have already duckdns.
Not sure of my question, perhaps really stupid…
I enabled the Mobile APP sensors and Forced Mobile App credentials but the sensors don’t appear in Home Assistant. The only thing that appears is Device tracker
Can you share a screenshot of the enabled sensors?
Yep! same.
we need to enable MQTT in hass…if i have understand…but i have duckdns und i thought mqtt is already enable…
wait for a response of Ionut, i am too newbie
What message is showing Home Assistant in the console when you are trying to enable the mobile app sensors?
i have no message in log
Then please enable debug mode in Ariela, and try to enable some sensors and send me the logs. Thank you.
Refusing to update non-registered sensor: …
This appears because Ariela tries to update a sensor which was not registered. I am more interested in what appears when you enable a sensor and you select the mobile app for that sensor
thanks Ionut, sent the log!
I don’t see service under settings.
This means you do not have latest Ariela version
It looks like the new “sensors” option in settings is only enabled with MQTT enabled.
With the ability to use mobile_app instead of MQTT shouldn’t this be available without MQTT enabled?
Thanks!
DeadEnd
The mobile_app will work without MQTT enabled. I just checked the code and it seems to be some old code checks there. I will fix this in the next app version
Seems like mobile_app updates faster then MQTT for me. This is a great change. Do you think it uses less battery since its not using MQTT anymore? Also, you stated that you would add an option to select how long in between auto reconect in the settings.
I’m using the latest version and its still defaulted for 10 seconds. Was this implemented?
Seems like mobile_app updates faster then MQTT for me. This is a great change. Do you think it uses less battery since its not using MQTT anymore? Also, you stated that you would add an option to select how long in between auto reconect in the settings.
I didn’t do any tests but in theory it should update faster. Regarding battery usage, that will going to see in the future.
I’m using the latest version and its still defaulted for 10 seconds. Was this implemented?
I had a lot of work to do to implement the mobile_app sensors, so this is still in a TODO list.