Aeon labs micro switch Node error when switching from wall

[Sergio]

I hope someone can give me a hand on this. Please, please.

I'm using an Aeon Labs Zwave-Stick and an A.L Micro-switch to control outside lights (gen 1 I guess). Pairing and detecting it's all ok, and I can control the switch from domoticz without issue.
But as soon as I switch from the wall switch, things go bad. First, Domoticz does not detect the change in state. Sometimes, after a big while, it detects.
But always after a while the node is marked as dead.
Can someone give me a hand? I just bought this unit for testing before buying house wide sets, but I'm stuck on this problem several months ago without arriving to a solution.

The switch has to have polling marked?
What's the recommended polling interval in the stick configuration (only have one switch)?
It's necessary or the switch should send it's state immediately?

Also I can't add the microswitch without opening the wall switch and pushing the micro-switch button. So I always have to take the Zstick with me and dismantle the wall switch. Is it normal?
If so, Would be a nightmare to do it @ the house.

Thanks in advance.

[Sergio]

This mid-day at home, I've made the following:

First I've tried to re-add the switch from software, by turning the wall switch, but it didn't appear in the program:
That's the log:

Code: Select all

2015-03-27 15:11:51.676  Incoming connection from: 192.168.11.101
2015-03-27 15:12:00.506  Hardware Monitor: Fetching data (System sensors)
......
2015-03-27 15:13:17.270  New sensors allowed for 5 minutes...
2015-03-27 15:13:17.270  OpenZWave: Node Include command initiated...
2015-03-27 15:13:30.704  (ZWaveStick2) Lighting 2 (Unknown)
2015-03-27 15:13:30.847  Hardware Monitor: Fetching data (System sensors)
2015-03-27 15:13:37.048  ZWave: Stopping Controller command (Timeout!)
2015-03-27 15:14:00.950  Hardware Monitor: Fetching data (System sensors)

I removed the zwave stick. And opened the switch box.
Unpaired the switch using it's button.
Then unpaired again.
unpaired another time.
Then paired it again.

Then I went to domoticz and re-configured the stick (that lost the usb port).
Switch appeared in stick configuration so entered the name.
Then in devices there where two switches showing !???
So I started adding one and it appeared as dead in switches tab. So I deleted it and also disappeared from devices list.
I went for the other and was the good one.
I tried to switch from the software -> all good.
Switched from wall -> lights up but no response from domoticz.
Switched off then on from wall -> domoticz detected on.
Continued but no response from domoticz.

That's the log for the maneuver:

Code: Select all

2015-03-27 15:43:41.715  OpenZWave: Closed
2015-03-27 15:43:46.037  EventSystem stopped...
2015-03-27 15:43:46.457  OpenZWave: Starting...
2015-03-27 15:43:46.457  OpenZWave: using config in: /opt/domoticz/Config/
2015-03-27 15:43:46.602  OpenZWave: Driver Ready
2015-03-27 15:43:46.602  OpenZWave: Node Removed. HomeID: 25485099, NodeID: 5 (0x05)
2015-03-27 15:43:46.602  OpenZWave: New Node added. HomeID: 25485099, NodeID: 6 (0x06)
2015-03-27 15:43:46.664  OpenZWave: Value_Added: Node: 6 (0x06), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2015-03-27 15:43:46.664  (ZWaveStick2) Lighting 2 (Unknown)
2015-03-27 15:43:47.121  OpenZWave: All Nodes queried
2015-03-27 15:44:00.220  Hardware Monitor: Fetching data (System sensors)
......
2015-03-27 15:51:00.252  Hardware Monitor: Fetching data (System sensors)
2015-03-27 15:51:12.633  OpenZWave: Domoticz has send a Switch command! NodeID: 6 (0x06)
2015-03-27 15:51:12.633  (ZWaveStick2) Lighting 2 (Switch)    <============================= Switch was the name that already appeared at the phantom switch
2015-03-27 15:51:17.740  OpenZWave: Domoticz has send a Switch command! NodeID: 6 (0x06)
2015-03-27 15:51:17.740  (ZWaveStick2) Lighting 2 (Switch)
2015-03-27 15:51:25.488  OpenZWave: Domoticz has send a Switch command! NodeID: 6 (0x06)
2015-03-27 15:51:25.488  (ZWaveStick2) Lighting 2 (Switch)
2015-03-27 15:51:30.263  Hardware Monitor: Fetching data (System sensors)
2015-03-27 15:51:31.575  OpenZWave: Domoticz has send a Switch command! NodeID: 6 (0x06)
2015-03-27 15:51:31.575  (ZWaveStick2) Lighting 2 (Switch)
2015-03-27 15:51:52.658  (ZWaveStick2) Lighting 2 (Switch)
2015-03-27 15:51:52.658  OpenZWave: Received timeout notification from HomeID: 25485099, NodeID: 6 (0x06)
2015-03-27 15:52:00.273  Hardware Monitor: Fetching data (System sensors)
2015-03-27 15:52:30.284  Hardware Monitor: Fetching data (System sensors)
2015-03-27 15:52:32.859  (ZWaveStick2) Lighting 2 (Switch)
2015-03-27 15:52:32.860  OpenZWave: Received timeout notification from HomeID: 25485099, NodeID: 6 (0x06)
2015-03-27 15:53:00.293  Hardware Monitor: Fetching data (System sensors)
2015-03-27 15:53:22.701  OpenZWave: Domoticz has send a Switch command! NodeID: 6 (0x06)
2015-03-27 15:53:22.701  (ZWaveStick2) Lighting 2 (Luz porche)   <================================== That's the name I gave the "good" one.
2015-03-27 15:53:27.828  OpenZWave: Domoticz has send a Switch command! NodeID: 6 (0x06)
2015-03-27 15:53:27.828  (ZWaveStick2) Lighting 2 (Luz porche)
2015-03-27 15:53:30.306  Hardware Monitor: Fetching data (System sensors)
2015-03-27 15:53:46.349  OpenZWave: Domoticz has send a Switch command! NodeID: 6 (0x06)
2015-03-27 15:53:46.349  (ZWaveStick2) Lighting 2 (Luz porche)
2015-03-27 15:54:00.316  Hardware Monitor: Fetching data (System sensors)
....
2015-03-27 15:55:30.344  Hardware Monitor: Fetching data (System sensors)
2015-03-27 15:55:31.603  (ZWaveStick2) Lighting 2 (Luz porche)
2015-03-27 15:56:00.352  Hardware Monitor: Fetching data (System sensors)
....
2015-03-27 15:58:30.404  Hardware Monitor: Fetching data (System sensors)
2015-03-27 15:58:41.576  (ZWaveStick2) Lighting 2 (Luz porche)
2015-03-27 15:58:41.577  OpenZWave: Received timeout notification from HomeID: 25485099, NodeID: 6 (0x06)
2015-03-27 15:58:41.603  (ZWaveStick2) Lighting 2 (Luz porche)
2015-03-27 15:59:00.414  Hardware Monitor: Fetching data (System sensors)
2015-03-27 15:59:30.422  Hardware Monitor: Fetching data (System sensors)
2015-03-27 15:59:34.564  OpenZWave: Domoticz has send a Switch command! NodeID: 6 (0x06)
2015-03-27 15:59:34.565  (ZWaveStick2) Lighting 2 (Luz porche)
2015-03-27 16:00:00.432  Hardware Monitor: Fetching data (System sensors)

The switch still appears as valid.
It happens that if I enter the zwave panel and pust refresh value at the switch it gets the correct value and then domoticz has it when i come back. Sometimes only entering the panel syncs it.
The panel it's not functional to me. I can push, go come, change that doesn't do anything.

[Sergio]

That's the current configuration file:

Code: Select all

# cat zwcfg_0x0184df2b.xml
<?xml version="1.0" encoding="utf-8" ?>
<Driver xmlns="http://code.google.com/p/open-zwave/" version="3" home_id="0x0184df2b" node_id="1" api_capabilities="8" controller_capabilities="28" poll_interval="3000" poll_interval_between="false">
        <Node id="1" name="" location="" basic="2" generic="2" specific="1" type="Static PC Controller" listening="true" frequentListening="false" beaming="true" routing="false" max_baud_rate="40000" version="3" query_stage="Complete">
                <Manufacturer id="0086" name="Aeon Labs">
                        <Product type="0002" id="0001" name="Z-Stick S2" />
                </Manufacturer>
                <CommandClasses>
                        <CommandClass id="32" name="COMMAND_CLASS_BASIC" version="1" after_mark="true">
                                <Instance index="1" />
                                <Value type="byte" genre="basic" instance="1" index="0" label="Basic" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="0" />
                        </CommandClass>
                </CommandClasses>
        </Node>
        <Node id="6" name="LightSWPorch" location="" basic="4" generic="16" specific="1" type="Routing Slave" listening="true" frequentListening="false" beaming="true" routing="true" max_baud_rate="40000" version="4" query_stage="Complete">
                <Manufacturer id="0086" name="Aeon Labs">
                        <Product type="0003" id="001a" name="Micro Switch (2nd Edition)" />
                </Manufacturer>
                <CommandClasses>
                        <CommandClass id="37" name="COMMAND_CLASS_SWITCH_BINARY" version="1" request_flags="4">
                                <Instance index="1" />
                                <Value type="bool" genre="user" instance="1" index="0" label="Switch" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="False" />
                        </CommandClass>
                        <CommandClass id="39" name="COMMAND_CLASS_SWITCH_ALL" version="1" request_flags="4">
                                <Instance index="1" />
                                <Value type="list" genre="system" instance="1" index="0" label="Switch All" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="3" size="1">
                                        <Item label="Disabled" value="0" />
                                        <Item label="Off Enabled" value="1" />
                                        <Item label="On Enabled" value="2" />
                                        <Item label="On and Off Enabled" value="255" />
                                </Value>
                        </CommandClass>
                        <CommandClass id="43" name="COMMAND_CLASS_SCENE_ACTIVATION" version="1" request_flags="4">
                                <Instance index="1" />
                        </CommandClass>
                        <CommandClass id="86" name="COMMAND_CLASS_CRC_16_ENCAP" version="1" request_flags="4">
                                <Instance index="1" />
                        </CommandClass>
                        <CommandClass id="112" name="COMMAND_CLASS_CONFIGURATION" version="1" request_flags="4">
                                <Instance index="1" />
                        </CommandClass>
                        <CommandClass id="114" name="COMMAND_CLASS_MANUFACTURER_SPECIFIC" version="1" request_flags="4">
                                <Instance index="1" />
                        </CommandClass>
                        <CommandClass id="130" name="COMMAND_CLASS_HAIL" version="1" request_flags="4" after_mark="true">
                                <Instance index="1" />
                        </CommandClass>
                        <CommandClass id="133" name="COMMAND_CLASS_ASSOCIATION" version="1" request_flags="4">
                                <Instance index="1" />
                                <Associations num_groups="2">
                                        <Group index="1" max_associations="5" label="Group 1" auto="true">
                                                <Node id="1" />
                                        </Group>
                                        <Group index="2" max_associations="5" label="Group 2" auto="false" />
                                </Associations>
                        </CommandClass>
                        <CommandClass id="134" name="COMMAND_CLASS_VERSION" version="1" request_flags="4">
                                <Instance index="1" />
                                <Value type="string" genre="system" instance="1" index="0" label="Library Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="3" />
                                <Value type="string" genre="system" instance="1" index="1" label="Protocol Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="3.40" />
                                <Value type="string" genre="system" instance="1" index="2" label="Application Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="3.00" />
                        </CommandClass>
                </CommandClasses>
        </Node>
</Driver>

[Sergio]

OpenZwave debug after server restart:

Code: Select all

# cat OZW_Log.txt | grep -v Info, | grep -v Detail,
2015-03-27 17:56:40.460 Always, OpenZwave Version 1.3.116 Starting Up
2015-03-27 17:56:40.872 Warning, CheckCompletedNodeQueries m_allNodesQueried=0 m_awakeNodesQueried=0
2015-03-27 17:56:40.872 Warning, CheckCompletedNodeQueries all=0, deadFound=0 sleepingOnly=0
2015-03-27 17:56:41.093 Warning, CheckCompletedNodeQueries m_allNodesQueried=0 m_awakeNodesQueried=0
2015-03-27 17:56:41.093 Warning, CheckCompletedNodeQueries all=1, deadFound=0 sleepingOnly=1

[Sergio]

Turning on-off from domoticz then turning on-off-on-off from wall switch:

Code: Select all

2015-03-27 20:07:01.529 Info, Node006, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True
2015-03-27 20:07:01.529 Info, Node006, SwitchBinary::Set - Setting node 6 to On
2015-03-27 20:07:01.529 Detail, Node006, Queuing (Send) SwitchBinaryCmd_Set (Node=6): 0x01, 0x0a, 0x00, 0x13, 0x06, 0x03, 0x25, 0x01, 0xff, 0x25, 0x08, 0x15
2015-03-27 20:07:01.529 Detail, Node006, Queuing (Send) SwitchBinaryCmd_Get (Node=6): 0x01, 0x09, 0x00, 0x13, 0x06, 0x02, 0x25, 0x02, 0x25, 0x09, 0xea
2015-03-27 20:07:01.530 Detail,
2015-03-27 20:07:01.530 Info, Node006, Sending (Send) message (Callback ID=0x08, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=6): 0x01, 0x0a, 0x00, 0x13, 0x06, 0x03, 0x25, 0x01, 0xff, 0x25, 0x08, 0x15
2015-03-27 20:07:01.538 Detail, Node006,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2015-03-27 20:07:01.538 Detail, Node006,   ZW_SEND_DATA delivered to Z-Wave stack
2015-03-27 20:07:01.550 Detail, Node006,   Received: 0x01, 0x05, 0x00, 0x13, 0x08, 0x00, 0xe1
2015-03-27 20:07:01.551 Detail, Node006,   ZW_SEND_DATA Request with callback ID 0x08 received (expected 0x08)
2015-03-27 20:07:01.551 Info, Node006, Request RTT 20 Average Request RTT 18
2015-03-27 20:07:01.551 Detail, Node006,   Expected reply was received
2015-03-27 20:07:01.551 Detail, Node006,   Message transaction complete
2015-03-27 20:07:01.551 Detail,
2015-03-27 20:07:01.551 Detail, Node006, Removing current message
2015-03-27 20:07:01.551 Detail,
2015-03-27 20:07:01.551 Info, Node006, Sending (Send) message (Callback ID=0x09, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=6): 0x01, 0x09, 0x00, 0x13, 0x06, 0x02, 0x25, 0x02, 0x25, 0x09, 0xea
2015-03-27 20:07:01.556 Detail, Node006,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2015-03-27 20:07:01.556 Detail, Node006,   ZW_SEND_DATA delivered to Z-Wave stack
2015-03-27 20:07:01.751 Detail, Node006,   Received: 0x01, 0x05, 0x00, 0x13, 0x09, 0x01, 0xe1
2015-03-27 20:07:01.751 Detail, Node006,   ZW_SEND_DATA Request with callback ID 0x09 received (expected 0x09)
2015-03-27 20:07:01.751 Info, Node006, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2015-03-27 20:07:01.751 Warning, Node006, WARNING: Device is not a sleeping node.
2015-03-27 20:07:41.551 Detail,
2015-03-27 20:07:41.551 Info, Node006, Sending (Send) message (Attempt 2, Callback ID=0x0a, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=6): 0x01, 0x09, 0x00, 0x13, 0x06, 0x02, 0x25, 0x02, 0x25, 0x0a, 0xe9
2015-03-27 20:07:41.553 Info, mgr,     Manager::WriteConfig completed for driver with home ID of 0x0184df2b
2015-03-27 20:07:41.558 Detail, Node006,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2015-03-27 20:07:41.558 Detail, Node006,   ZW_SEND_DATA delivered to Z-Wave stack
2015-03-27 20:07:41.703 Detail, Node006,   Received: 0x01, 0x05, 0x00, 0x13, 0x0a, 0x00, 0xe3
2015-03-27 20:07:41.703 Detail, Node006,   ZW_SEND_DATA Request with callback ID 0x0a received (expected 0x0a)
2015-03-27 20:07:41.703 Info, Node006, Request RTT 151 Average Request RTT 84
2015-03-27 20:07:41.710 Detail, Node006,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x06, 0x03, 0x25, 0x03, 0xff, 0x2e
2015-03-27 20:07:41.710 Detail,
2015-03-27 20:07:41.710 Info, Node006, Response RTT 158 Average Response RTT 91
2015-03-27 20:07:41.710 Info, Node006, Received SwitchBinary report from node 6: level=On
2015-03-27 20:07:41.710 Detail, Node006, Refreshed Value: old value=false, new value=true, type=bool
2015-03-27 20:07:41.710 Detail, Node006, Changes to this value are not verified
2015-03-27 20:07:41.710 Detail, Node006,   Expected reply and command class was received
2015-03-27 20:07:41.710 Detail, Node006,   Message transaction complete
2015-03-27 20:07:41.710 Detail,
2015-03-27 20:07:41.710 Detail, Node006, Removing current message
2015-03-27 20:07:41.736 Detail, Node006,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x06, 0x03, 0x25, 0x03, 0xff, 0x2e
2015-03-27 20:07:41.736 Detail,
2015-03-27 20:07:41.736 Info, Node006, Received SwitchBinary report from node 6: level=On
2015-03-27 20:07:41.736 Detail, Node006, Refreshed Value: old value=true, new value=true, type=bool
2015-03-27 20:07:41.736 Detail, Node006, Changes to this value are not verified
2015-03-27 20:07:41.802 Detail, Node006,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x06, 0x03, 0x25, 0x03, 0xff, 0x2e
2015-03-27 20:07:41.802 Detail,
2015-03-27 20:07:41.802 Info, Node006, Received SwitchBinary report from node 6: level=On
2015-03-27 20:07:41.802 Detail, Node006, Refreshed Value: old value=true, new value=true, type=bool
2015-03-27 20:07:41.802 Detail, Node006, Changes to this value are not verified
2015-03-27 20:07:41.827 Detail, Node006,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x06, 0x03, 0x25, 0x03, 0xff, 0x2e
2015-03-27 20:07:41.827 Detail,
2015-03-27 20:07:41.827 Info, Node006, Received SwitchBinary report from node 6: level=On
2015-03-27 20:07:41.827 Detail, Node006, Refreshed Value: old value=true, new value=true, type=bool
2015-03-27 20:07:41.827 Detail, Node006, Changes to this value are not verified
2015-03-27 20:07:41.894 Detail, Node006,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x06, 0x03, 0x25, 0x03, 0xff, 0x2e
2015-03-27 20:07:41.894 Detail,
2015-03-27 20:07:41.894 Info, Node006, Received SwitchBinary report from node 6: level=On
2015-03-27 20:07:41.894 Detail, Node006, Refreshed Value: old value=true, new value=true, type=bool
2015-03-27 20:07:41.894 Detail, Node006, Changes to this value are not verified
2015-03-27 20:07:41.980 Detail, Node006,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x06, 0x03, 0x25, 0x03, 0xff, 0x2e
2015-03-27 20:07:41.980 Detail,
2015-03-27 20:07:41.980 Info, Node006, Received SwitchBinary report from node 6: level=On
2015-03-27 20:07:41.980 Detail, Node006, Refreshed Value: old value=true, new value=true, type=bool
2015-03-27 20:07:41.980 Detail, Node006, Changes to this value are not verified

Anyone??

[leby]

I also started with only one switch and nearly gave up since it did not work well. When I added three more switches the network started to act as it should... I can't say that yours will as well but get at least a second switch before you give up. I'm using the zwave stick as secondary controller and it works fine...

[Sergio]

Still failing. I've tried HomeGenie and got a very similar issue. Could it be something stored in the Aeon Labs Stick so it survives the several re-installations I've done and now a completely new program?

[tlpeter]

What i see is an inclusion that is started when you use the switch.
What kind of switch do you use?
What does the manual say about inclusing of the zwave node?
Is the parameter for the switch correct on the node?

The moment you hit the switch there is an inclusion started thus nothing happens (what you except to happen)

[Sergio]

WOW! I didn't notice this reply until now. The forum didn't send me an alert.

The micro switch is:
Aotec Micro Switch G2
model: DSC26103-ZWEU

This is not an energy metering switch.

It worked flawlessly when I first installed Domoticz, but at some point I did a fresh install and started to fail. Could be something changed in MF. configurations?

The manual states that it can be paired from a small button it has, and through switching the wall switch when wired in a certain way.
I never managed to pair it using the wall switch so I always used the small button.

What is this "parameter" in the node?

Domoticz updated to the latest version, but the problem still occurs.

The behaviour is the following:
After a full system restart.
Trough Domoticz I can switch on and off the light.
The schedule (it's the porch light) works as expected.
Then one of this:
1- If you switch using the wall switch, seems only switching off, domoticz looses the light state.
after that, if I try to set it trough DZ, the node is marked dead after two or three attempts.
2- Somehow, when switching trough DZ, the node becomes unresponsive (when switching off) and is marked dead.

Full system restart, makes the switch alive again.

[krisha]

The behaviour is the following:
After a full system restart.
Trough Domoticz I can switch on and off the light.
The schedule (it's the porch light) works as expected.
Then one of this:
1- If you switch using the wall switch, seems only switching off, domoticz looses the light state.
after that, if I try to set it trough DZ, the node is marked dead after two or three attempts.
2- Somehow, when switching trough DZ, the node becomes unresponsive (when switching off) and is marked dead.

Full system restart, makes the switch alive again.

Sorry for reviving this thread, but I have the same problem with an AEON micro switch (2nd edition/DSC26103).

Did you solve the problem?

I figured out that everything works fine when the micro switch is near the controller. But as soon as it is more far and it misses a switch command it gets problematic and soon it is dead. I think if that happens the controller (AEON Z-Stick Gen5) does not send out any new commands.

My domoticz is nearly up2date. The topology shows it has a connection to another switch just 5m away (ok, through 2 walls...).

off topic/warning: this device has a capacitor at the 230V side - do not touch the input pins after removal. Also this device does not easily fit into a regular flush mounted box.

[Sergio]

The behaviour is the following:
After a full system restart.
Trough Domoticz I can switch on and off the light.
The schedule (it's the porch light) works as expected.
Then one of this:
1- If you switch using the wall switch, seems only switching off, domoticz looses the light state.
after that, if I try to set it trough DZ, the node is marked dead after two or three attempts.
2- Somehow, when switching trough DZ, the node becomes unresponsive (when switching off) and is marked dead.

Full system restart, makes the switch alive again.

Sorry for reviving this thread, but I have the same problem with an AEON micro switch (2nd edition/DSC26103).

Did you solve the problem?

I figured out that everything works fine when the micro switch is near the controller. But as soon as it is more far and it misses a switch command it gets problematic and soon it is dead. I think if that happens the controller (AEON Z-Stick Gen5) does not send out any new commands.

My domoticz is nearly up2date. The topology shows it has a connection to another switch just 5m away (ok, through 2 walls...).

off topic/warning: this device has a capacitor at the 230V side - do not touch the input pins after removal. Also this device does not easily fit into a regular flush mounted box.

Nope. I completely ditched the zwave system. Now I use mysensors (completely different band). As my rfxtrx also was failing, I replaced it with a rflink. But still works erratically.

I think those systems are made and tested in a perfect environment, a very small flat or a gorgeous house by the sea. So there are few interferences and/or the emitter it's nearby.

Enviado desde mi MI 5s Plus mediante Tapatalk