X10 Community Forum
🔌General Home Automation => Automating Your House => Topic started by: Moose on July 09, 2021, 10:13:14 AM
-
I have an Automation rule that simply runs when a Motion sensor is tripped between Sunset and Sunrise, turn on a Porch light. I have noticed that the Rule has been activated several times before sunset, from 10 to 30 minutes before sunset. My location in the app is correct. Any thoughts?
-
Is there not anyone running a rule where a light turns on at sunset?? Brobin maybe? ??? I checked it again last night and it was enabled a full half hour before sunset. I did not have this issue when I ran only Homegenie. Sunset was spot on.
-
I do have some sunrise/sunset rules and have never had an issue with any offset of those exact times. Check the setting for the rule to ensure that there are no offsets programmed. It should look like this:
-
Thanks for the suggestion. But, when I checked the Rule via Edit, I do not even see the option to add an offset.
-
I see that option only appears when setting up Sunset and Sunrise individually as opposed to using the Time Window function which I assume is what you're doing to bracket the time. I don't have any idea why you'd be seeing incorrect times unless your location is somehow ambiguous. Have a look at your web portal at https://console.smartenit.io to see how it's set and edit if needed. Postal codes seem to be important. I'm not using any Time Window rules so I haven't experienced any issues but I'd think that if the regular SS/SR times are dead on it would carry through.
Be sure you check "Click here to expand window across dates" at the bottom of the rule so that sunset today window carries through to sunrise tomorrow.
-
I don't have any idea why you'd be seeing incorrect times unless your location is somehow ambiguous.
Postal codes seem to be important.
I'm not using any Time Window rules so I haven't experienced any issues but I'd think that if the regular SS/SR times are dead on it would carry through.
Be sure you check "Click here to expand window across dates" at the bottom of the rule so that sunset today window carries through to sunrise tomorrow.
I rechecked my address. It had me a couple of miles away but I inputted my actual address. Postal code was correct though.
If you are not using a Time Window, how do you end your rule in the jpg above?
I had not clicked the "...expand window..." square at the bottom. It is now so I will check tonight. Thanks.
-
The rule in my jpg above is just a one shot at sunset that I use to confirm all is well. At Sunset an email is sent that says "Green Flash Time" so there's no 'Time Window' needed in the rule. I'll be curious as to your results tonight. It might be useful to set up a simple Sunset rule like mine just to get a daily time verification that you can monitor. If that one is rock solid and the Time Window rule varies that would be an interesting question for Smartenit! I know you're in Canada but I think clocks work the same up there, right? rofl
-
Yes, our clocks work like yours. ;D I tried a simple Sunset test and it worked fine. Official sunset at 9:04pm, the Rule activated at 9:05. But my original Rule is still misbehaving. I went out at 8:40 and my motion light turned on. Brobin, could you create a little Sunset-Sunrise Rule test to compare. Mine is just logic ANDed with a motion sensor to turn on a light. Very simple, I thought. B:(
-
Sure, I can do that. I'll set it up and let you know how it goes. Can you post a screen shot of your rule so I do it exactly the same?
-
I set up a Time Window rule so that If I tell Alexa to turn on the Christmas Tree before Sunset tomorrow I should NOT get an email. In doing so I want to make sure that you have the circled ALL showing rather than ANY as that would negate the Time Window restriction.
-
When I ticked the "...expand window across dates" it added the Nth notation. I noted in your Rule, it says Sunset July 12 till Sunrise July 12th. ???
-
Looks like it's OK but I'd expect a couple of dates in there. You can edit to add them in the app. I just updated mine with today and tomorrow's dates but it should carry through daily anyway.
I turned on the Xmas Tree this morning and did NOT get an email which means the TimeWindow worked to exclude it. I'll try it again this evening during the 30 minutes leading up to Sunset to see if there any changes.
-
I meant to ask you, the motion sensor X10 transmit code is different from the porch light X10 code, correct?
-
Yes, the MS16A is at default A1 and the porch light is A2.
-
Keep in mind that if not disabled, the MS16A also uses a second code to send an ON for dusk and an OFF for dawn on A2 - same as your light! A1 is motion only. So if the A2 transmits an ON at dusk (about 20 min before sunset?) it would turn on the porch light. Maybe try giving the light a new code or be sure to disable the dusk/dawn feature in the MS16A.
http://www.authinx.com/x10/manuals/MS16A.pdf
-
Keep in mind that if not disabled, the MS16A also uses a second code to send an ON for dusk and an OFF for dawn on A2 - same as your light! A1 is motion only. So if the A2 transmits an ON at dusk (about 20 min before sunset?) it would turn on the porch light. Maybe try giving the light a new code or be sure to disable the dusk/dawn feature in the MS16A.
Okay, hmmm. I had forgotten that. :' But, if that happened, I would not get a Porch light ON message in the Smartenit Event Log, would I? I clearly get an Event saying "Porch Rule has been triggered" at 8:40PM followed by the rest of the event chain.
-
That sounds right and since the unit isn't looking for A2 as a trigger it should be ignored even during the TimeWindow. Just another piece to consider but I'd probably change the porch light code anyway just to eliminate the possibility.
-
I've completed my testing of the Time Window trigger today and see the same behavior as yours. So at least we can stop fiddling with settings till we find an answer!
Sunset here (Naples, FL) was at 8:23pm today and I got my "Green Flash" message at precisely that time. I had also turned on the Xmas Tree at 7:23pm and again at 8:03pm and the Time Window was triggered and sent an email both times! So the window is opening at least one hour in advance of what's expected. The last test prior to those was at 6:19pm which did NOT trigger the rule.
I'm going to send an email to Smartenit support to see what they have to say. You might want to do the same so they know this is not a single user issue. Let's keep each other posted on their responses.
-
For anyone following along, Smartenit will fix the Time Window error in a future FW release. :'
-
I rechecked mine tonight and it activated a full hour ahead of Sunset too.
-
I have another weird symptom that has turned into a puzzle. The Automation Rule is still as above. But, every evening at 7:20PM, the Porch light turns on. The event appears in the Smartenit log. I also have the Homegenie app running in the background on a PI, just for fun. It shows all of the activity initiated by the Harmony hub except the 7:20 Porch light coming on. Any thoughts?
-
What time is sunset where you are now? IIRC, you only have a time window set and not something that would trigger at a specific time like 7:20PM correct? Is there any other device you have set to turn on at 7:20PM?
As for not seeing only the 7:20PM X10 transmission in HG, is the P2 sending it as an ON command or a DIM command? I ask because the Insteon implementation of dimming (from the P2's PLM) uses X10 extended commands which might not be seen by the CM15A connected to to your PiHG. Someone else here who's more familiar with the CM15 might be able to chime in on that possibility.
-
Sunset here is 6:14. There is no other event scheduled for 7:20. The event is "7:20 pm Porch light turned on".
The one possibility is one Brobin and I discussed before. I am using an MS16a set to A1 to trigger the Porch light after sunset. The Porch light is set to A2. So, there is a chance the MS16a is sending a Dusk On code. But, that should show up on the HG via the CM15, correct?
-
I would think so. If it's possible without too much difficulty, I'd pull the batteries for the motion detector or unplug the receiver(s) if that's easier, and see what happens tonight. That will at least confirm or eliminate the MS16A from consideration.
-
Not so easy to pull batteries today. I have 2 sensors set to A1. It snowed 2" over night and I need a ladder.
And to clarify, when the A2 Porch light is on, it shows as ON in the Smartenit Dashboard (and in the Log), but not on HG Dashboard.
If the A2 ON were getting sent at Dusk would you not expect an A2 OFF to be sent at Dawn?? There are no A2 OFFs in the Harmony log near Sunrise.
-
Yes, I would expect to see an off too but let's test the easiest stuff first. Rather than pulling the batteries for testing how about just unplugging the TM751/RR501 receiver?
What is this "snow" thing you speak of? Here in Florida we're feeling winter's cold chill upon us... the temperature plummeted to 76F this morning! 8) rofl
-
Well, I unplugged the RR501 and 7:20 arrived and the porch light turned on. It got logged in Smartenit but nothing on HG.
It is a little early for snow here, but not unheard of. You must have heard of snow. The Snowbirds that escape from Canada must talk about it. :'
-
Oh, you mean those people who turn bright red after 2 days here in the winter? (not sure if it's from the sun or the docktails - maybe both!) :o ;D
OK, so now we know for sure the motion detector isn't the cause. To be a specific time every day it seems that there'd have to be an entry in one of your P2's Automation Rules causing that or an activation from some other controller. To be sure that it's coming from the P2 you could unplug the PLM before 7:20PM and see if the light stays off. If it turns on then the signal is coming from somewhere else. If you'd like me to look at your Automation Rules on the web portal (console.smartenit.io) I'm happy to do that. You can PM me your P2's login info and then change the PW after I've had a look.
-
To be a specific time every day it seems that there'd have to be an entry in one of your P2's Automation Rules causing that or an activation from some other controller.
To be sure that it's coming from the P2 you could unplug the PLM before 7:20PM and see if the light stays off. If it turns on then the signal is coming from somewhere else.
I will unplug the PLM tonight and see. I only have 3 Rules. Voice commands for turning on the morning lights and killing everything at bedtime. The Rule that is most suspect is the one on page 1 of this post. If you recall, it was already a little wanky because it would allow motion triggers 1 hour before Sunset.
-
I do remember that and if the light comes on tonight with the PLM unplugged then the next step would be to delete that rule.
I'll stay tuned for this evening's breaking news!
-
I do remember that and if the light comes on tonight with the PLM unplugged then the next step would be to delete that rule.
I'll stay tuned for this evening's breaking news!
Well, if the light came on with the PLM unplugged, the problem is not with the Smartenit or an Automation Rule but elsewhere, correct?? Anyway, I have to start over, remove a few more variables and try again. I have 2- A2 porch lights, and one of them came on. Go figure. #:) I will let you know. :'
-
Absolutely. If the porch light came on at 7:20 and the PLM was unplugged, then it couldn't have come from the P2 since the PLM is what transmits the signal (the same way that your PiHG uses a CM15A to transmit X10 signals).
You have another transmitter somewhere sending that signal and the P2 was just reporting that it saw it on the powerline. If the HG is online with a CM15A plugged in, it could come from the HG or be something previously set in in the CM15A. Unplug the CM15A for tonight's test and think about any other controllers that might be plugged in.
One rather remote possibility, particularly in 2021, is that a neighbor on the same electrical transformer is using X10 as well and sending the mystery signal.
-
They said that only 1 of 2 devices on code A2 turned on. Seems strange that only 1 turned on. Clearly not the P2 device though.
-
I noticed that. It'd be a real coincidence if that bulb just happened to burn out yesterday! It'll be interesting to see what happens tonight with the RR501, PLM and CM15A all unplugged. Holloween is over so if A2 turns on it won't be Casper the Ghost!
-
If the HG is online with a CM15A plugged in, it could come from the HG or be something previously set in in the CM15A.
One rather remote possibility, particularly in 2021, is that a neighbor on the same electrical transformer is using X10 as well and sending the mystery signal.
I have killed HG completely for now. My nearest neighbour is about 1/2 mile away, so not likely. :)
-
They said that only 1 of 2 devices on code A2 turned on. Seems strange that only 1 turned on.
Perhaps not that unusual here. I quite often will hit A4 On and have 1 of 6 A8 lights come on. I likely still have some noise issues.
-
I have killed HG completely for now. My nearest neighbour is about 1/2 mile away, so not likely. :)
Keep the CM15A unplugged too if that wasn't included in killing HG completely.
Looking forward to tonight's update!
-
I have unplugged the CM15A. Today, my whole X10 system went crazy. My security alarm console was intermittently alarming, lights going on and off.
A lot of the light activity was not showing up on the Smartenit app either. And at times the Harmony would lose connectivity.
Anyway, if you remember a while back, before I built all those inline 20 amp filters, my problems were found to be caused by some LED lighting. I put a filter on the circuit and all was well. I have just disconnected the 2 -15' lengths of rope lighting that I think is the source. Things have been quiet for the last hour. :)%
-
How many X10 Controllers do you have on your setup. So far I’m counting three.
-
Well maybe it IS Casper the Ghost after all! :o You unplug much more and you'll be living by candlelight!
When I replaced an incandescent pool light with an LED it shut down most of X10 for the house when it turned on. Jeff Volp's article suggested a hash choke between the X10 wired in module and the LED bulb which solved the problem. My local electronics surplus outlet had a box of unmarked chokes that were pretty beefy looking (an engineering term for sure) so I tried one and it worked. Next time I was there I grabbed a handful and I'm happy to send you one if you need it. The one that Jeff recommends is on ebay as well. https://www.ebay.com/itm/322651422833
When you say the Harmony would lose connectivity do you mean from the internet or the PLM not being able to receive/transmit?
Glad things settled down and looking forward to this evening's report.
-
Yes I have 3, only 2 connected right now. The Smartenit Harmony and the X10 Security console. Actually I have another but it is usually on idle. IE it is on House code B where as, all my devices are on House code A.
Well, the Porch light did not turn on at 7:20, or any other time. But, half of my Living room lights, A8, went off about 6-8 times per hour and did not show up on the Smartenit log. Harmony losing connectivity was my conclusion when I would try and control a device with the app and the device would go red.
We can talk more about the choke tomorrow. Thanks.
-
So from where we are on the phantom A2 at 7:20 command it appears that unplugging the CM15A solved it. That means that HG or something programmed directly into the CM15A (through AHP) is causing it. If you want to keep those items in the mix you could look at clearing the CM15A's memory (see: https://forums.x10.com/index.php?topic=28827.0) as well as looking for the mystery timer in HG.
Now let's look at the Harmony connection issue. If you go to the Dashboard and look at the P2 Gateway icon you should see a green dot in the upper left corner of the box. If it's red it means that the app can't see the P2 which means that the P2 isn't connected to the internet/Smartenit server. Check your Ethernet cable and switch (if one is being used).
If you're just seeing a red circle around the on/off button of a device when you tap it then check the USB cable to the PLM and the power outlet it's plugged into. That red circle means the command can't be sent.
As for the A8 problem it sounds like something is dumping a lot of garbage on your powerline and you need to see what else it could be other than the LED lights you unplugged. Maybe another LED bulb that's in the process of failing? It could be a bulb's internal power supply has overheated and is trashing the line. See what you can find on that front.
One step forward, two steps back!
-
I have never used AHP or put batteries in my CM15a's. Do you believe it likely that something got stored in memory??
This morning was interesting. The main kitchen light consists of 3 LED bulbs and 3 incandescent bulbs. I originally did this with compact fluorescent bulbs to make the load resistive enough to control with X10. I think one or more of these LED bulbs must be failing. For about an hour, the Kitchen light, A3, switched off about 6 times. Then it settled down.
The Harmony going red has stopped since disconnecting the LED rope lights.
-
If you never used AHP it's unlikely that anything is stored in the memory that wouldn't have showed up before. So, by process of elimination, the HG program would seem to be the culprit for the 7:20pm A2 signal.
As for the other problems you're having, the various LED devices seem to be the culprit. Perhaps they're all getting old now and developing power supply issues. They say the bulbs will last for 30 years but that doesn't account for the time for the power supplies to fail. LED bulbs/devices are a bit of a crapshoot since the manufacturers - particularly of the cheap Chinese generic ones - are built as cheaply as possible without much regard for component quality. BTW, if the LED bulbs don't say 'dimmable' never use them with a lamp module or dimmer switch as the power supplies will prematurely fail. You could add hash chokes to all the LED circuits to help or find some name brand ones that might be be built better. You'd wire them in series with the hot side output for the switch or module and use some heat shrink or tape on the leads.
-
I will recheck the A8 behavior tonight because I think it continued to turn off after all LED bulbs were all off.
Another strange one today. I have an appliance module A7 plugged in that I call Test 1. I use it for command confirmation because I can hear the click of the relay. It has been going on and off this morning. It has never been on a Timer or part of a script or automation rule. It shows up in the Harmony log too.
In terms of the choke, do you think that the X10 XPF filter offers the same filtering, or does the choke address something else? I do have the XPF feeding all but the kitchen table bulbs. I think I will use all incandescents there till this is resolved.
-
Casper is definitely in the house!
The thing is line noise usually just blocks signals and very, very rarely, if ever, causes things to actually turn on and off. Unplug the security console and any other controllers and just watch and wait. There has to be a controller/transmitter of some kind causing all this.
-
If you have boxed up any x10 RF remotes unpack them to besure you didn't leave batteries in them. I had did this and after bumping the boxesd up items a remote started to send on off codes. Took me forever to find the source of my Phantom signals.
-
So from where we are on the phantom A2 at 7:20 command it appears that unplugging the CM15A solved it. That means that HG or something programmed directly into the CM15A (through AHP) is causing it. If you want to keep those items in the mix you could look at clearing the CM15A's memory (see: https://forums.x10.com/index.php?topic=28827.0) as well as looking for the mystery timer in HG.
Now let's look at the Harmony connection issue. If you go to the Dashboard and look at the P2 Gateway icon you should see a green dot in the upper left corner of the box. If it's red it means that the app can't see the P2 which means that the P2 isn't connected to the internet/Smartenit server. Check your Ethernet cable and switch (if one is being used).
If you're just seeing a red circle around the on/off button of a device when you tap it then check the USB cable to the PLM and the power outlet it's plugged into. That red circle means the command can't be sent.
As for the A8 problem it sounds like something is dumping a lot of garbage on your powerline and you need to see what else it could be other than the LED lights you unplugged. Maybe another LED bulb that's in the process of failing? It could be a bulb's internal power supply has overheated and is trashing the line. See what you can find on that front.
One step forward, two steps back!
Have you checked your X10 security console to see if there are any automation rules defined there. The more X10 controllers you have on the same network the more likely you are to experience conflicts. You’ve a combination of PL/RF commands firing off from different X10 controllers that could well be cancelling each other out owing to conflicting rule sets.
It might be a case of deciding what X10 Controller is most important to your overall setup. Obviously you’ll want your X10 security console which works very well with the CM15 and HG. I’ve not used the Smartenit controller (wouldn’t have any need for it anyway) but it does appear you have a certain amount of unnecessary redundancy in your setup.
Maybe you should do a needs assessment on your setup and post back here for further guidance. As it stands from what you describe you’ve definitely got some form of conflict in the mix. HG and a properly setup CM15 will more than fulfil your X10 requirements plus your X10 security console can be directly controlled by HG.
-
The Security Console is also an X10 Transceiver on the X10 House Code it is set to. Besides processing any Security RF devices you have.
-
The Security console is off for now. And, for the most part, my "system" works. My problem seems to be mostly one of RF anomalies. The mail culprit is the MS16a sensor set to A1. The one on the back porch works well. The one one the front porch is very flakey. The are both about 12 feet from the PAT01 transceiver. The front one often does not trigger, even though I can see the lights flash on it. Again, often, when it triggers, my Test1 on A7 trips instead.
Last night at 9:01 I went to the back door and triggered my Automation Rule and the Porch lights turned on for the 2 minutes defined in the rule. But, the Porch Light device ikon on the harmony app did not turn green for the 2 minutes. But it was all in the app log.
I am sure the problems revolve around too much RF noise and devices too close together. But I have a limited number of spots to use. I have Jeff Volp's X-repeater and filters. Without an RF sniffer tool, I am not sure how to track this down.
-
Just to add, it is windy out and one of the motion sensors is switching ON and activating a Universal module to ring a doorbell. The Sensor ON is showing up in the Harmony log, but when I quickly check the app, the Device does not show as ON.
-
Based on what you saw I ran a little test. I watched a device's icon status on the P2's dashboard as I turned it on and off from another controller. The icon status doesn't change in the app when the signal is received from a different controller but the commands were received by the P2 and displayed on the Events screen. The only time the icon status appears to change is when the icon in the app is tapped to turn it on or off or in response to an Automation Rule execution or Alexa command. So it would appear that the icon status is only designed to change when the command is sent by the P2.
While it would be nice to see the icons respond to received commands, the important thing is that the P2 does indeed see them and can execute Automation Rules based on receiving them.
I never actually use the app to control anything unless testing so I never noticed that it displays that way. While it doesn't matter for the way I use it, I can see where it would be a logical visual aid to have the icon status track received as well as sent commands. I know that Smartenit is very receptive to feedback on how to improve the P2 and the app and they've done several f/w updates with things I've suggested. The best way to get that ball rolling is to contact them through the website with a request to make the change and see what they say. Let me know if you do that and I'll send one seconding the motion.
-
In terms of the choke, do you think that the X10 XPF filter offers the same filtering, or does the choke address something else? I do have the XPF feeding all but the kitchen table bulbs.
Brobin, back to the choke. I was wondering how you installed these and how many? I can see if you have a light fixture with it's own octagon box, soldering it inside. Did you just cut into a line cord, solder it in and tape it up?? Or something more creative?
-
I installed one choke on an inground pool light that I'd replaced with a multi LED bulb. In the pool's electrical panel I had installed an XPFM fixture module to control the light and I added the choke between the blue 'load' wire and the hot going to the fixture as drawn in purple below. You can use heat shrink or tape to insulate it and the connections can be soldered, crimped or wire nutted. In my case I had plenty of room but the principle is the same. You could even put the choke inside the base of the lamp in the picture below - just cut the hot going from the module to the fixture wherever convenient.
-
Just to add, it is windy out and one of the motion sensors is switching ON and activating a Universal module to ring a doorbell. The Sensor ON is showing up in the Harmony log, but when I quickly check the app, the Device does not show as ON.
I knew I recognised the user name. I helped you back in Feb 2020 with what appeared to be a faulty CM19 and HG via PM. You’ve now been through a CM15 and are currently trying to set up a Smartenit Controller with your setup. Have you managed to actually get an X10 Controller working successfully with your setup. You said you intended to revisit this project in March 2020 but I heard nothing back.
-
I did have to give up on the CM19. I was able to prove it worked with AHP and a Windows PC to provide sufficient current. I tried 3 different PS with the RPI and could not get it to work.
I did get HG working and gave an update at the end of this thread. https://forums.x10.com/index.php?topic=31229.90
My transition to Smartenit took place here. https://forums.x10.com/index.php?topic=31439.0
-
I did have to give up on the CM19. I was able to prove it worked with AHP and a Windows PC to provide sufficient current. I tried 3 different PS with the RPI and could not get it to work.
I did get HG working and gave an update at the end of this thread. https://forums.x10.com/index.php?topic=31229.90
My transition to Smartenit took place here. https://forums.x10.com/index.php?topic=31439.0
Great but I asked you a question earlier in this post about your X10 security panel and possible conflict with automation rules on it and other X10 controllers on your setup. I didn’t notice any response. What X10 security console do you have. Have you checked it for automation rules for possible conflicts.
-
It is an older PS561. All I have is 2 Security Motion Sensors, alarm modules and wireless key fobs. Nothing fancy. And as I mentioned an old timer module that is on "idle" on a different House Code.
-
It is an older PS561. All I have is 2 Security Motion Sensors, alarm modules and wireless key fobs. Nothing fancy. And as I mentioned an old timer module that is on "idle" on a different House Code.
For troubleshooting purposes I suggest that you remove the X10 security console from your setup for the moment along with any additional X10 controllers and concentrate on getting one X10 Controller working reliably with your setup, either the Smartenit or the CM15 and start adding back till you discover the source of your problem. It really does sound like you have some form of signal conflict in your setup. Your X10 security console is quite old and possibly your security sensors so I’d try tackling the issue from that angle. Are your X10 security sensors registering and correctly reporting your house code/unit code in HG.
-
I did mention back in Reply 49 that the Security console is off for now. I have never used the security motion sensors with HG. They do work fine though when the Security console is setup and armed.
-
I just did a little experiment with a spare MS16a set to A1. My Smartenit is set up in the Kitchen. When I walk around and manually send ON commands anywhere in the Kitchen area, the Porch Sensor device is not activated. Once I leave the room, everything works fine. It is like there is an RF field blocking the On code.
-
I did mention back in Reply 49 that the Security console is off for now. I have never used the security motion sensors with HG. They do work fine though when the Security console is setup and armed.
You may have the console deactivated but are the security sensors deactivated too. Remember every time they are triggered on they will trigger off quickly. You need to consider all RF sensors on the premises and how they are actually configured. As I suggested strip your setup down to the basics and slowly add back each element testing it fully before moving on. Remember your X10 rf Controller will still be picking up rf signals even if they are not configured on the system. I’ll leave it with you but you have the basic idea.
-
I just did a little experiment with a spare MS16a set to A1. My Smartenit is set up in the Kitchen. When I walk around and manually send ON commands anywhere in the Kitchen area, the Porch Sensor device is not activated. Once I leave the room, everything works fine. It is like there is an RF field blocking the On code.
Where is the transceiver located? The MS16A signal is received by the Transceiver which sends an X10 command out on the powerline. The PLM on the powerline receives that signal and sends it to the P2.
-
I just did a little experiment with a spare MS16a set to A1. My Smartenit is set up in the Kitchen. When I walk around and manually send ON commands anywhere in the Kitchen area, the Porch Sensor device is not activated. Once I leave the room, everything works fine. It is like there is an RF field blocking the On code.
Where is the transceiver located? The MS16A signal is received by the Transceiver which sends an X10 command out on the powerline. The PLM on the powerline receives that signal and sends it to the P2.
In the Kitchen, inches from the PLM. I have tried moving the transceiver around, but with no luck. I think perhaps one of my power bars had turned into a transmitter.
-
Most power strips have filters which can interfere with X10. Best to plug directly into wall outlet.
-
Well, the ghosts are back! B:( I cannot control my X10 modules with Smartenit, again. The app seems to be working. If I turn on devices from other controllers, the app shows the device as green, ON. If I ask Alexa to turn on a device, the app shows green. If I try and control devices in the app, the device turns green but does not come ON.
So, it would seem that the Smartenit hub is working and connected to the network. And, the transceiver seems to be working because it is feeding device status to the hub. Thoughts?
-
Do the CM15A and other controllers turn the devices themselves on/off? Can you control a module plugged plugged into the same outlet as the P2?
This sounds like some device in your home is spewing noise. You can try turning off one breaker at a time to find which circuit it is then look for things on that circuit to unplug/disconnect. Suspected culprits are wall warts as well as CFL and LED bulbs. When these things get old they can create line noise before they actually fail. Also think about ANY new device that may have come into your home - like a new cell phone charger of new LED bulbs. Over the years I've had ALL of these things happen.
-
This is a little more bizarre than my usual. There are 2 appliance modules just inches away from the PLM and they can be controlled by my Homeseer controller. I even plugged an appliance module into the PLM and it would not respond, but it will via Homeseer. The device events from Homeseer are showing up in the Smartenit log too. I am wondering if the PLM died?
-
So, I needed to try something else, so I plugged the PLM with the attached appliance module into an extension cord that was plugged in elsewhere. And guess what happened. :' Everything worked. :)% Then I plugged it back where it came from, and everything still worked. >! I do not get it. >*<
Thanks for your input Brobin.
-
Maybe just the act of rebooting the PLM by unplugging it cleared the problem. But then, we've already established the fact that you live in a haunted house so who knows? :' rofl >!
-
Everything worked for about 24 hours, then I had To "reboot" the PLM again. ???
-
Everything worked for about 24 hours, then I had To "reboot" the PLM again. ???
Try pressing and holding the SET button on the PLM for 10 seconds to reset it.
-
If you are trying to do a Factory Reset on the 2412U PLM. That clears everything out.
Unplug the 2412U and wait for maybe ten seconds.
Plug it back in while holding the Set Button for ten seconds and then release the Set Button.
-
If you are trying to do a Factory Reset on the 2412U PLM. That clears everything out.
Unplug the 2412U and wait for maybe ten seconds.
Plug it back in while holding the Set Button for ten seconds and then release the Set Button.
Are there 2 levels of Reset or was Brobin's description just not quite as complete?
-
Brian H is correct. Sorry I left that part out. I should have added "while plugging it in."