MyDomoticz - Testers wanted!

[chimit]

It seems that the headers of the lockfree queue in boost on the Raspberry are there, but the implementation is broken.
I replaced with with a std::queue. If you don't know what I am talking about, then just do a git pull again and try again.
I just tested myself and I can compile and link on the Pi.

[fhwessels]

I did a git pull and its working again

Sent from my YOGA Tablet 2-1050L using Tapatalk

[fhwessels]

Hi chimit I can't logon to domoticz against. The icon is just red every if I reboot Raspberrypi it stay red. Before when I had this problem a reboot fix.

Sent from my YOGA Tablet 2-1050L using Tapatalk

[Domosapiens]

fhwessels,
that is because you spam your readers with

Sent from my YOGA Tablet 2-1050L using Tapatalk

[fhwessels]

Hi Domosapienhs please explain why you saying I'm spamming?

fhwessels,
that is because you spam your readers with
Sent from my YOGA Tablet 2-1050L using Tapatalk

[kkc1983]

Hi chimit,

Would like to participate to test the MyDomoticz service, but i can't send PM yet.

[pasgabriele]

Hello chimit,
Would like to participate to MyDomoticz test, but i can't send PM yet.

[chimit]

Email me at [email protected].

[erik4281]

I can't send a PM yet, so just mailed you.

[chimit]

For all users who are interested in using this service: The MyDomoticz code is now in the master branch on Github.

Follow the steps on https://www.domoticz.com/wiki/Installin ... rom_Source and you will be all set.

== Rene

[bizziebis]

Thanks for your work. It's working without any problems!

[dynasticorpheus]

I am getting below error message so wondering if someone has a hint in which direction I should look to resolve this? Note that I am running domoticz on my mipsel based dreambox so big change I am the only one having this problem. I am on latest master and using boost 1.60. Everything else seems to work perfectly fine.

Code: Select all

Error: PROXY: Only wrote 0 of 76 bytes.

[chimit]

dynasticorpheus, I sent you a pm.

[JC38]

Hello,
Using the web page from mydomoticz.com to connect to remote or even local Domoticz is ok.
But I'm not successfull trying to use the remote one as a slave.

Here what I can see in the master log from the status and error tabs

Code: Select all

2016-01-04 20:32:32.963 PROXY: Notification received: slave "aqwerty987654321" online now.
2016-01-04 20:33:56.687 Error: PROXY: Read failed, code = 335544539. Reconnecting: short read
2016-01-04 20:34:07.487 PROXY: Authenticate result: success.

Here what I can see in the slave log from the status and error tabs

Code: Select all

2016-01-04 20:32:22.298 Error: PROXY: Read failed, code = 335544539. Reconnecting: short read
2016-01-04 20:32:32.609 PROXY: Authenticate result: success.
2016-01-04 20:39:06.827 Error: PROXY: Read failed, code = 335544539. Reconnecting: short read
2016-01-04 20:39:23.448 PROXY: Authenticate result: success.

Regarding the wiki :

In the “Allowed IP address” box, you can enter the (external) ip address that your Domoticz instance is allowed to connect from.

Is it "You can" or "you have to" enter the external ip address ?

[chimit]

Thanks JC38 for the bug report.
Your master and slave domoticz, on what platforms are they?

About your question: The allowed IP addresses box works the same way as usual.
So if you put nothing, it will ask you for your password.
However, if you put the external ip address from the host that you are browsing from, then you can log in from that machine (and all the other machines that have that external ip address) without a password.
Note: I assumed this works without having tested much.

== Rene

[dynasticorpheus]

dynasticorpheus, I sent you a pm.

Did not receive it (yet) ?

[JC38]

The slave is a Rpi B, the master a Rpi2

Since this morning, i'm not able to connect to the slave (I've tried to update the beta through the setup menu and after that, connexion through myDomcoticz was impossible).
I manage to restart the internet connexion so the Wan Ip has changed.
In mydomoticz, the slave is always green and with the old IP

I'm able to accessing the slave using a standard method. In its log, I can see : PROXY: Authenticate result: Maxinstances reached.

[chimit]

I must have not-tested well something then.
I suggest you disable master/slave communication through MyDomoticz for now, until I find time to look at it.
Anyway, your feedback is appreciated very much.
The zombie slave should disconnect eventually, which will allow your slave to reconnect again. This doesn't go automatically in this case. You will have to restart Domoticz or change one of the MyDomoticz settings in the settings menu. That will initiate a reconnect as well.
Apologies for the inconvencience.

== Rene

[JC38]

René, I haven't read your last post before doing my latest changes.
So at the Slave side, I have changed some settings in myDomoticz by disabling and enabling the 2 options (enabled and shared).

And here are the latest errors read on the master :

2016-01-05 19:11:22.932 Error: PROXY: Shared Server access disallowed, denying receive data request.
2016-01-05 19:11:23.167 Error: PROXY: Shared Server access disallowed, denying receive data request.
2016-01-05 19:11:23.168 Error: PROXY: Shared Server access disallowed, denying receive data request.
2016-01-05 19:11:23.168 Error: PROXY: Shared Server access disallowed, denying receive data request.
2016-01-05 19:11:52.866 Error: PROXY: Shared Server access disallowed, denying receive data request.
2016-01-05 19:11:52.980 Error: PROXY: Shared Server access disallowed, denying receive data request.
2016-01-05 19:11:52.981 Error: PROXY: Shared Server access disallowed, denying receive data request.
2016-01-05 19:11:52.981 Error: PROXY: Shared Server access disallowed, denying receive data request.
2016-01-05 19:11:58.015 Error: PROXY: Read failed, code = 335544539. Reconnecting: short read

[chimit]

If you disconfigure your master from using Domoticz (by using normal tcp access) these messages will go away.
Maybe later, I will want to be in touch with you about your Domoticz crashing when I get around debugging this issue.