Domoticz

I'll try to get this done over the weekend.

The proxy seems to be down at the moment, but I guess your fix works, as if I pull the network cable, it still does not stop trying. I.e. I get 'Error: PROXY: Error resolving domoproxy.domoticz.com: The requested name is valid, but no data of the requested type was found' multiple times into the log.

Toni wrote:The proxy seems to be down at the moment, but I guess your fix works, as if I pull the network cable, it still does not stop trying. I.e. I get 'Error: PROXY: Error resolving domoproxy.domoticz.com: The requested name is valid, but no data of the requested type was found' multiple times into the log.

Thanks for your feedback. It really helps.
Is there a pause (15 seconds) between trying? Previously, under some circumstances, retrying was done lots of times per second.

Yes, there is a delay between tries.

But speaking of MyDomoticz, I just upgraded to V3.5995, and it connects to the Proxy. But I don't see anything in https://my.domoticz.com/mydomoticz/dashboard, and also the 'Proxy' tab is missing from Domoticz.

Toni wrote:Yes, there is a delay between tries.

But speaking of MyDomoticz, I just upgraded to V3.5995, and it connects to the Proxy. But I don't see anything in https://my.domoticz.com/mydomoticz/dashboard, and also the 'Proxy' tab is missing from Domoticz.

You might want to clear your browser cache if it's been a while. The dashboard has been updated using push-based websocket updating, instead of time-interval http polling.

== Rene

Oh yes, that was it... And I thought a simple reload would be enough.

Toni wrote:Oh yes, that was it... And I thought a simple reload would be enough.

Some browsers are kind of aggressive, concerning cache - not obeying the usual cache parameter rules.
It's a usual web developers problem.

I can't seem to successfully login to the my domoticz web interface. I have registered an account, validated that account via the email link, but my login attempt always comes back with "invalid login". I have reset my password countless times... any ideas?

ryanfx wrote:I can't seem to successfully login to the my domoticz web interface. I have registered an account, validated that account via the email link, but my login attempt always comes back with "invalid login". I have reset my password countless times... any ideas?

I have the same problem!

I can login to https://my.domoticz.com/mydomoticz/dashboard but there's no instance detected.
In the Domoticz error log I see "Error: PROXY: StartThread(): Exception: resolve: Host not found (authoritative)" which I'm assuming is the proxy to MyDomoticz.
I'm not sure which hostname is used for Domoticz to connect to MyDomoticz, but my.domoticz.com resolved successfully from my domoticz machine.
Has anybody else seen this problem and managed to fix it?

EDIT:

Actually, something tells me that domoticz tries to connect to a hostname which doesn't exist "Host not found".


EDIT 2:

I did a tcpdump and figured out myproxy.domoticz.com is trying to get resolved, and that doesn't exist.

EDIT 3:

Looking in the source code it seems domoproxy.domoticz.com is now used.
Maybe I should update Even though I haven't received any notifications about any newer versions, running v3.5877

kastrom wrote:

ryanfx wrote:I can't seem to successfully login to the my domoticz web interface. I have registered an account, validated that account via the email link, but my login attempt always comes back with "invalid login". I have reset my password countless times... any ideas?

I have the same problem!

ryanfx, kastrom: Thanks for reporting this. It was a bug, after having implemented csrf tokens on all mydomoticz pages.
Seems that I had missed something. Please try again to create a password. And apologies for the inconvenience.

Silenus wrote:I can login to https://my.domoticz.com/mydomoticz/dashboard but there's no instance detected.
In the Domoticz error log I see "Error: PROXY: StartThread(): Exception: resolve: Host not found (authoritative)" which I'm assuming is the proxy to MyDomoticz.
I'm not sure which hostname is used for Domoticz to connect to MyDomoticz, but my.domoticz.com resolved successfully from my domoticz machine.

Yeah, we did need to change the hostname. So updating to the newest beta version will resolve your issue.
Not sure when a new stable version is planned.

And sorry for not having posted this here in this forum. It certainly deserved to be mentioned.

== Rene

During the next binary update of MyDomoticz, we are using a challenge response method in order to log in to your dashboard.
You won't notice anything, you can log in just as usual.

The difference is that your password is not sent anymore to the MyDomoticz server. In stead just a hash is sent (a different one each time), so MyDomoticz is unable to know your password anymore, after you've set it up. Even when logging in.

The only reason you will want to know about this is if you are using a script, logging in automatically.
A side note on the same topic: O-AuthV2 is still under construction, due to limited time being able to work on this.

== Rene

After some weeks I logged in to MyDomoticz and don't see anything. What is wrong? I did not change anything in Configuration. Only thing was an Domoticz update.

bullrin wrote:After some weeks I logged in to MyDomoticz and don't see anything. What is wrong? I did not change anything in Configuration. Only thing was an Domoticz update.

Do you have MyDomoticz enabled in your settings?
What are the relevant lines in your logs?
What update channel are you using? Stable or Beta?

chimit wrote:

bullrin wrote:After some weeks I logged in to MyDomoticz and don't see anything. What is wrong? I did not change anything in Configuration. Only thing was an Domoticz update.

Do you have MyDomoticz enabled in your settings?
What are the relevant lines in your logs?
What update channel are you using? Stable or Beta?

Yes it is still enabled, I've nothing changed. I can't see any entries in the log related to MyDomoticz. I'm using the latest code from git (building it on rpi3)

bullrin wrote:

chimit wrote:

bullrin wrote:After some weeks I logged in to MyDomoticz and don't see anything. What is wrong? I did not change anything in Configuration. Only thing was an Domoticz update.

Do you have MyDomoticz enabled in your settings?
What are the relevant lines in your logs?
What update channel are you using? Stable or Beta?

Yes it is still enabled, I've nothing changed. I can't see any entries in the log related to MyDomoticz. I'm using the latest code from git (building it on rpi3)

Ah... I think I know what the problem is. Try to clear your browser cache and reload.
Apologies for the inconvenience.

== Rene

Hi,

Recently I installed Domoticz (D) and also created the MyDomoticz (MD) account. But the dashboard from my D is not showing up in MD. I do have an API key that shows up in my settings. I'm running the beta channel (fully updated) and my log entry just displays: I do have a different error in my log that I think started when I switched from stable to beta, but not sure if thats related: Already tried clearing my cache and refreshing my browser. Do you might have an idea what the issue could be? Thanks.

Rolf

Rolfie wrote:Hi,

Recently I installed Domoticz (D) and also created the MyDomoticz (MD) account. But the dashboard from my D is not showing up in MD. I do have an API key that shows up in my settings. I'm running the beta channel (fully updated) and my log entry just displays:

Code: Select all

PROXY: Authenticate result: success.

I do have a different error in my log that I think started when I switched from stable to beta, but not sure if thats related:

Code: Select all

Error: PluginSystem: Failed load 'libpython3.5.so', Python probably not installed on system.

Already tried clearing my cache and refreshing my browser. Do you might have an idea what the issue could be? Thanks.

Rolf

In case you created more than one account, the api key might be different from the one that you use to log in.

That error has been reported separately by several people.
It's nothing to worry about, apparently.