Aeon Aeotec DSD37-ZWUS Repeater Off/On Toggle?

Is there a better .xml and .json file to use than the GenericIO1 device for Aeon Extender/Repeaters? The generic file includes an Off/On toggle within the UI which doesn’t seem functional. (screenshot attached)

When adding an Aeon Aeontec DSD37-ZWUS Extender/Repeater on UI7, the following devicetype is used:
urn:schemas-micasaverde-com:device:GenericIO:1
D_GenericIO1.xml
D_GenericIO1.json

When toggling the device ‘On’ from within the UI, it switches back to ‘Off’ after a few seconds. It’s very confusing. I thought it was broken at first, but I speculate that the GenericIO1 device type includes On/Off functionality but that it doesn’t apply to this device. Does a more specific device type exist?

No, the Aeon repeater is a Z-Wave switch without a relay. It displays as a switch, but the switch doesn’t function, as you found out, because no relay exists.

So, what did you think were switching On and Off? The relay doesn’t control/power anything. Did you think you were powering the whole thing down?

Initially I thought the Off/On may have been toggling the relay functionality as ‘active’ or ‘inactive,’ until I saw that it was just using a generic device type.

The question still remains if a more specific device type or xml/json file exists which hopefully eliminates those unneeded UI elements? Having the device present but always showing its ‘Off’ status is not elegant and quite misleading.

Initially I thought the Off/On may have been toggling the relay functionality as ‘active’ or ‘inactive,’ until I saw that it was just using a generic device type.

The question still remains if a more specific device type or xml/json file exists which hopefully eliminates those unneeded UI elements? Having the device present but always showing its ‘Off’ status is not elegant and quite misleading. [/quote]

Sounds like you might what to change the start-up LUA to just hide the device all together.

[quote=“xycmu, post:3, topic:185874”]The question still remains if a more specific device type or xml/json file exists which hopefully eliminates those unneeded UI elements?[/quote]The answer still remains:

But, @integlikewhoa does offer a good option of completely hiding the device.

so since the thread ended, i was curious to know if the Device type was changed or left as a basic IO device.
If changed, does it operate as expected.

I also have UI7 with a bunch of repeaters through the house… Wanting to get better reception from the Fortrezz water sensors that keep failing to report back to the Edge… I have 7 water sensors, with 2 that keep failing to communicate.

I assumed it was a communication error, and was hoping the repeaters would help solve the issue. After install the same two sensors are failing to communicate.
I have done the Heal process… no help.

I thought that since the repeaters were off status…tried to turn them on… no avail… they dont turn on…lol

any insight?

[quote=“symonsaz, post:6, topic:185874”]so since the thread ended, i was curious to know if the Device type was changed or left as a basic IO device.
If changed, does it operate as expected.

I also have UI7 with a bunch of repeaters through the house… Wanting to get better reception from the Fortrezz water sensors that keep failing to report back to the Edge… I have 7 water sensors, with 2 that keep failing to communicate.

I assumed it was a communication error, and was hoping the repeaters would help solve the issue. After install the same two sensors are failing to communicate.
I have done the Heal process… no help.

I thought that since the repeaters were off status…tried to turn them on… no avail… they dont turn on…lol

any insight?[/quote]

I wanted to find out the out come of this as I have the same problem now with my sensors and a couple other things like the flashing red alarm. Of course it has to be the units that I need to be working most! Did you get a fix for the problem? I have U7 as well. Thanks