Domoticz

galadril wrote: Friday 08 May 2020 9:19 But this issue with all the old servers / 1000 emails, most nice emails, but some really rude ... / I received like 60 1-star on rating because of this update..

Alain wrote: Saturday 09 May 2020 11:55 219 version works perfect for me.

Initially I rated the app 4-stars, but as developer commitment and service is also important, I adjusted my rating to 5-stars. Your dedication is second to none @galadril

jvdz wrote: Saturday 09 May 2020 13:33 I've made a recording of what I see on my s10e phone : https://1drv.ms/v/s!ArbrxAynjpqNhPt21Ng ... w?e=bOabAt
In this case the first 3 times you see that the Switch "TVHoek" is not doing anything, then the 4th and 5th time it is switching fine and then the 6th time it is failing again.

galadril wrote: Saturday 09 May 2020 14:50 EDIT: Can you contact me on [email protected] ? quickly discussing this in dutch is maybe a bit easier

dyter wrote: Saturday 09 May 2020 15:41 is it possible to start the domoticz voice app throught the google voice of android device ?

galadril wrote: Saturday 09 May 2020 14:50

jvdz wrote: Saturday 09 May 2020 13:33 I've made a recording of what I see on my s10e phone : https://1drv.ms/v/s!ArbrxAynjpqNhPt21Ng ... w?e=bOabAt
In this case the first 3 times you see that the Switch "TVHoek" is not doing anything, then the 4th and 5th time it is switching fine and then the 6th time it is failing again.

Can you set Dashboard as your startup page? just to see if that all works..
Because im thinking that there may be an issue with the Plan page..?

EDIT: Can you contact me on [email protected] ? quickly discussing this in dutch is maybe a bit easier
Even with testing the Plan page, i can't reproduce it.. i think its a combination of Domoticz version + no auth that I just can't setup here or on your test server... Can i test against your system maybe?

sdmg wrote: Saturday 09 May 2020 20:21 I have the same problem and it only happens to me on the switch page, not on the plans page.
I am using the latest stable version of domoticz 2020.2.11995 and 0.2.219 of the app.

galadril wrote: Saturday 09 May 2020 20:34

sdmg wrote: Saturday 09 May 2020 20:21 I have the same problem and it only happens to me on the switch page, not on the plans page.
I am using the latest stable version of domoticz 2020.2.11995 and 0.2.219 of the app.

I've build a new version and jvdz assisted me with testing, it looks to be fixed.
So within 2hours, there should be a new version in the app store v0.2.220

Let me know!

sdmg wrote: Sunday 10 May 2020 10:51

galadril wrote: Saturday 09 May 2020 20:34

sdmg wrote: Saturday 09 May 2020 20:21 I have the same problem and it only happens to me on the switch page, not on the plans page.
I am using the latest stable version of domoticz 2020.2.11995 and 0.2.219 of the app.

I've build a new version and jvdz assisted me with testing, it looks to be fixed.
So within 2hours, there should be a new version in the app store v0.2.220

Let me know!

This morning I installed the latest version 0.2.220 and at least it still doesn't work. Before if it worked on plans and not on switches, now neither of them.
When I activate the switch in the app it is activated in domoticz but in the app it appears off, only if I slide to refresh the screen it is activated.

I'll keep testing.
A greeting.

Darsh wrote: Thursday 07 May 2020 14:17

jvdz wrote: Thursday 07 May 2020 14:01I simply created a empty file logincheck in directory \home\pi\domoticz\www which fixed that.

Tried that - still doesn't work, but this changes the error message in the app to "Invalid credentials. IMPORTANT: Please check if your Domoticz system uses Login Page as the authentication method. Basic Auth is going to be removed from Domoticz from the next update!"


Darsh

galadril wrote: Saturday 09 May 2020 20:13

dyter wrote: Saturday 09 May 2020 15:41 is it possible to start the domoticz voice app throught the google voice of android device ?

No its not integrated with google assistant, its just some simple speech command that you can record and use (you can config them in the settings)

galadril wrote: Thursday 07 May 2020 0:20

jvdz wrote: Wednesday 06 May 2020 23:56 Is there any documentation on how this "logincheck api method" works and what the app expect as conversation, without trying to distil it for the current GitHub source?

We call the /logincheck endpoint with md5 hashed password, and base64 hashed username as form-data in the POST call.
It returnes some json with info about the logged in user (rights, etc).
And it returns an authentication cookie.. and that cookie is then used for other connections instead of the username/password.
Until the cookie expires.. then we login again for a new cookie

dyter wrote: Tuesday 12 May 2020 17:26 it's really a shame and useless because the app can't wake the device and notifications don't work in real time

jvdz wrote: Tuesday 12 May 2020 17:39

galadril wrote: Thursday 07 May 2020 0:20

jvdz wrote: Wednesday 06 May 2020 23:56 Is there any documentation on how this "logincheck api method" works and what the app expect as conversation, without trying to distil it for the current GitHub source?

We call the /logincheck endpoint with md5 hashed password, and base64 hashed username as form-data in the POST call.
It returnes some json with info about the logged in user (rights, etc).
And it returns an authentication cookie.. and that cookie is then used for other connections instead of the username/password.
Until the cookie expires.. then we login again for a new cookie

I have been looking at this a little closer but the thing I do not understand is how this /logincheck is made safe to use over an SSL connection?
The Userid and Password are part of the URL so are part of the cleartext part of the SSL connection and can be captured. I do understand that the password isn't reversible, but what is stopping anybody from using the hashes of Userid and Password to start their own connection with the server to get the cookie?
With Basic authentication (https: // userid:password @ ip/) the userid and password are part of the header which does get encrypted by the SSL connection.
I am sure I am missing something here but could somebody enlighten me how it really works?

Jos

galadril wrote: Wednesday 13 May 2020 8:42 Thats probably why the latest logincheck url has all the data in the POST body instead of query parameters....