HS Watch Address

[Michel]

Unfortunately I do not use the HS-Monitor, so testing is not possible.

But in order to check whether the actuator replies to a READ-Telegram correctly, just send a value-read telegram on the appropiate Groupaddress via the ETS or via the "Befehl" "Abfragen" via the HS.

If it works, you should receive the actual state of that channel or you will see the answer in the HS-EIB-Monitor accessible via hslist if activated at "Systemlisten" in the Experte.

[Warichet]

in order to check whether the actuator replies to a READ-Telegram correctly, just send a value-read telegram on the appropiate Groupaddress via the ETS or via the "Befehl" "Abfragen" via the HS.

Thank you for the simple, yet clever tip

If it works, you should receive the actual state of that channel

Yes, indeed, I see it in the ETS GA monitor, very consistent .
The display in the HS Monitor doesn't change

or you will see the answer in the HS-EIB-Monitor accessible via hslist if activated at "Systemlisten" in the Experte.

Nice, haden't used it, yet.

Sooo, my tentative conclusion:
the HS Monitor doesn't display the Watch Address correctly.

Any chalenger ?


PS: I know, the HS Monitor is not a supported tool.

[Warichet]

Sooo, my tentative conclusion:
the HS Monitor doesn't display the Watch Address correctly.

Any chalenger ?

Digging an old topic.
So far, no reply for the challenge.

After having read & re-read what has been said here, I'm still at square one, no clue about this crummy watch address.

Would someone be so kind to test it for me ? please ?
No, no, don't tell me how it should work, I'm convinced. I'd like to know IF it works as advertized.

Thank you very much for the effort

[makki]

Will try tomorrow, promised, as this thread brought me the knowledge (today) of existance and what Watch-Adresses are good for; there're some ideas saving me several current logic-constructions to read adresses after changes to other ones..

Makki

[makki]

If I got you right, after flashing the HS 20 times today anyway (Troubleshoot APC..) I tested this:
It works fine, after sending a vlaue to a KO used as second listening address on an actuator without feedback, the values get read and are also visible in the HS-Monitor.

It just confused me a little bit that you have to add the Watch-address under the KO to Query, as I understood from the docu it's the other way around..

Makki

[Warichet]

Hi Makki,

Thank you for sharing the results of your tests.

after sending a vlaue to a KO used as second listening address on an actuator without feedback, the values get read and are also visible in the HS-Monitor.

I fear I understood you . To make things clear, let's take a simple example.

Suppose we have a @#tua&r with no status feedback, say: 1.1.101
In ETS, following GA are defined
0/0/101 Spot L5A. On/Off (linked to port #H of the actuator 1.1.101, flags: K L E T)
0/0/102 Spot L5A. Status (linked to nothing, will be used in the HS)
Those GA are imported/created in the HS.
So, in the HS, under 0/0/102, I've created a watch address pointing to 0/0/101, which is the only one "knowing" the status of the actuator for sure.
In the HS, Visu, a dynamic icon points to 0/0/102, supposed to reflect the current status of the actuator, it doesn't work.

One alternate way of doing is to bypass this watch address stuff all together and link the status of the Visu to 0/0/101, basta !

Thank you for pointing me to my mistake(s)

[Warichet]

By checking all posts again , I've re-read Gaston's post

You may then use the Status object in zthe HS as central address for the actual switching object to keep it in sync with central commands.

Soooo, same player shoot again:

Suppose we have an actuator with no status feedback, say: 1.1.101
In ETS, following GA are defined
0/0/101 Spot L5A. On/Off (linked to port #H of the actuator 1.1.101, flags: K L E T)
0/0/102 Spot L5A. Status (linked to nothing, will be used in the HS)
Those GA are imported/created in the HS.
So, in the HS, under 0/0/102, I've created a CENTRAL address pointing to 0/0/101, which is the only one "knowing" the status of the actuator for sure.
In the HS, Visu, a dynamic icon points to 0/0/102, supposed to reflect the current status of the actuator.

It works.
Oh well .....