HS Watch Address

[Warichet]

Is that really true?

Yes, Sir

Your status is triggered by the actuator port???

Please pardon my ignorance, but that is what I've understood from the help.

This is compleytely wrong, imho. Normally it is the other way round: Actuator port has status object as watch adress!

In my case, I've a Merten actuator, that has a status object, only for channel 1 . I've understood that I could "fake" a status object via the watch address, by monitoring the actual state of the actuator port. The funny thing, it works for a dimmer (seems not to work for 1 bit object)

Thank you for putting me right

[MatthiasS]

GA 0/6/21 the actual actuator port (1.1.155#A)
GA 0/6/22 status, watch address triggered by 0/6/21

Is that really true?

Your status is triggered by the actuator port???

This is completely wrong, imho. Normally it is the other way round: Actuator port has status object as watch adress!

[Warichet]

Would someone be so kind to check if a Watch Address on a 1bit object can be seen in the HS Monitor ?

No one has a HS and the HS Monitor and a Watch address and 5 min to help a desperate newbee ?

I would be very happy if someone could do the test. I'm reaching the "end of the road" due to my lack of experience and no other system to compare with.

Thank you in advance

[Warichet]

Would someone be so kind to check if a Watch Address on a 1bit object can be seen in the HS Monitor ?

Thank you

[Warichet]

Hi Gaston,
Nice to hear from you again

But anyway I am asking myself why you need watch addresses for Aktuator status objects.

Ouups, pardon, I didn't make myself very clear and forgot to mention that this crummy actuator has no status object, hence the usefullness of the watch address

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.

OK, thanks. I haven't explored the central address function yet (still so many things to learn )

[Gaston]

Hi Raymond,

My first thought would be that the read flag is not set on the status object. But anyway I am asking myself why you need watch addresses for Aktuator status objects. Usually these get transmitted (assuming the T flag is set) at least when the state of the port changes. So there is no need to explicitely read them.

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.

Cheers,
Gaston

[Warichet]

Hi,

I've defined several "watch address", and they work fine, except one.
So, on the same actuator, I've defined following:

GA 0/6/21 the actual actuator port (1.1.155#A)
GA 0/6/22 status, watch address triggered by 0/6/21
When looking in the MS Monitor: it works, both GA are toggled together

GA 0/6/23 the actual actuator port (1.1.155#B)
GA 0/6/24 status, watch address triggered by 0/6/23
When looking in the MS Monitor: I see that only GA 0/6/23 is toggled. GA 0/6/24 doesn't move, seems to be dead.
I realize that the above statement might look crazy, but hélas, that's what I see.
NB: port 1.1.155#B *IS WORKING*, I hear it clicking.
NB: when I link GA 0/6/24 to 0/6/21 (it doesn't make sense, just for test) it doesn't work either.

How could I debug this problem ? Are there any known restrictions ? (didn't find any in the help).

Thank you for your hints