Hello # (englisch)

    Thank you all for your help.

    ABRP is a nice addition. Even when BLE dongles will be supported we still need to update the battery percentage when we are outside the car.


    As this is a beta. We still ask to discuss the new

    Features and provide feedback. As it is not convenient to speak in 3 different forums I ask users to provide feedback in the forum accepting all the languages (Italian, Spanish too). We are all comfortable with auto translate tools and it’s nicer than repeating everywhere the same things.


    Glad some of your are sharing the news here. Thank you for that.

    Great to see this app now released officially.



    Thinking about a possible Android port: is the part for the backend comms (REST api and token handling) packaged in a library, which could ease a possible porting? In a way, I'm thinking of having a common backend handling while the frontend/UI would need system dependent parts.


    Not having looked at the project (since I don't do iOS development), is this something you considered in the app design?

    Hi Dot,


    There's no library officially provided by Smart. They discuss it, but as any big corporation it might take a while.


    You will find a Python library made by DasBasti: https://github.com/DasBasti/pySmartHashtag he created it mostly for his project for Home Assistant: https://github.com/DasBasti/SmartHashtag .


    Personally, for Hello # we took example on the work from Marco at https://github.com/marco79cgn/ios-scriptable-widgets . I found it easy to experiment with his script in JavaScript directly in Scriptable on iOS and on Postman (also uses JS)


    If what you mean is having a common Backend between android and iOS, I don't think we would be able to create it in Hello # as everything is written directly in Swift and swift UI. While Android requires Library in Java, C++ or Kotlin. A C++ library is too much work for me, sorry and Java and Kotlin don't work on iOS.


    If Hello Smart is so slow, we think it's because they use a tool to make apps that works equally on Android and iOS, and their Adobe SDK. Hence slow on both. We are convinced that only a Native app like Hello # can offer the right responsiveness we all want.


    We would encourage an Android project to start in native, to make the best of it. Java or Kotlin. And focus on making the Android app the best app.

    We can still share good UI ideas, but the core components are too different.


    A lot of our coming efforts will be on Widget, Siri Shortcuts, Live Activity.... all those will take a lot of our free time and are really specific for iPhone.


    If someone starts a projects on Android, I would gladly help with answering any question and providing advice on what we went through. We can share critical parts of the code in Swift for them to rewrite for Android.


    I would suggest to start by showing all the data from the car just to master the access to the API and its signature encryption.


    I can share the Car Images and the model names. I made Proxy servers for caching them, so when a car stops being available from smart, we still have the images and names in our DB.

    thanks, that's useful advice and i agree with it. I get the point on programming language differences making a joint backend handling very difficult.


    I'll look into the possible rewriting of swift code into Java. Indeed, having an initial viewing of data would be a good start.


    I'll drop you a PM to get things started. Thanks

    chriscat

    I can now also help test the Hello # app with ABRP support. :thumbup:


    I have noticed that the charging power displayed in ABRP differs from that in the Hello # app and the Hello Smart app.

    For example, 10.36kW charging power is displayed in the Hello # app (and this is the realistic value), while only 8.6kW charging power is displayed in ABRP.


    Hello #.png Hello Smart.pngABRP.png


    What could be the reason for this? Are the correct values not yet being transmitted to ABRP?

    #1 Pulse 05/24-, 7tkm :thumbdown:

    Corsa-e 11/20-, 19.8kWh/100km, 48tkm

    AMP+-ERA-e 02/18-05/24, 19.2kWh/100km, 197tkm

    Zoe Q210 08/16-02/18, 20.2kWh/100km, 54tkm

    Danke 1

    Thank you. We will double check. It seems that 3-phase charging is sent to ABRP like a 1-phase. The square root of 3 multiplier could be missing.

    I have noticed that there are always SoC deviations between ABRP and the Smart. When I drive a 100km route, the deviation between the app and the car is about 5-7%.


    Hello# is running in the background and the button for automatic updating is activated. However, I don't get the feeling that it's updating in the background.


    Did I overlook something? or is there something else that needs to be activated?

    Zitat von kliffkante

    I have noticed that there are always SoC deviations between ABRP and the Smart. When I drive a 100km route, the deviation between the app and the car is about 5-7%.


    Hello# is running in the background and the button for automatic updating is activated. However, I don't get the feeling that it's updating in the background.


    Did I overlook something? or is there something else that needs to be activated?

    Hello# cannot work in the background. This feature is in work. Stopping apps working in the background is default by the operating system to save battery.

    ========================

    Standort: Baden-Baden

    Smart #1 Launch Edition seit 23.05.2023

    AHK, Smart OS 1.4.1 EU, IOS App 1.4.32

    Danke 2

    But even when Hello# is active and running in the foreground, the display will eventually turn off or go into lock mode. Do I need to disable iPhone automatic lock of the iPhone for it to run flawlessly?