X10 Community Forum
📱X10 WIFI => 🐞X10 WIFI App problems or bugs => Topic started by: ceedee on September 18, 2018, 08:56:34 AM
-
Not a crisis, but documenting for the record.
I still use a PR511 to turn on my exterior lights at dusk (yes, real dusk!). I have the sensor set to turn on units 1, 2, and 4. All three turn on correctly, but the WM100 only records unit 1 in the log, and most importantly, only updates the on/off status in the app. No sign of units 2 and 4. A swipe refresh does not work. The WM100 apparently never saw the last two commands.
So, it appears that the "simultaneous" nature of three unit "on" commands is an issue for the WM100.
-
I'm guessing the PR511 is, for example, sending "A1, A2, A4, ON" and the WM100 is ignoring anything else between the first address and the ON command. If all three lights come on together that's what's being sent (as opposed to each one coming on in sequence). If you have a Maxi-Controller (SC-503) which has discrete address and command buttons you can further test that theory and then you can use any controller to see if sending "A1 ON, A2 ON and A4 ON" registers correctly. If it does then the developer needs to study up a bit!
-
No 503, but it records properly when I press 1 on, etc. on my controller.
I used to have all outside lights use the same unit code, but I wanted flexibility, now that I have the WM, so I split them up. Oh well.
-
If you're using AHP or some other programmable controller you could use the A1 ON from the PR511 to trigger (re)sending A2 ON and A4 ON for the purpose of keeping the WM100 in sync with the actual status. The lights will already be on anyway.
-
I'm guessing the PR511 is, for example, sending "A1, A2, A4, ON"
I used to have several PR511 and as I recall, you are correct. If ceedee can see more than one light at the same time, and if they go on at the same instant, it would confirm that A2, A3, A4 ON is what is being sent.
-
My CM15 sends ON commands and DIM commands starting at unit 1 and going to unit 8 all in quick succession, since they are all on the same setback from dusk....sometimes the WM100 gets two or three of the units commands, often different ones each day. I have several units set for OFF all at the same time and they all (four unit addresses) go off simultaneously and the WM100 only gets the lowest unit code.
Never has the WM100 been correct for 8 of my 11 lighting modules/switches unless I manually switch the device.
-
One more nail in the WM100's coffin.
-
And I quote:
.The WM100 has an active ‘sense’ technology that will adjust the status of the devices in the app regardless of if the signal was sent from the WM100 or any other source (like a hand remote)"
Well, no.
-
I had hoped maybe this was addressed with the latest update as the developer didn't go into much detail when they stated minor issues where fixed.
I fired off a email to Authinx on this as well as adding the option for a backup /restore function stressing the need for that.
-
If I were the other WM100 users it would be more than emails I'd be firing off to Authinx. Maybe they could have the curtesy to address the owners directly via this forum, answer their questions and reaasure them. Maybe they have and I've missed their post. If they can't get the basics right I don't see a "Pro" model ever materialising. The underlying advantage of the WM100 appears to be its increased power to transmit X10 signals and little else.
-
This doesn't concern the WM100, only the PR511. Except for false triggering during lightning flashes and a shattered lens from blowing debris during a wicked storm, ours have been working fine for years. Some time during the night one of them switched on, and did not respond to an ALL_OFF on any housecode. Troubleshooting showed the relay stuck in the on position. The contacts are not welded shut, and the coil is fine, so there must be some other failure. I hope its replacement lasts another 15 years.
Jeff