MAX! home automation 1.3 released

MAX! home automation 1.3 released

[Dmitry A. Kazakov]

MAX! home automation is a GTK+ application to manage ELV/eQ-3 MAX! 
cubes. A cube is a gateway to a network of radiator thermostats, shutter 
contacts etc.

http://www.dmitry-kazakov.de/ada/max_home_automation.htm

Changes to the previous version:

- MQTT server added;
- LAN discovery by default scans all known interfaces;
- Settings page allows explicit setting of the host address to scan or 
cube address to connect.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de

Re: MAX! home automation 1.3 released

[tonyg]

Has this now been separated from the Components Library?

Re: MAX! home automation 1.3 released

[Dmitry A. Kazakov]

On 01/06/2016 11:52, tonyg wrote:
> Has this now been separated from the Components Library?

No, it still uses Simple Components and some other libraries.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de

Re: MAX! home automation 1.3 released

[tonyg]

Great, Thanks, would of made some major problems for me if it had !

Re: MAX! home automation 1.3 released

[tonyg]

I was wondering if you had considered functions on adding rooms and naming the devices for the home automation client, and assigning devices to room.

Maybe I could do this as a contribution. I might need some pointers ha!

Re: MAX! home automation 1.3 released

[Dmitry A. Kazakov]

On 03/06/2016 01:04, tonyg wrote:
> I was wondering if you had considered functions on adding rooms and
> naming the devices for the home automation client, and assigning devices
> to room.

Right I wanted it too. The problem is that it was not reverse-engineered 
yet.

> Maybe I could do this as a contribution. I might need some pointers ha!

You are welcome. The main source of information is here:

    https://github.com/Bouni/max-cube-protocol

It describes pairing of a new device, and I implemented that, but the 
rest, all the commands needed to maintain device names etc are missing.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de

Re: MAX! home automation 1.3 released

[tonyg]

I had some problems with the old version with now have cleared up with the new elv (3qMAX) cube software. I am thinking they might be performance issues now because I am running them on the Pi.
   These are that I am overriding the procedure which delivers message from the cube, and putting the data received in a protected object. I only seem to collect some of the messages Are you running yours on a desktop?

Re: MAX! home automation 1.3 released

[Dmitry A. Kazakov]

On 06/06/2016 01:38, tonyg wrote:
>
> I had some problems with the old version with now have cleared up
> with  the new elv (3qMAX) cube software. I am thinking they might be
> performance issues now because I am running them on the Pi.
> These are that I am overriding the procedure which delivers message
> from the cube, and putting the data received in a protected object. I
> only seem to collect some of the messages Are you running yours on a
> desktop?

Yes, but you cannot lose messages, it is TCP/IP and all callbacks go 
from the I/O task context. The ELV protocol is half-duplex, there is no 
way to miss anything within a session.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de

Re: MAX! home automation 1.3 released

[tonyg]

Thats very useful information. I'll do a test programme to illustrate the issue I'm having.

Re: MAX! home automation 1.3 released

[tonyg]

Further to your note that tcp ip does not lose messages I added the trace command to my example which inherits the elv_client_object and overrides the data_received procedure.

I took the trace messages out from your test_elv_ test program then diff'ed them with trace messages from my example -- I got the following which seemed to suggest the trace messages were very similar.
-- START OF DIFF
tony@wb:~$ diff q1.txt q2.txt 
1,4c1,3
< MAX! cubes discovered:
< ---------------------------------
< 192.168.1.85 eQ3MaxAp LEQ1324749
< ---------------------------------
---
> 2016-06-08 13:35:33.70 : Start of task - before rendezvous
> 2016-06-08 13:35:33.70 : Post rendezvous
> 2016-06-08 13:35:33.70 : STATUS Ending PI APP
7c6
< 192.168.1.85:62910 > |H:LEQ1324749,1158e5,0113,00000000,0df75d8e,0a,32,100608,0a09,03,0000%0D%0A| 0..69
---
> 192.168.1.85:62910 > |H:LEQ1324749,1158e5,0113,00000000,0c3b4a32,01,32,100608,0d23,03,0000%0D%0A| 0..69
182,183c181,182
< 192.168.1.85:62910 > |L:CxC1AgkSGAAkAAAACw+n/AkSGAAmAAAACxCgdgkSGAAhAAAABgXDuAk| 24..80
< 192.168.1.85:62910 > |AAAsRPx4JEhkAIQAAAAsQtKoJEhgAIQAAAAwJZ4YJEhkEIQAAAMwGD07cCRISCxE9qAkSGAAYAAAACxC| 0..79
---
> 192.168.1.85:62910 > |L:CxC1AgkSGAAhAAAACw+n/AkSGAAkAAAACxCgdgkSGAAhAAAABgXDuAk| 24..80
> 192.168.1.85:62910 > |AAAsRPx4JEhkAIQAAAAsQtKoJEhgAIQAAAAwJZ4YJEhkEIQAAAM4GD07cCRIQCxE9qAkSGAAhAAAACxC| 0..79
185c184
< 192.168.1.85:62910 > |ogkSGAAkAAAACxC2JAkSGAAmAAAADAlzFgkSGAQmAAAA1AsS4wgDDAAAAAAAAAwJcyUJEhkEIQAAAM8M| 0..79
---
> 192.168.1.85:62910 > |ogkSGAAkAAAACxC2JAkSGAAkAAAADAlzFgkSGAQkAAAA7gsS4wgDDAAAAAAAAAwJcyUJEhkEIQAAANIM| 0..79
187c186
< 192.168.1.85:62910 > |ZZtCRIYBCQAAADLDAlYcAMMAAAAAAAAAAsQtjAJEhkAIQAAAAsRPcwJEhkAIQAAAAwJcyAJEhgEJAAAA| 0..79
---
> 192.168.1.85:62910 > |ZZtCRIYBCQAAADPDAlYcAMMAAAAAAAAAAsQtjAJEhkAIQAAAAsRPcwJEhkAIQAAAAwJcyAJEhgEIQAAA| 0..79
189c188
< 192.168.1.85:62910 > |EMEZdgCRJYARgAAADNDAlb8AkSGAQhAAAA2A==%0D%0A| 0..39
---
> 192.168.1.85:62910 > |gMEZdgCRJYASEAAADXDAlb8AkSGAQhAAAA2g==%0D%0A| 0..39
tony@wb:~$ 
--******END OF DIFF

when I run your test programme I get all the messages, I get all the trace messages for the devices in my own example but I am only getting about half the messages put into a PO. Since the PO places them inside the overidden data_received procedure , I can't see how half the messages are disappearing.

Re: MAX! home automation 1.3 released

[tonyg]

Nor do I. I don't seem to be getting responses from quite a few of the devices. The devices do seem to be working normally otherwise though. 

Its a mystery :)

Re: MAX! home automation 1.3 released

[Dmitry A. Kazakov]

On 10/06/2016 13:02, tonyg wrote:
>
> Nor do I. I don't seem to be getting responses from quite a few of
> the  devices. The devices do seem to be working normally otherwise though.

Is the cube that sends responses not the devices.

Is it possible that you send l-requests too frequently before reading 
the response out?

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de

Re: MAX! home automation 1.3 released

[tonyg]

Maybe :) . Theres a cap on the amount of radio traffic, is this implemented by the cube or the JScript browser app (looking like its the cube judging by this). And theres 20 devices in the house. 

What I know is is correct at the moment is I should rewrite my Pi program!

Thanks again for your input Dmitri! You are always helpful.

Re: MAX! home automation 1.3 released

[Dmitry A. Kazakov]

On 13/06/2016 11:26, tonyg wrote:
> Maybe :) . Theres a cap on the amount of radio traffic,

Yes, of course. The number of wireless slots left free to communicate is 
returned from the cube in response to some commands.

You can monitor it in order to keep the traffic low. However this should 
not affect the L-command, because that must not cause any additional 
wireless traffic.

> And theres 20 devices in the house.

I know from other users that the traffic gets quickly chocked if the 
application tries to control the thermostats manually. E.g. by sending 
the set temperature to all thermostats each second, instead of 
programming them to run in the automatic mode.

Also the MAX! home automation tries to get the measured temperatures 
from the radiator thermostats. This involves wireless traffic and some 
commands to "massage" the thermostats, because they do not send the 
measured temperature on their own. You may look into this too, e.g. to 
increase the timeouts when a temperature measurement is counted 
"obsolete" or to turn this out completely.

> Thanks again for your input Dmitri! You are always helpful.

You are welcome.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de