IPX800 Binding info

I understand what you mean, is better that I try to revert to FW 3.05.62. In this way I can test your v2_binding, and we know if it is possible to revert the firmware :wink:
Let you know !

Yesterday I did some test

  1. I revert IPX800_v3 to FW 3.05.62 --> It is possible (little boring but possible :wink: )

  2. Test IPX800_binding_v2
    FW 3.05.62 “Send data on status change”–>ON
    OUTPUT
    Command from OH to IPX800 --> OK
    Change status on IPX800 --> update item on OH -->OK
    INPUT
    Change status on IPX800 --> update item on OH -->OK
    COUNTER
    Change value when change status on IPX800 --> update item on OH -->OK
    Change value on IPX800 --> update item on OH at the first change status on IPX800
    ANALOG
    OH item is update only one time after the binding install, at the first change status on IPX800
    Then the item on OH do not update anymore
    In my opinion in the binding Analog item do not work correctly…it would be better if it were periodically updated (example every second … or parametric)

  3. IPX800 Firmware version
    FW 3.05.70 have a bug and do not accept TCP command when you set “Send data on status change–>ON" the OH binding don’t work
    https://forum.gce-electronics.com/t/tcp-et-retour-du-status-des-entrees-et-sorties/7916/5
    FW 3.05.62 the OH binding work (except for analogue) but I have some instability problem (that I solve with 3.05.70)
    FW 3.05.74b Is a beta release (that I found in the forum above) that I have in test. It does not have the instabilities of the 3.05.62 and it does not have the bug of the 3.05.70. The v2_binding works like FW_3.05.62

Ok, that’s cool.
I’m going to take a look at the ANALOG entry.
Is COUNTER working correctly ? I don’t clearly understand your topic on this

COUNTER works correctly !

Can you test this version ? I think I maybe made a mistake in histeresis logic - so I removed it for testing.

Test GCE_2.5.8_binding

  1. FW 3.05.62 “Send data on status change”–>ON
    OUTPUT
    OK
    INPUT
    OK
    COUNTER
    OK
    ANALOG
    Now Analog channel work like COUNTER
    OH item is update when (or every time that) there is a change status on IPX800 (and IPX800 send data)
    “change status” = an INPUT change or an OUTPUT chance
    For the COUNTER channel ( it counts how many times an INPUT change) ,it is OK, but for Analog is not OK.
    In my opinion it would be better if it were periodically updated (example every second, every minute … or someting else)
    For example I use an analog channnel to measure brightness, and in a rule, when brightness becomes <1% I turn ON some lights.
    If there is no change of INPUT or OUTPUT on IPX the OH item linked to Analog is not updated.
    I hope I explain myself… sorry for my english

No problem @valefranch, I will try to test and investigate this issue during the week-end.

I think I get it : Analog and Counters does not generate push from the IPX to the binding when they are changed, so yes, I think you’re right, I shall pull these informations on the recurring basis.

Can you please test this version. I did add a configuration item on Counter and Analog channels that defines the expected pull refresh rate.

The fact is the IPX does only send a M2M push message when there is an update on a digital input or digital output. The message sent contains informations for all ports - so unless there is an update on one of those ports, nothing is seen on the binding side. The tricky thing is due to the asynchronous communication mode.

Hi,
I test this last version, but I think there is a problem!
OUTPUT
Command from OH to IPX800 --> OK
Change status on IPX800 --> nothing happens
INPUT
Change status on IPX800 --> nothing happens
COUNTER pull refresh rate 1000 (I also tryed 5000 and 500)
nothing happens, nothing is read from OH (even if there is a “Change status” on IPX and IPX send data)
ANALOG pull refresh rate 1000 (I also tryed 5000 and 500)
nothing is read from OH

It seems that OH is not receiving signal from IPX800

Mmmm really weird. Have you tried deleting the IPX thing from OH and recreate it once the new binding version is in place ?

Yes I delete the thing and recreate it, I try also to stop and restart OH_2.4 but nothing change.

Then I test your binding with OH 2.5.4 installed in an other computer and magically it works :grinning:


Then I change pull refresh rate and It works
The next days I try to do other test and let you know

1 Like

Complete Test IPX800 V3
binding GCE_2.5.8_binding (with pull on Counter & Analog)
openHAB version 2.5.8 stable
OUTPUT
Relay 1-8 --> OK
Relay 9-32 --> don’t find channels in the v2 binding
INPUT
Digital Input 1-8 --> OK
Digital Input 9-32 --> don’t find channels in the v2 binding
COUNTER
Counter 1-8 --> OK
ANALOG
I test Analog channel 1, 2 e 3
I use 2 kinds of binding: HTTP (that I already use) & GCE and create 6 ITEMS on OH linked to them.
I set pull refresh rate = 5000 (in both binding) and Histeresis = 0 for all the channel
I save the data every minute in rrd4 database
The value are similar (in my opinion little differences are due to the moment of pull request) for channels Analog_1 and Analog_2, but I seem to see a different behavior for Analog_3! Little strange, Histeresis?
@glhopital What do you think about it?



Yes, I think difference between http / gce comes from little time shift of the polling. I do not get what you point regarding A3

For inputs and outputs, I could add missing channels in the binding.

Regarding A3: I try to understand this behavior


that I did not see in A1 & A2…
I physically swapped the channels A2 with A3 , swapping the wires, and I see this behavior in A2!
There seems to be a filter in the GCE binding…but it is good: the signal is more smooth :slight_smile:
cheers

For me it looks like refresh period is not set at the same pace between the two approaches, or…could be that GCE item is an integer while HTTP item is a float ?

I try to set refresh period at the same pace:

HTTP binding
http.cfg
image
items


I don’t know very well what mean “10000” in REGEX, but changing it, the result do not change!

GCE binding
image
image

Integer vs Float
May be!!
but I don’t know where I can set it!

Maybe you can declare your http analog items as %d instead of %.1f

Hi
I declare http items as %d… and the http & GCE items have the same behaviour.
But after 2 days I see some differences


Detail
image

After a while channels 2 and 3 seem to stop refresh (or they refresh randomly).
I have observed the value: http value is correct with IPX800!
When you change something in IPX (es you close an input or command an output) the http & CGE value are alined.
Channel 1 is OK