Thank for letting me know about the call state sensor issue. I will fix this issue on the next Ariela version
Its not just call state, its also wifi, notification,and NFC as well.
Well the sensor needs a device_class to be registered in mobile app, and iluminance has been choose, since in HA we do not have device class nfc, device class call state etc 
Thanks for all the hard work you do. I am a big advocate for Ariela and sing its praise where ever I can.
Thank you very much, i am really glad you and others appreciate my work 
I found the sensor settings. I did have the latest. Not sure why I didn’t see it earlier. Do you have recommended or examples for setting up the internal mqtt? I’m slowly catching up. Thanks again
Ariela should help you / give some examples of choosing mqtt. I do not have any examples for now since this new change break the old examples.
Also, if you do not want to setup MQTT you can tell Ariela to use the Home Assistant client and not the build in (Ariela → Settings → MQTT)
Very difficult to keep up with the many changes. I’m sure you can’t wait for 1.0 to be released 
. Thanks again for your hard work. Yours is the first app I purchased before I had a need due to your excellent support!
I was able to configure the built in via ssl://IP Address:8883. I tried to use a similar setting for my external, ssl://XXX.duckdns.org:8883 and it fails. Is this what got broken by the update?
Cannot enable sensors on latest version, using mobile_app. It says I need to configure MQTT to use sensors?!
And for the push notifications (mobile_app again) I cannot send a image.
{
"title": "Ringeklokke",
"message": "Det ringer på døren",
"data": {
"tag": "866050",
"image": "https://CENSORED/local/frontdoor.jpg",
"color": "#FFFF00"
}
}MQTT requirement is old code Ionut is aware of, has found, and will be fixed in next release.
1 Like
Indeed there are many things that needs to be added 
And also, thank you very much for the support, it really helps me keeping things further.
Most likely Ariela cannot connect to external because that port is not reachable external? Can you try with other MQTT client and see if you can connect to that external IP?
This will be fixed on next release( tomorrow)
Have you tried to make the notification bigger? Most of the Android notifications do not show at full size. Please tell me if works.
Cannot make it any bigger. Nothing happens when I try to activate the notification on the device.
Not even sure if the JSON is correct, as I haven’t used pictures in notifications until today 
Oh - it seems like it doesn’t like HTTPS for the picture - tried placing it on a non HTTPS site and then it works 
Can you try with this image “https://www.google.com/images/branding/googlelogo/1x/googlelogo_color_272x92dp.png”
The image downloader for Notifications is done by the Android itself and not by Ariela, and i suspect that you have a self signed certificate that Android OS do not know how to handle itself.
Not self signed - fully certified wildcard AlphaSSL certificate.
Hmm - that one actually works. That’s strange.
That one was on me - did a SSL check and found that I had forgotten to include the intermediate certificate from AlphaSSL.
Now it works like supposed.
1 Like
Got Ariela working and after enabling mobile_app in HA (+restart HA) and sensor in Ariela, now I see the notify-service in HA.
But how to send a message? I’m confused. Where to put the text as shown here? Or what to put in as service data in the Services-tab? Ideally I want to use Node-Red by the way to send something via HA.
Well its quite simple.
In Service put:
notify.mobile_app_your_device
In service data:
{
“message”: “This is my first Ariela notification”
“title” : “Ariela Rocks”
}