Hassapp: An alternative iOS app to empower your HA

simocyz · February 12, 2019, 5:05pm

Count me in, you got a PM

jkirkcaldy · February 12, 2019, 6:35pm

Looks great. I’d love to help test it.

Flipso · February 12, 2019, 7:11pm

Nice, that looks really awesome!

kikettas · February 12, 2019, 11:48pm

I’ve been trying to reproduce the issue today but wasn’t able to do so. Will release a fix that might fix the issue in the next alpha.
Noted your suggestion

revin · February 12, 2019, 11:49pm

Hi @kikettas

I’d love to test it. I’ll drop a PM

Good Work!

kikettas · February 12, 2019, 11:50pm

I’ve working on adding the reordering for both devices and rooms, and fixing some bugs that people were having.

Regarding the TestFlight invitations, I will send more once I release the new alpha .

bsherman · February 13, 2019, 6:24am

I’m late to the party, but happy to test on testflight, too!

Great looking design!

jensenbln · February 13, 2019, 9:09am

Still no devices showing up in alpha.2

Cheers

kikettas · February 13, 2019, 9:35am

It seems to be an issue when retrieving the devices info, something wrong with the JSON provided by HA. It’s rather difficult to reproduce it from my side since our configs are different, but I will try to find whats going on and see if I can fix it.

danichispa · February 13, 2019, 9:55am

@kikettas there’s a bug in new version, with the reordering of items in a room. If you pull the item under the “Manage devices” label, the app crashes.

kikettas · February 13, 2019, 10:11am

True, true, true. Good catch there, I didn’t try that edge case.

Would you mind to add it to https://bitbucket.org/kikettas/hassapp/issues?

Thank you for helping

cjsimmons · February 13, 2019, 10:21am

Yep. Sadly still no devices with the latest update.

Do you have a URL endpoint that we could look at to get the json file to help see if we can find an issue?

kikettas · February 13, 2019, 10:30am

It might be caused by symbols that cannot be parsed by the Foundation JSONDecoder (escaped symbols, backslashes…).

Sure, the HA endpoint that handles this is: /api/states (more info can be found here)

If anyone with the issue want to try this out quickly, I can add he/she to another testing group and work on the issue faster.

hieudn · February 13, 2019, 11:12am

Great!!! Count me in the beta program

cjsimmons · February 13, 2019, 11:44am

Thanks. Going to server/api/{anything here} results in a 401: Unauthorized.

Using curl and running the following command with a token works and give the API running message, so it is running.

curl -X GET -H "Authorization: Bearer ABCDEFGH" -H "Content-Type: application/json" http://localhost:8123/api/

I’m not sure what’s going on, or how the app is authenticating with HA, but something somewhere isn’t right.

borntofly · February 13, 2019, 11:58am

Count on me for the beta testing

Corey_Maxim · February 13, 2019, 11:59am

Yea, I’m still having the no device issue in the new beta

kikettas · February 13, 2019, 1:24pm

Are you sure you are using the corrent Token for this endpoint?

curl -X GET -H "Authorization: Bearer <Your access token here>" \
   -H "Content-Type: application/json" http://localhost:8123/api/states

Argo · February 13, 2019, 1:36pm

I just can not connect to Home Assistant. Everything works from chrome (and Home Assistant main app of course)

What am I doing wrong? Or should I open an issue?

Upd: Is remote access required?

n1k5y · February 13, 2019, 2:02pm

No, remote access in not required.