X10 Community Forum
📱🖥️PiX10Hub => 💬General Discussion => Topic started by: Moose on February 09, 2021, 03:28:02 PM
-
My CM15A is connected to a RPI with Homgenie and HABridge. For the 3rd time in the last few months, my X10 system "dies" and I am not able to turn anything on or off. It does not matter which one of several controllers, including those wired to an AC outlet. Occasionally, one command will go "on" but immediately goes "off". I walked around the house disconnecting and unplugging device after device until I found unplugging the CM15A "fixed" the problem. At least I could turn the lights off to go to bed. :) ;)
Any ideas? At one point, I was looking at the HG logs and I could see a steady stream X10A4 Level 1 commands, hundreds of them. At the time I was trying to do A4-off to kill a radio.
-
Have a look at this http://forums.x10.com/index.php?topic=31391.msg186768#new
-
Once you’ve ruled out your hardware look next at any automations you’ve set up in HG. If the logic in any of your scripts it could be firing off this A4 on command waiting for a condition to be met. I assume you’ve no X10 remote acting up. Try removing batteries from remotes and continue your checks.
-
I have been reading the linked post and the parallels are amazing. In my case, as soon as I pulled the CM15A, everything settled down. I am taking my time now to do some more testing. Thanks.
-
I have been reading the linked post and the parallels are amazing. In my case, as soon as I pulled the CM15A, everything settled down. I am taking my time now to do some more testing. Thanks.
Remember, examine the logic in your scripts in HomeGenie carefully. Imagine you have a command that turns on A4 and another that turns it off. The first script depends on A4 being on before it terminates and so on. Another example is if a sensor is set to turn on A4 and it's faulty. Constantly sending the A4 on command. One final thing. When you are finished troubleshooting HomeGenie disable logging otherwise you will kill your SD card with all those log writes.
-
Thanks, I had forgot about disabling logging and the memory chip life. -:)
I still have the CM15A unplugged(HG running on the RPI), and just the Smartenit P2 running my lights. I have 2 "Routines" configured to turn groups of lights on/off in Alexa. I had everything working nicely yesterday, but after a few hours none of the Alexa commands would work. I could still turn off the X10 lights with the wired keypad. This is not the 1st time Alexa forgot everything.
I "Removed All" Alexa devices this morning and "Rediscovered" and everything is working again.
Any ideas.
-
When that happened did you notice if the green dot was present on the gateway icon in the Smartenit app or was it a red dot? If it happens again try a reboot of the P2 & PLM before resorting to the R&R with Alexa.
-
It quit again. Alexa would say OK but nothing happened. I was able to control devices from the P2 app on the phone. So, I tried powering off the RPI, Homegenie and the HABridge, and the Alexa commands worked again. B:(
-
With the RPI turned OFF, remove devices in the Alexa app, exit the app, then log back in and rediscover devices in the Alexa app. It's important that all the HABridge devices be removed to eliminate double entries. Maybe it'd be a good idea to remove or disable HABridge in the RPI to keep it from happening again. Others here can advice on that.
-
With the RPI turned OFF, remove devices in the Alexa app, exit the app, then log back in and rediscover devices in the Alexa app. It's important that all the HABridge devices be removed to eliminate double entries. Maybe it'd be a good idea to remove or disable HABridge in the RPI to keep it from happening again. Others here can advice on that.
@brobin are you using HA Bridge. I thought the Smartenit hardware did away with the need for 3rd party emulators.
@Moose are you sure you have no port conflicts in your setup. Did you recently update either HomeGenie or HA Bridge. Amazon did a recent firmware upgrade and if you rely on HA Bridge for Alexa functionality this may be your problem.
Can you completely remove HomeGenie/HA Bridge from your setup temporarily and see if Smartenit and Alexa function correctly.This should help to narrow down your problem.
-
No I don't use HA-Bridge or an RPi and yes, the Smartenit hardware does indeed do away with the need for 3rd party emulators.
I have just two controllers; the Stargate and the Smartenit. If all I wanted to do was X10 control I wouldn't even need the Stargate!
My comments are for Moose as he does have the RPi running HA-Bridge and unplugging it solved his problem. I learned this awhile back when I migrated from Alex10 (running on a WIN pc) to the PiAlexaHub. With two instances of the same Alexa device she gets confused so it's best to remove and rediscover with the competing system out of the picture.
-
With the RPI turned OFF, remove devices in the Alexa app, exit the app, then log back in and rediscover devices in the Alexa app. It's important that all the HABridge devices be removed to eliminate double entries. Maybe it'd be a good idea to remove or disable HABridge in the RPI to keep it from happening again. Others here can advice on that.
@brobin are you using HA Bridge. I thought the Smartenit hardware did away with the need for 3rd party emulators.
@Moose are you sure you have no port conflicts in your setup. Did you recently update either HomeGenie or HA Bridge. Amazon did a recent firmware upgrade and if you rely on HA Bridge for Alexa functionality this may be your problem.
Can you completely remove HomeGenie/HA Bridge from your setup temporarily and see if Smartenit and Alexa function correctly.This should help to narrow down your problem.
I am not sure about port conflicts. How does one know for certain? I think there was an HABridge update back in December. I will leave the PI off for a while and see if helps.
-
That sounds like the way to go. Additionally, look in the Alexa app for duplicates and if you see them I'd do the remove and rediscover to clean that up.
-
That sounds like the way to go. Additionally, look in the Alexa app for duplicates and if you see them I'd do the remove and rediscover to clean that up.
If I'm reading these Smartenit posts correctly that unit gives connectivity to Alexa. If that's the case theres no need for the HA Bridge. The devices in HomeGenie should already be exposed to Alexa via Smartenit. Could you confirm this.
-
Exactly. Here's a rough diagram of what happens if the porch light has an X10 switch set to E1:
Alexa, turn on porch light --> Smartenit Skill --> P2 Hub sends E1-On.
Of course, any other controller in the house will receive the E1-On as well which can trigger whatever else you'd like to have happen or the P2 Hub can do other things as defined in the 'Automation Rules' that you create. Unless you're using HG for things other than just X10 control the P2 Hub can handle all the schedules/macros itself.
-
Exactly. Here's a rough diagram of what happens if the porch light has an X10 switch set to E1:
Alexa, turn on porch light --> Smartenit Skill --> P2 Hub sends E1-On.
Of course, any other controller in the house will receive the E1-On as well which can trigger whatever else you'd like to have happen or the P2 Hub can do other things as defined in the 'Automation Rules' that you create. Unless you're using HG for things other than just X10 control the P2 Hub can handle all the schedules/macros itself.
Exactly as I thought. In that case HA Bridge is not necessary in this setup and should be disabled. Only adding unnecessary processes in the system. I’m now wondering if in fact two sets of devices have been discovered by Alexa. One set by Smartenit and one set by HA Bridge. After all HA Bridge acts as Bridge for the Alexa discovery service.
-
Yes, that's my thought too - and my personal experience when migrating from Alex10 to the PiAlexaHub and finally to the P2 Hub. That's why I made the suggestion I did earlier today.
On the first migration I learned that the Alexa app must be cleared lest there be two competing entries that would result in a failed command. Unless cleared completely as described earlier I found that the old entries could be spontaneously rediscovered! That was 2 years ago so perhaps that's been fixed.
-
Yes, that's my thought too - and my personal experience when migrating from Alex10 to the PiAlexaHub and finally to the P2 Hub. That's why I made the suggestion I did earlier today.
On the first migration I learned that the Alexa app must be cleared lest there be two competing entries that would result in a failed command. Unless cleared completely as described earlier I found that the old entries could be spontaneously rediscovered! That was 2 years ago so perhaps that's been fixed.
You need to delete the Alexa devices one by one in your Alexa account and not as a bulk delete in order for Alexa not to see them again. As I mentioned if Smartenit has taken over the Alexa bridge function it’s important not to have another bridge operating on the network. So disable HA Bridge, go to Alexa account and delete devices individually and run the Alexa discovery service.
-
All of the devices associated with HG seem to be gone from Alexa. HG and HABridge are off. Individual commands through Alexa to Smartenit Devices are working fine. But, I had created 2 "Routines" in Alexa to control 2 sets of devices. A few hours after Re-Discovery, Alexa forgets them. I just took a look in the Alexa app. The Routine Titles are still there, but all the "Actions" have disappeared.
I would like to find a way to control a group of devices from within the Harmony, the way I did with HG.
When everything was "working" with HG and the Harmony, yes there were 2 sets of devices, and for the most part, they co-existed nicely. So I have dropped from 25 devices to just 15.
-
All of the devices associated with HG seem to be gone from Alexa. HG and HABridge are off. Individual commands through Alexa to Smartenit Devices are working fine. But, I had created 2 "Routines" in Alexa to control 2 sets of devices. A few hours after Re-Discovery, Alexa forgets them. I just took a look in the Alexa app. The Routine Titles are still there, but all the "Actions" have disappeared.
When everything was "working" with HG and the Harmony, yes there were 2 sets of devices, and for the most part, they co-existed nicely. So I have dropped from 25 devices to just 15.
They’ll coexist until Amazon do a firmware update. The HA Bridge functionality will then break and that’s when your problem starts. Unlike registered skills like the one you have in your Smartenit hub these firmware updates kill emulators like HA Bridge. As it is now you no longer need the HA Bridge so leave it disabled. That should solve most of your issues.
-
I don't own a smartenit but if you can create scenes in it then create one with all the modules you want turned on. Then in Alexa have her discover scenes they should get discovered.
-
I tired creating a "Scene" but I did not have an appropriate "Controller" to trigger the Scene. So, at Brobin's suggestion, I tried the Alexa Routine. Perhaps Brobin can help.
-
OK create a device group in Alexa , add your named X10 devices you wish to it and give it a name.
then just say, Alexa turn on/off (Group Name)
-
I tired creating a "Scene" but I did not have an appropriate "Controller" to trigger the Scene. So, at Brobin's suggestion, I tried the Alexa Routine. Perhaps Brobin can help.
When you you don’t have an appropriate "Controller" what controller are you referring to. Is it the Smartenit hub or you CM15. Which is the priority here, Alexa or X10
-
I tired creating a "Scene" but I did not have an appropriate "Controller" to trigger the Scene. So, at Brobin's suggestion, I tried the Alexa Routine. Perhaps Brobin can help.
The 'Scenes' function in the P2 Hub is only for Insteon devices but you can essentially do the same thing by creating an Automation Rule. You can create a dummy X10 device to use as a trigger.
For example, define an Appliance Module as "Office Lamps" and assign it X10 code 'N1' (or whatever) and save it.
Next, create an 'Automation Rule' called 'Office Lamp Scene' or whatever you like.
In the 'When' section select 'ANY' condition, tap '+' then 'Device Status' and choose the 'Office Lamps' device you created earlier, then tap 'Is on' and 'Everyday' and 'Save.' The Summary will say 'Every day when Office Lamps is On.' You could also add a daily sunset +/- condition here as well (that's why I said choose ANY instead of ALL conditions).
Now, in the 'Then do' section tap '+' then select a device and follow the prompts to turn it on and set the dim level as appropriate, tap 'Save.' Repeat for each device in the scene and 'Save.'
Have Alexa discover devices to find the new 'Office Lamps' device and you're done. Tell Alexa to "turn on office lamps" and all the actions in the Automation Rule will happen. Give it a try!
-
I tired creating a "Scene" but I did not have an appropriate "Controller" to trigger the Scene. So, at Brobin's suggestion, I tried the Alexa Routine. Perhaps Brobin can help.
When you you don’t have an appropriate "Controller" what controller are you referring to. Is it the Smartenit hub or you CM15. Which is the priority here, Alexa or X10
I asked Brobin that question I while back. http://forums.x10.com/index.php?topic=31349.0
-
I tired creating a "Scene" but I did not have an appropriate "Controller" to trigger the Scene. So, at Brobin's suggestion, I tried the Alexa Routine. Perhaps Brobin can help.
When you you don’t have an appropriate "Controller" what controller are you referring to. Is it the Smartenit hub or you CM15. Which is the priority here, Alexa or X10
I asked Brobin that question I while back. http://forums.x10.com/index.php?topic=31349.0
The "appropriate controller" is a misnomer as the controller is appropriate for scene control of Insteon Scenes but not X10. So it'd be more accurate if the error message said there were no appropriate devices. For X10 devices, scenes can be created under 'Automation Rules' rather than 'Scenes' which are only available for Insteon.
-
I dare not mention this but if the broadcast service is enabled in HomeGenie, the Smartenit hub should discover its devices. Again it’s trying to determine where the priority will be placed on the setup. HomeGenie will do all scenes, macros, timers and automations that any setup would need. If it’s just about Alexa leave things as they are.
I do suggest that if anyone wants the best of both worlds that’s simple to setup and use I’d go the Homeseer Hometroller route. Based around the Raspberry Pi 3 it has everything anyone would need for both the novice and the advanced user. While X10 is no longer supported the slack has been taken up by a very knowledgeable community. I can confirm that the CM11, CM15 and the CM19 will all work. At least twice a year they have a half price sale https://shop.homeseer.com/products/homeseer-pi-smart-home-hub
-
I tired creating a "Scene" but I did not have an appropriate "Controller" to trigger the Scene. So, at Brobin's suggestion, I tried the Alexa Routine. Perhaps Brobin can help.
When you you don’t have an appropriate "Controller" what controller are you referring to. Is it the Smartenit hub or you CM15. Which is the priority here, Alexa or X10
I asked Brobin that question I while back. http://forums.x10.com/index.php?topic=31349.0
Any guesses as to why/how Alexa just "forgot" all the "Actions" that I had put into the Routines? :) B:(
-
Any guesses as to why/how Alexa just "forgot" all the "Actions" that I had put into the Routines? :) B:(
If the modules you had in the routines were from modules HA-Bridge was handling when you deleted the device they would be removed from a routine.
-
I dare not mention this but if the broadcast service is enabled in HomeGenie, the Smartenit hub should discover its devices. Again it’s trying to determine where the priority will be placed on the setup. HomeGenie will do all scenes, macros, timers and automations that any setup would need. If it’s just about Alexa leave things as they are.
I do suggest that if anyone wants the best of both worlds that’s simple to setup and use I’d go the Homeseer Hometroller route. Based around the Raspberry Pi 3 it has everything anyone would need for both the novice and the advanced user. While X10 is no longer supported the slack has been taken up by a very knowledgeable community. I can confirm that the CM11, CM15 and the CM19 will all work. At least twice a year they have a half price sale https://shop.homeseer.com/products/homeseer-pi-smart-home-hub
The Smartenit Hub won't discover anything other than Insteon and ZigBee devices during the 'Add New Device' process. X10 devices are added manually by naming the device and selecting House and Unit codes.
-
I think I have a group activity working, but I have a new issue. I created a Device called Gooddmorning to turn on 2 lights and a radio in the AM. I altered the spelling to make sure Alexa found my new device instead of an obsolete one called Goodmorning. I control it with a pseudo module in X10 called B1. I can tap the device button in the Harmony app and everything works. But, with Alexa I can no longer say "Alexa Gooddmorning On" I have to say "Alexa turn on Gooddmorning". What the heck changed that I did not see coming. B:( ;D
-
I think I have a group activity working, but I have a new issue. I created a Device called Gooddmorning to turn on 2 lights and a radio in the AM. I altered the spelling to make sure Alexa found my new device instead of an obsolete one called Goodmorning. I control it with a pseudo module in X10 called B1. I can tap the device button in the Harmony app and everything works. But, with Alexa I can no longer say "Alexa Gooddmorning On" I have to say "Alexa turn on Gooddmorning". What the heck changed that I did not see coming. B:( ;D
Set it up as a Routine in the Alexa app. When we say "Alexa good morning" it triggers a pseudo module that causes her to tell us the weather, raise the blackout shades and turn off the alarm.
-
I think I have a group activity working, but I have a new issue. I created a Device called Gooddmorning to turn on 2 lights and a radio in the AM. I altered the spelling to make sure Alexa found my new device instead of an obsolete one called Goodmorning. I control it with a pseudo module in X10 called B1. I can tap the device button in the Harmony app and everything works. But, with Alexa I can no longer say "Alexa Gooddmorning On" I have to say "Alexa turn on Gooddmorning". What the heck changed that I did not see coming. B:( ;D
Set it up as a Routine in the Alexa app. When we say "Alexa good morning" it triggers a pseudo module that causes her to tell us the weather, raise the blackout shades and turn off the alarm.
rofl B:( I just deleted my Alexa Routines because there was a name conflict with my new Automation Rule setup within Smartenit. :)
So, when you are trying something new, how do you choose whether it will be a Smartenit device and/or Automation Rule vs an Alexa Routine? There must be some advantages or disadvantages that I do not immediately see, yet! ???
-
I think I have a group activity working, but I have a new issue. I created a Device called Gooddmorning to turn on 2 lights and a radio in the AM. I altered the spelling to make sure Alexa found my new device instead of an obsolete one called Goodmorning. I control it with a pseudo module in X10 called B1. I can tap the device button in the Harmony app and everything works. But, with Alexa I can no longer say "Alexa Gooddmorning On" I have to say "Alexa turn on Gooddmorning". What the heck changed that I did not see coming. B:( ;D
Set it up as a Routine in the Alexa app. When we say "Alexa good morning" it triggers a pseudo module that causes her to tell us the weather, raise the blackout shades and turn off the alarm.
rofl B:(I just deleted mt Alexa Routines because there was a name conflict with my new Automation Rule setup within Smartenit. :)
So, when you are trying something new, how do you choose whether it will be a Smartenit device and/or Automation Rule vs an Alexa Routine? There must be some advantages or disadvantages that I do not immediately see, yet! ???
I prefer to use a pseudo module (I like your name for it) to trigger an Automation Rule (aka Macro) in the p2 Hub as I can easily modify it without dealing with the Alexa app. The only time I have multiple items in a routine is if multiple gateways/hubs are involved.
For example, I have one routine called 'Start Cooking' that my wife uses. When Alexa hears that, she communicates first to a stand alone Somfy gateway to lower the lanai screens and 8 seconds later to the P2 Hub to open the sliding doors to the lanai and turn on some lights. So if I wanted to add, delete or modify which lights or their dim levels, I would do that in the Automation Rule rather than messing with the Alexa routine which I'd be more likely to break.
-
All of the devices associated with HG seem to be gone from Alexa. HG and HABridge are off. Individual commands through Alexa to Smartenit Devices are working fine. But, I had created 2 "Routines" in Alexa to control 2 sets of devices. A few hours after Re-Discovery, Alexa forgets them. I just took a look in the Alexa app. The Routine Titles are still there, but all the "Actions" have disappeared.
When everything was "working" with HG and the Harmony, yes there were 2 sets of devices, and for the most part, they co-existed nicely. So I have dropped from 25 devices to just 15.
They’ll coexist until Amazon do a firmware update. The HA Bridge functionality will then break and that’s when your problem starts. Unlike registered skills like the one you have in your Smartenit hub these firmware updates kill emulators like HA Bridge. As it is now you no longer need the HA Bridge so leave it disabled. That should solve most of your issues.
Could you suggest Linus command(s) to elegantly remove HABridge completely? Or should I just disable it?
-
I am still a little puzzled. I have an Automation Rule for Goodmorning...
When all of these conditions are met:
Every day when Gooddmorning is On
EFFECTS
Then do the following:
After 1 secs, turn On Kitchen Radio
After 1 secs, turn On Kitchen Counter
After 1 secs, set Kitchen Light to 100%
After 5 secs, turn Off Gooddmorning
When I run it, I get these Events reading from the bottom up...
Kitchen Light turned on INFO 2021-02-14T15:11:53.000Z
Kitchen Light set to 99% INFO 2021-02-14T15:11:53.000Z
Gooddmorning turned off INFO 2021-02-14T15:11:46.000Z
Action "After 5 secs, turn Off Gooddmorning" triggered INFO 2021-02-14T15:11:44.000Z
Kitchen Counter turned on INFO 2021-02-14T15:11:42.000Z
Kitchen Radio turned on INFO 2021-02-14T15:11:42.000Z
Action "After 1 secs, set Kitchen Light to 100%" triggered INFO 2021-02-14T15:11:41.000Z
Action "After 1 secs, turn On Kitchen Counter" triggered INFO 2021-02-14T15:11:40.000Z
Action "After 1 secs, turn On Kitchen Radio" triggered INFO 2021-02-14T15:11:40.000Z
Gooddmorning turned on INFO 2021-02-14T15:11:39.000Z
"Gooddmorning " rule has been triggered INFO 021-02-14T15:11:39.000Z
What is odd to me, the Kitchen Light does come on 3rd, but shows up in the Event log after the Automation Rule has terminated.
Also, when I had the Kitchen Light selected to come 1st in the Automation Rule, it turned on last, at least 10 seconds after the Rule terminated. Any thoughts Brobin?
-
Could you suggest Linus command(s) to elegantly remove HABridge completely? Or should I just disable it?
sudo systemctl stop ha-bridge.service
sudo systemctl disable ha-bridge.service
That will disable it and prevent it from loading at bootup
You can then remove the HA-Bridge and service if you wish.
-
Could you suggest Linus command(s) to elegantly remove HABridge completely? Or should I just disable it?
sudo systemctl stop ha-bridge.service
sudo systemctl disable ha-bridge.service
That will disable it and prevent it from loading at bootup
You can then remove the HA-Bridge and service if you wish.
What about complete removal. Would it be something like
sudo apt-get remove habridge
then
rm -r "any habridge folders"
-
I am still a little puzzled. I have an Automation Rule for Goodmorning...
When all of these conditions are met:
Every day when Gooddmorning is On
EFFECTS
Then do the following:
After 1 secs, turn On Kitchen Radio
After 1 secs, turn On Kitchen Counter
After 1 secs, set Kitchen Light to 100%
After 5 secs, turn Off Gooddmorning
When I run it, I get these Events reading from the bottom up...
Kitchen Light turned on INFO 2021-02-14T15:11:53.000Z
Kitchen Light set to 99% INFO 2021-02-14T15:11:53.000Z
Gooddmorning turned off INFO 2021-02-14T15:11:46.000Z
Action "After 5 secs, turn Off Gooddmorning" triggered INFO 2021-02-14T15:11:44.000Z
Kitchen Counter turned on INFO 2021-02-14T15:11:42.000Z
Kitchen Radio turned on INFO 2021-02-14T15:11:42.000Z
Action "After 1 secs, set Kitchen Light to 100%" triggered INFO 2021-02-14T15:11:41.000Z
Action "After 1 secs, turn On Kitchen Counter" triggered INFO 2021-02-14T15:11:40.000Z
Action "After 1 secs, turn On Kitchen Radio" triggered INFO 2021-02-14T15:11:40.000Z
Gooddmorning turned on INFO 2021-02-14T15:11:39.000Z
"Gooddmorning " rule has been triggered INFO 021-02-14T15:11:39.000Z
What is odd to me, the Kitchen Light does come on 3rd, but shows up in the Event log after the Automation Rule has terminated.
Also, when I had the Kitchen Light selected to come 1st in the Automation Rule, it turned on last, at least 10 seconds after the Rule terminated. Any thoughts Brobin?
I don't know enough, or even much, about the inner workings of the programming logic to do more than guess, but I'd suspect it has something to do sending a dim level to a lamp module/switch as opposed to just sending an ON command to an appliance module/switch.
What's the reason for the 1 sec delay between each device? It'd be interesting to see what happens if all the delays are set to 0 (or maybe you already know?). Even without the delays the commands will still be issued sequentially.
But it's all working as you want, correct?
-
I am still a little puzzled. I have an Automation Rule for Goodmorning...
When all of these conditions are met:
Every day when Gooddmorning is On
EFFECTS
Then do the following:
After 1 secs, turn On Kitchen Radio
After 1 secs, turn On Kitchen Counter
After 1 secs, set Kitchen Light to 100%
After 5 secs, turn Off Gooddmorning
When I run it, I get these Events reading from the bottom up...
Kitchen Light turned on INFO 2021-02-14T15:11:53.000Z
Kitchen Light set to 99% INFO 2021-02-14T15:11:53.000Z
Gooddmorning turned off INFO 2021-02-14T15:11:46.000Z
Action "After 5 secs, turn Off Gooddmorning" triggered INFO 2021-02-14T15:11:44.000Z
Kitchen Counter turned on INFO 2021-02-14T15:11:42.000Z
Kitchen Radio turned on INFO 2021-02-14T15:11:42.000Z
Action "After 1 secs, set Kitchen Light to 100%" triggered INFO 2021-02-14T15:11:41.000Z
Action "After 1 secs, turn On Kitchen Counter" triggered INFO 2021-02-14T15:11:40.000Z
Action "After 1 secs, turn On Kitchen Radio" triggered INFO 2021-02-14T15:11:40.000Z
Gooddmorning turned on INFO 2021-02-14T15:11:39.000Z
"Gooddmorning " rule has been triggered INFO 021-02-14T15:11:39.000Z
What is odd to me, the Kitchen Light does come on 3rd, but shows up in the Event log after the Automation Rule has terminated.
Also, when I had the Kitchen Light selected to come 1st in the Automation Rule, it turned on last, at least 10 seconds after the Rule terminated. Any thoughts Brobin?
I don't know enough, or even much, about the inner workings of the programming logic to do more than guess, but I'd suspect it has something to do sending a dim level to a lamp module/switch as opposed to just sending an ON command to an appliance module/switch.
What's the reason for the 1 sec delay between each device? It'd be interesting to see what happens if all the delays are set to 0 (or maybe you already know?). Even without the delays the commands will still be issued sequentially.
But it's all working as you want, correct?
I am getting closer. I added the delays earlier because some things seemed to be happening simultaneously and then some devices would not come on at all. So, I thought a bit of delay would create order. :) As I said above, when the Kitchen Light was put 1st, there was a 10-20 second delay. I was not sure if it would come on at all. Have you ever noticed Actions being completed after the Automation Rule completed on your setup?
I have one other odd behavior. I have two porch lights on the same code, and two porch motion sensors, also on their same code. I combine that with after sunset and before sunrise so that any motion at either porch turns on both Porch lights(and I have them stay on for 2 minutes). That has always worked well, initially with HG. Now with the P2, the front porch only comes on about 1/2 the time(but, the back porch light is on, so I know the logic worked). If I manually turn the front porch light on, it always goes out in 2 minutes. I have yet to swap out the switch, but it feels like a long shot. Thoughts?
-
I am getting closer. I added the delays earlier because some things seemed to be happening simultaneously and then some devices would not come on at all. So, I thought a bit of delay would create order. :) As I said above, when the Kitchen Light was put 1st, there was a 10-20 second delay. I was not sure if it would come on at all. Have you ever noticed Actions being completed after the Automation Rule completed on your setup?
I have one other odd behavior. I have two porch lights on the same code, and two porch motion sensors, also on their same code. I combine that with after sunset and before sunrise so that any motion at either porch turns on both Porch lights(and I have them stay on for 2 minutes). That has always worked well, initially with HG. Now with the P2, the front porch only comes on about 1/2 the time(but, the back porch light is on, so I know the logic worked). If I manually turn the front porch light on, it always goes out in 2 minutes. I have yet to swap out the switch, but it feels like a long shot. Thoughts?
OK, I understand the delays and what you describe confirms the time needed for the dim commands. If you don't need dimming from the P2 Hub for the Kitchen Light, you could try redefining it as an appliance module to eliminate the dim set delay. If you do need dimming from the P2, define 'Kitchen Light' as an appliance module and add a new device 'Kitchen Lamp' as a lamp module with the same House/Unit code for both. So the P2 Hub will have two devices with the same address. In your Gooddmorning rule, 'turn on Kitchen Light' will send the ON with no dimming. If you want to dim it with the app select Kitchen Lamp and set the level.
As for the porch lights, as I understand it, you have the two porch motion sensors (MS16 or similar & transceiver?) sending an X10 code to turn on the two porch lights set to that code. So the lights are turning on in response to the code sent by the motion sensor rather than a code sent from the P2 Hub. The P2 Hub hears the X10 code and responds by sending an OFF after a two minute delay. Is that right? If so, then I'd guess a signal issue from the transceiver to one of the porch lights. If I've got that wrong tell me more about how it's set up.
-
I am getting closer. I added the delays earlier because some things seemed to be happening simultaneously and then some devices would not come on at all. So, I thought a bit of delay would create order. :) As I said above, when the Kitchen Light was put 1st, there was a 10-20 second delay. I was not sure if it would come on at all. Have you ever noticed Actions being completed after the Automation Rule completed on your setup?
I have one other odd behavior. I have two porch lights on the same code, and two porch motion sensors, also on their same code. I combine that with after sunset and before sunrise so that any motion at either porch turns on both Porch lights(and I have them stay on for 2 minutes). That has always worked well, initially with HG. Now with the P2, the front porch only comes on about 1/2 the time(but, the back porch light is on, so I know the logic worked). If I manually turn the front porch light on, it always goes out in 2 minutes. I have yet to swap out the switch, but it feels like a long shot. Thoughts?
OK, I understand the delays and what you describe confirms the time needed for the dim commands. If you don't need dimming from the P2 Hub for the Kitchen Light, you could try redefining it as an appliance module to eliminate the dim set delay. If you do need dimming from the P2, define 'Kitchen Light' as an appliance module and add a new device 'Kitchen Lamp' as a lamp module with the same House/Unit code for both. So the P2 Hub will have two devices with the same address. In your Gooddmorning rule, 'turn on Kitchen Light' will send the ON with no dimming. If you want to dim it with the app select Kitchen Lamp and set the level.
As for the porch lights, as I understand it, you have the two porch motion sensors (MS16 or similar & transceiver?) sending an X10 code to turn on the two porch lights set to that code. So the lights are turning on in response to the code sent by the motion sensor rather than a code sent from the P2 Hub. The P2 Hub hears the X10 code and responds by sending an OFF after a two minute delay. Is that right? If so, then I'd guess a signal issue from the transceiver to one of the porch lights. If I've got that wrong tell me more about how it's set up.
That IS an interesting idea, 2 modules, same device. I will play with that.
Not quite. Two MS16's set to A1 and two lights on dimmers set to A2. The MS16's are logic ANDed with "after sunset and before sunrise" so that the lights go on with motion, after dark, for 2 minutes. It did work fine with HG. The flakey one is a newer decora type and the other is the old style small pushbutton.
-
I assume you have dispensed with HG completely in favour of the P2 so ensure you have stopped the HG service in order to avoid any conflicts in automation scripts between the two. You clearly have some form of bottleneck on the line. In fact if the P2 is looking after all your automations do you need X10 in HG. If not just disable X10 in HG altogether.
-
That IS an interesting idea, 2 modules, same device. I will play with that.
Not quite. Two MS16's set to A1 and two lights on dimmers set to A2. The MS16's are logic ANDed with "after sunset and before sunrise" so that the lights go on with motion, after dark, for 2 minutes. It did work fine with HG. The flakey one is a newer decora type and the other is the old style small pushbutton.
So we know the P2 Hub is sending A2-On because at least one of the modules responds. Does the Decora switch respond correctly from the app? You mention that they are dimmer switches and we know from the Kitchen Light that the P2 Hub sends dimming commands even for 100%. So, as in the Kitchen Light discussion, try defining the Porch lights as Appliance modules or even as bot as discussed above. Maybe the Decora switch is not receiving as strong a signal or understanding the dim to 99% command. Are the P2's PLM and HG's CM15A located on the same circuit?
-
While I am working on fine tuning the P2, HG is off. It is hard to know if the the P2-PLM and CM15A were on the same phase, but I do have a X10 phase connector with repeater in the house.
-
I don't know how the PLM X10 signal strength compares to the CM15a but I haven't had any issues. However I have an XTB-IIR in the house so I wouldn't expect any. Perhaps you could move the P2/PLM to the same out let as the CM15a and test from there. Also look around the outlets near the PLM and see if there are any chargers, printers, or PC's plugged in. If you're using a power strip for the PLM, try plugging the PLM directly into a wall outlet.
-
I assume you have dispensed with HG completely in favour of the P2 so ensure you have stopped the HG service in order to avoid any conflicts in automation scripts between the two. You clearly have some form of bottleneck on the line. In fact if the P2 is looking after all your automations do you need X10 in HG. If not just disable X10 in HG altogether.
I am keeping my options open. Once I get things sorted a little more, HG would make a nice desktop interface if I can get HG and P2 to play nice together. :) I hate working from a cell phone. So small, and only 1 device visible at a time.
-
Don't forget that you can also run the app from a tablet or you can access and work with everything from the web portal by logging into your account at https://console.smartenit.io/ from any browser.
-
I assume you have dispensed with HG completely in favour of the P2 so ensure you have stopped the HG service in order to avoid any conflicts in automation scripts between the two. You clearly have some form of bottleneck on the line. In fact if the P2 is looking after all your automations do you need X10 in HG. If not just disable X10 in HG altogether.
I am keeping my options open. Once I get things sorted a little more, HG would make a nice desktop interface if I can get HG and P2 to play nice together. :) I hate working from a cell phone. So small, and only 1 device visible at a time.
While you’re getting your P2/PLM setup sorted out I suggest you dispense with your CM15 and get yourself a CM19. It’s RF based and in my opinion is a lot more stable than the CM15 with HG. For $20 this should get your HG/Raspberry Pi back on track and should work a lot better with your Smartenit setup https://www.x10.com/cm19a.html
-
The system with the P2 is running pretty well. I even have my wireless control pads working again. I found a CM19 in my parts box, so I will give that a try. I do have one more oddity though. For the last 4 nights, between 7:15 and 7:40, the command for "Gooddmorning on" gets run according to the Smartenit event log. It results in the Kitchen Radio getting turned back on. I see no corresponding event in Alexa's history, except my command to turn off the radio. This Command has never been automated or put on a timer by me. It has always been a voice command. Any thoughts?
-
Given the times, could it be related to some sunset or sunrise time? Can you send a screenshot of your Automation Rule? It might be easier to do that from the web portal at console.smartenit.io . I understand that you don't see any activity in the Alexa app but what about in the Smartenit app? Any other controller (HG) set to turn things on at dawn or dusk?
-
Given the times, could it be related to some sunset or sunrise time? Can you send a screenshot of your Automation Rule? It might be easier to do that from the web portal at console.smartenit.io . I understand that you don't see any activity in the Alexa app but what about in the Smartenit app? Any other controller (HG) set to turn things on at dawn or dusk?
I did say that in the Smartenit event log, the "Gooddmorning" script gets run. It is about 2 hours past sunset though. They are pretty basic, but I will attach the 2 Automation Rules.
-
Could whatever device address you're using for 'Gooddmorning' be getting turned on by another controller during that time?
-
Could whatever device address you're using for 'Gooddmorning' be getting turned on by another controller during that time?
Only if there was some harmonic crossover or frequency overlap. All my active devices are on the "A" channel. I put the Gooddmorning pseudo device on B1.
-
That's a strange one. The next thing that comes to mind is to ask Alexa ro cancel all alarms and reminders just to be sure that's not triggering it. I assume you don't have an X10 tester to monitor.
-
That's a strange one. The next thing that comes to mind is to ask Alexa ro cancel all alarms and reminders just to be sure that's not triggering it. I assume you don't have an X10 tester to monitor.
No I do not have an X10 Tester, but I do not have any Alarms, Reminders or Routines in Alexa either. :) I suppose I could just try a different device address, say B3 to see what happens.
-
Might as well try that but change the Housecode too just to be sure, like C-3. If you have a lamp or appliance module that you could set to B1 it'd be interesting to see if it turns on at the same time. The X10 B1-ON is not sent by Alexa or the P2 so it would tell us if somehow something is sending that code.
-
Might as well try that but change the Housecode too just to be sure, like C-3. If you have a lamp or appliance module that you could set to B1 it'd be interesting to see if it turns on at the same time. The X10 B1-ON is not sent by Alexa or the P2 so it would tell us if somehow something is sending that code.
Yeah! Problem solved. :)% This discussion helped a lot. Thanks Brobin. But, it took me a while to sort through it. I made a post here... http://forums.x10.com/index.php?topic=31432.0 Saying that I had this Timer and how well it still worked. So, I got thinking outside of the box a little, because I have not done anything with the Timer in years, except "enable or disable" it. My problem comes from the way I disable it. I turn the rotary House Code switch from A to B or P(one click either direction). In this case I had it on B which was turning on the radio via Gooddmorning at 7:15 +/- 30 minutes. I guess I should move my Gooddmorning and Bedttime routines to house code C. :'
-
Glad to hear you worked it out!