Domoticz

chimit wrote:

Madgeni wrote:

IFTT support will probably be added during/after app support (with OAUTH).
Currently there's no target date known of when that will be finished.

+1 for oauth2 support! Any idea on timescales?

The short answer: No. It depends on whenever I have enough free time available for implementation and testing.

Totally understand - appreciate all your hard work

Still just get this in my log:

Error: PROXY: Connect failed, reconnecting: Network is unreachable

Any ideas?

Same here...
From the log:
Error: PROXY: Connect failed, reconnecting: Network is unreachable

The problem with the dashboard.

If I choose a floor plan as the dashboard mode (normal, compact, mobile and floorplan options) in the Domoticz settings, in the upper menu the button "Floorplan" (between Dashboard and Switches) disappears and the link http://192.168.1.5:8080/#/Dashboard doesn't exist. When I click on "Dashboard", the address is "http://192.168.1.5:8080/#/Floorplans" not "http://192.168.1.5:8080/#/Dashboard". I prefer this, because floorplan is my favourite.

In this case, trying to connect from my.domoticz.com to local domoticz server by pressing the green man icon is impossible. This is because mydomoticz tries to connect with "https://my.domoticz.com/mydomoticz/dashboard#Floorplans".
In case, when the dashboard in domoticz is different than floorplan, when I click green man icon in mydomoticz, it connects with address "https://my.domoticz.com/my/3...4/#/Dashboard" and all works fine.

Please fix it, thanks.

I register on Domiticz.com, filled all field in my Domitcz but my boad stay clear and I have this message in the Log:
PROXY: Connect failed, reconnecting: Connection timed out

And MyDomoticz Instance ID: (none)

Any Idea to help me

I have registered and set up but I only see this in de logs:

Error: PROXY: Connect failed, reconnecting: Network is unreachable

Online I see this only
My dashboard are some switches and a group.

Hello,

i have installed domoticz on my raspberry pi. Works all good. After that, i followed the steps from http://domoticz.com/wiki/MyDomoticz and that also worked.

Unfortunately, i removed the instance from my dashboard, but probably when Domoticz was connected. Now, i can log in but i see only a empty dashboard. I cant find out how to repair / reset this to get mydomoticz get worked again. Can someone tell me how to fix this or where i can find the information to do this?

Many thx, Marcel

hello.
Yesterday i've updated Domoticz on RPI with ./updaterelease;
finally domoticz instance came up in MyDomoticz.

But when i click on green icon it shows background of my domoticz, then returns to instances list. Unfortunately i cant see now the log file, maybe in the evening.

-----------------
OK the message was "browser cache failed" and login dialog wont appear.
When i change it to Firefox everything works fine!!!
THANKS!!!!!!!

Domoticz instance goes offline in the MyDomoticz portal, and does not come back before Domoticz is restarted. In the logs I have:
Domoticz is connected to the network via Huawei 4G router B593.

This exception seems to come from CProxyManager::StartThread(), perhaps the StartThread is not rescheduled if it fails?

EDIT: I think I got it fixed: https://github.com/domoticz/domoticz/pull/978

Got the same error as user above.
For me connection was lost "forever" when I've changed the password in settings via domoproxy.
Connection was lost, domoticz was freezed. After restart i cant connect - host not found.

I'll provide logs soon.

Hi Everyone,
is the service down?
Just wondering, nobody is talking about it and I cant connect it for few days.
Thanks

Hello. My instance was working fine after making new account few days ago.
Till now - MyDomoticz was offline (maybe yesterday)? since then i have no instance od the control panel.
Will my domoticz be stable in the future or its only for educational purpsoes and it will disappear soon?

ArturK wrote: The problem with the dashboard.

If I choose a floor plan as the dashboard mode (normal, compact, mobile and floorplan options) in the Domoticz settings, in the upper menu the button "Floorplan" (between Dashboard and Switches) disappears and the link http://192.168.1.5:8080/#/Dashboard doesn't exist. When I click on "Dashboard", the address is "http://192.168.1.5:8080/#/Floorplans" not "http://192.168.1.5:8080/#/Dashboard". I prefer this, because floorplan is my favourite.

In this case, trying to connect from my.domoticz.com to local domoticz server by pressing the green man icon is impossible. This is because mydomoticz tries to connect with "https://my.domoticz.com/mydomoticz/dashboard#Floorplans".
In case, when the dashboard in domoticz is different than floorplan, when I click green man icon in mydomoticz, it connects with address "https://my.domoticz.com/my/3...4/#/Dashboard" and all works fine.

Please fix it, thanks.

Could you post this here? https://github.com/domoticz/mydomoticz/issues

Toni wrote:Domoticz instance goes offline in the MyDomoticz portal, and does not come back before Domoticz is restarted. In the logs I have:

Code: Select all

2016-11-13 07:16:30.112  Error: PROXY: timeout occurred, reconnecting
2016-11-13 07:16:45.115  Error: PROXY: StartThread(): Exception: resolve: Host not found (non-authoritative), try again later

Domoticz is connected to the network via Huawei 4G router B593.

This exception seems to come from CProxyManager::StartThread(), perhaps the StartThread is not rescheduled if it fails?

EDIT: I think I got it fixed: https://github.com/domoticz/domoticz/pull/978

Probably this is a network or DNS configuration issue on your end. That StartThread() is not rescheduled is on purpose. We don't want to reconnect if there´s no network to avoid error messages every 15 seconds.

Yeah, MyDomoticz has been offline for a bit.
It´s back now on a fresh host and available for the people who run a recent beta.
Unfortunately I don´t have time to respond immediately in case an issue arises. So there´s no SLA kind of warranties of this service.
Thanks to all the people who have helped testing so far.

°° Rene

chimit wrote: Probably this is a network or DNS configuration issue on your end. That StartThread() is not rescheduled is on purpose. We don't want to reconnect if there´s no network to avoid error messages every 15 seconds.

No, this had to be fixed (and was fixed by that pull request). Without this, any short network outage will cause Domoticz to not reconnect to MyDomoticz. For example, if you pull the ethernet cable for a short while, the MyDomoticz connection didn't come back until Domoticz was restarted. Imagine having Domoticz in some remote place, when having a short network outage in the 3G or 4G network...

Toni wrote:

chimit wrote: Probably this is a network or DNS configuration issue on your end. That StartThread() is not rescheduled is on purpose. We don't want to reconnect if there´s no network to avoid error messages every 15 seconds.

No, this had to be fixed (and was fixed by that pull request). Without this, any short network outage will cause Domoticz to not reconnect to MyDomoticz. For example, if you pull the ethernet cable for a short while, the MyDomoticz connection didn't come back until Domoticz was restarted. Imagine having Domoticz in some remote place, when having a short network outage in the 3G or 4G network...

The problem was that all of a sudden the Domoticz's started reconnecting enlessly without any delay in between, causing a ddos on MyDomoticz.
I cannot "prove" that this was because of your patch. But it generated the same log line and it did start after applying your patch.
I promise will try to look into it more, when I get the time.

Ouch, sorry if I caused that... It should probably have some retry delay.

Anyway, without my patch all you need is to disconnect the network for a short while -> MyDomoticz connection never comes back. It's very easy to reproduce this for example with the Windows version, just by placing a breakpoint on that line of code, and then pulling the network cable for a while.

Toni wrote:Ouch, sorry if I caused that... It should probably have some retry delay.

Anyway, without my patch all you need is to disconnect the network for a short while -> MyDomoticz connection never comes back. It's very easy to reproduce this for example with the Windows version, just by placing a breakpoint on that line of code, and then pulling the network cable for a while.

The funny thing is. The Reconnect() function does have a time-out. So we're not 100% sure, but we wanted to better be safe than sorry.
Like I said, I will look into it again and put your code back as neccesary.

chimit wrote:

Toni wrote:Ouch, sorry if I caused that... It should probably have some retry delay.

Anyway, without my patch all you need is to disconnect the network for a short while -> MyDomoticz connection never comes back. It's very easy to reproduce this for example with the Windows version, just by placing a breakpoint on that line of code, and then pulling the network cable for a while.

The funny thing is. The Reconnect() function does have a time-out. So we're not 100% sure, but we wanted to better be safe than sorry.
Like I said, I will look into it again and put your code back as neccesary.

Toni, I put your idea of catching resolver errors back in it, just in a bit of another form.
The suspected bug was probably of another cause. But your patch made it trigger.
The ContinueConnect() function gets invoked by an async_wait command. I suspect that the timer gets cancelled under some circumstances, which basically turns the timeout into 0.
Would you be so kind to check out my "iteratorbug" pull request and see if you see something wrong with it?
Also the resolver iterator was not correctly increased.

== Rene