Hager Domovea - Tipps & Tricks (Version 1.0: TJA 450, TJ 701A)

[JoergDr]

Home Status is a little bit special:

First, you cannot read out the current Home Status and assign it to a variable. You have to use a query to do that, like here where I additionally ask if the Home Status has changed (so I avoid unnecessary assignments):

Check Home Status.jpg
If these conditions are both true (Home Status changed and new Home Status is "At Home"), then you can assign a constant value to a variable of type "Home Status":

Assing Home Status.jpg

To set the assignment you have to select "Free Input" on the left side and then set the type "Home Status":

Type Select.jpg

Select Home Status.jpg

I didn't test it, but I am not sure if it is possible to make calculations with the type "Home Status". This might lead to unexpected results.

[JoergDr]

One more thing: you cannot use a trigger of the type "Home Status has changed", that does not work.

Instead you have to call a sequence when the Home Status enters or leaves a certain value:

Home Status Trigger.jpg

[AchillesGr]

i followed your steps,

i tried to set the home status to "night" so i set the two "input trigers" as the image below and i sett the action as a mathematical equation to change the output
when i press the "test" it works .
when i change the status from the pc client from at home to "night" bithing happens,
it seems that the problem is in triggers and not at the actions.
i set the triggers and actions:


action:
image.png



trigger:
image.png

also noticed that the screen is a bit diferrent than yours. the look of the two cells at above screen is different.
am i at the wrong tab?

"You have to use a query to do that" did you mean triggers?

thanks!!

[JoergDr]

Yes, you are wrong.

Home Status cannot be used as a trigger, only as a condition.

Please see my last post. #1592

[AchillesGr]

ok.Then at the #1591 what are you trying to do? if home status do not work as triger is it neccesary?

my main idea was to program two sensor buttons one for short absence and one for At home for simplicity when i enter or leaving the home.

So far i create individual sequences for "at home" , "absence" , "night"..... that each one plays when i enter each mode and sends to a Group Address "Home Status" the numbers "1" , "2" , "3" values to the bus.

also a will create sequences for the oposite. When it reads "1" from the bus then switch to "At Home" and so on...
i could not think any other way to comunicate the home status with button sensors on the bus.

thanks

[JoergDr]

At #1591 im am demonstrating how to make a decision about the current Home Status and store it in a variable. I think that was what you were asking for.

I have the same situation: when I leave my home I set the home status to "absent". I do this with an iPad mini I have mounted at the side of the main door.

But you can easily use sensor buttons for this. Just trigger the same sequence for all involved sensor buttons and compare the current status of the sensor buttons with the current Home Status (remember: in comparisons it is possible to compare against the actual Home Status). You don't need a variable for that and no transformation to numerical values, nor any Group Address.

Now, if the desired Home Status is not active, just set the desired Home Status with the "Home Status" command to the desired one. Then, upon change of the Home Status, you can call other sequences that perform the desired actions, as I have shown it in #1592.

This solution ensures that Home Status changes are recognized and perform the desired actions even when the Status has been changed by the Domovea GUI (like I do it with the iPad).

[AchillesGr]

yes that is what i am going to setup.
so far i am trying to control the domovea with a group adress and 1byte data type sending numbers 1,2,3,.... for the home statuses. Domovea can send those values to the bus BUT not the vice versa. i tried from the ETS to send 1byte numbers to change the home status but nothing happens. Not recogbized from domovea. tried many data types too with no results. Domovea easyly recogbizes 1bit on/off but not the 1byte....
Thinking to setup some Group Addresses for each one of the homes statuses with 1bit true/false to make sensors comunicate with the domovea and change its status.is that the way you did it?

what do you mean to "compare the current status of the sensor buttons with the current Home Status ?Do you mean to set feedback objects of the buttons ?


"Now, if the desired Home Status is not active, just set the desired Home Status with the "Home Status" command to the desired one" with multiple sequences each one for each status?and seting domovea to "listen" the dedicated Group Address?

[JoergDr]

Ok, what you want should be manageable...

First you should know some points about sequences:

If you use a GA as trigger of a sequence or inside of a sequence to make a decision (if GA = ...), then it must be ensured that Domovea can read from the GA (the so-called "L-Flag" must be set for the Communication Object. This flag might be named different in English).

Furthermore, the data type of the GA must match exactly the type that is defined in Domovea, in your case I assume "1-Byte unsigned". Look in the description of your sensor what datatype it sends.

If any of this conditions are not met, the Domovea stops the sequence immediately, without any notice. You can add commands in case of any error to be informed when this happens. For example this could be a sequence that pops up an error message on the clients. It is important to be informed of errors, otherwise you don't understand what's going on.

Error Sequence.jpg

These error handling commands are only an example of the error handling I use. For your testing it is sufficient to just call one sequence that pops up an error message. You will find more about error handling many many pages before in this thread.

Now, lets assume you have one sensor that issues different values of the type "unsigned byte" on GA 1/1/0. For example "1" for "at home", "2" for "absent" and so on.

You should design one sequence to handle that. In case you have more than one sensor, you need to have different GA's and you will need another sequence for every GA, otherwise you cannot distinct which sensor triggered your sequence.

Sensor Trigger.jpg

This should call the sequence on any data that is received from the sensor. Try if it works now by issuing a popup message:

Popup message.jpg
Ok, if that works, delete the popup message and add an "if" statement to decide what is to be done:

First If Statement.jpg

"If GA 1/1/0 (type 1-Byte unsigned) = 1 AND Home Status <> "At Home"" then set Home Status to "At Home":

Set Home Status 1.jpg

Then add another branch to handle Home Status "Absent" (1-Byte value 2):

Second If Statement.jpg

Set Home Status 2.jpg

and so on...
As you will see, you can nest only 3 "if..." statements, but you can just open another line when you need more cases:

nested statements.jpg

That is all. The sequence changes the Home Status of the Domovea according to the byte value it had received from the bus.

As I have already said, the reaction on the Home Status change should be done in one or more other sequences, called by the "Home Status change" page:

Home Status changed.jpg

I hope this will help you implementing your desired functionality.

Have a good time
Jörg

[AchillesGr]

Jörg ,
Many thanks for your help!
i am trying to set up as your instructions . Hope to manage that.
so far i couldnt find the wright data type in domovea side for the group address i set. .
tried "1-Byte unsigned" and also many type but domovea cannot read it. i am sending from ETS and not from a sensor.Parhaps this is the problem?

meanwile i setup diferent group adresses for each status each one send 1 bit.
also set a variable to change everytime with 1 bit reception acordingly and when this hapens immidiately i set a sequence for domovea to send back to the bus the new status so the sensors are "informed"
that worked but i have about 10 sequenses for doing that.is there a limit in how mwny sequences domovea can handle?

Yes you solution is much better....

thanks again

[JoergDr]

Ok, I just tested the trigger and reaction of the sequence.
As trigger I used GA 11/0/0 and declared it to be of type "1 Byte - unsigned" in domovea. Trigger "on any change" means on any data packet that is received from the bus. That triggers also, when the same byte is received many times, so that is exactly what we want.

Trigger.jpg

As reaction on the trigger I just send a 1-Bit Signal on GA 11/0/1. That is easier to detect in the ETS group Diagnosis.

Sequence.jpg

The data type is a 1-Bit Signal:

Acknowledgement.jpg

When you send from the ETS for testing, I would recommend to choose the data type 5.010 (unsigned 8-bit counter). This is just a 1-Byte number:

ETS Diagnosis.jpg
As you can see, on every sending of the 1-Byte number "1" the Domovea answers with a 1-Bit "1".
(Don't worry about "Garage Auf/Ab", this is just because I normally use the GA for another purpose).

As you can see, the Domovea triggers on 1-Byte numbers and reacts. So now you can implement your own sequence, with sending back the received status number (just read it into a 1-Byte variable and then send it back to the Status-GA of the sensor) and then setting Domovea's Home Status as I had shown before.

Good luck!
Jörg

Btw: Domovea has a limit of 50 sequences, but it's always a good idea to use as few as possible of them.

[AchillesGr]

Ok,that worked...
Jörg you helped a lot and i am gratefull for your time.
is there a way to run the configuration tool without the domovea itself ?i would like to exersise some times in my office gree time while domovea is instaled at home.
thanks!

[JoergDr]

Good Morning,
yes, you can do that in two manners:

1. use the local Domovea Server to be installed on a windows machine.
That way you can import your previously exported configuration and work on it - but you cannot test anything as the server software has no connection to the KNX bus.

2. use a remote control software like TeamViewer. This allows you to control your home PC remotely. But keep in mind that for installing a software like that you need the permission from your boss - except you are the boss yourself.

[tandem]

Hallo,
vielleicht kann mir jemand helfen, seit einiger Zeit funktionieren die Android Domovea Clients nicht mehr:

• Windows-Computer (vor 6 Monaten auf Win 11 upgedated) mit Domovea Server 3.7.0.1 Server. Der virtualisierte Server erst Win8, Win10 und jetzt Win11 Server läuft seit vielen Jahren ohne Probleme)
• Laptops über Wlan mit Domovea-Client (Domovea läuft ohne Probleme)
• PCs über Ethernet mit Domovea-Client (Domovea läuft ohne Probleme)
• Android Clients mit unterschiedlichem Software/Hardwarestand (Samsung Tablet, neue und alte Android Smartphones) zeigen plötzlich beim Start einen Verbindungsfehler.
• Einige Androids hängen an der Wand und haben keinen Internetzugang, werden also nie upgedated
• auch bei einer Verbindung von außen über VPN tritt der Fehler bei Android auf, beim Laptop nicht
• PC-Clients laufen weiter ohne Probleme
• Android Clients die verbunden sind laufen solange bis die App neu gestartet wird

Ich kann den Fehler mit den Androids kurzfristig beheben, wenn ich den Windows 11 Computer mit dem Domovea-Server auf einen Stand vor dem Fehler zurücksetze (da es eine VM ist über einen Snapshot). Nach einiger Zeit (Stunden/Tage) tritt der Fehler wieder auf.
Dienst- oder Rechner-Neustart bringt nichts. Firewall ein/aus auch nichts.

Erst dachte ich die Virtualisierung verursacht eventuell den Fehler. Ein auf einem neuen Win11 Laptop mit allen Updates installierter Domovea Server zeigt jedoch das gleiche Problem mit einem Unterschied:
Bein Verbindungsaufbau mit Android kam sofort der Verbindungsfehler.
Mit dem PC-Client ist alles ok.

Der Domovea Support hat mir nach einem Monat mitgeteilt, dass sie den Fehler nicht kennen und die alte Version V1 nicht mehr unterstützt wird!!

Danke ...

[JoergDr]

tandem

Die Domovea hat ein Maximum von 20 gleichzeitig verbundenen Clients, soweit ich weiss.
Versuch doch mal die Domovea neu zu starten, falls Du das nicht bereits gemacht hast. Vielleicht hilft es ja.
Den Neustart kann man im Domovea Konfigurator auslösen, ohne das Gerät ausschalten zu müssen.

Jörg

[andre12]

Hallo,


Ich habe ein kleines Problem mit einer Sequenz

diese Steuert meine Sprenger und schaltet mit einer Verzögerung diese nacheinander ein und aus.

Wen die GA 0/6/13 eine 1 sendet startet alles
aber ich bekomme die Sequenz nicht gestoppt bis sie komplett durchgelaufen ist wen die GA 0/6/13 0 Sendet
auch wiederholt sich die Sequenz teilweise bei wiederholtem senden der 1 auf der GA 0/6/13 wie kann ich das vermeiden
0/6/18 ist der Status
0/6/13 Schalten
jedoch ist die GA in der ETS ohne Verknüpfung genutzt wird die GA nur über die Domovea oder Youvi als Schalter

stehe grade irgendwie auf dem Schlauch
könnte mir bitte jemand nen Tip geben

Bye Andre