View the state of an Aeon switch
Hi!
I have just started on a Zipato-system for my home. I have two questions:
1. Is there a way to read the Aeon Smart Switch to see what state it is in, just like the Aeon Illuminator can be read for what intensity it is set at? The rules creator says "rule2java:null" when I try to read if the Aeon Switch is on or off.
2. I am using Nexa WBT-912:s for controlling all lamps in my staircase. I thought this would be a good way to avoid pulling wires to every switch. Unfortunately, it seems quite slow, and error prone. Sometimes the light will not change at all, and sometimes it blinks a few times. My guess is that this is the WBT-912 connection to the Zipabox, since tapping the button on the app is a lot faster. Is there really no true battery driven transmitter that can be hidden in wall like the Nexa 912?
Thanks!
/Bo
The same question
Can you post the rule?
Can you post the rule?
Yes, thanks for any help!
As you can see, Rule 1 works great, but Rule 2 will not compile.
/Bo
Yes, thanks for any help!
As you can see, Rule 1 works great, but Rule 2 will not compile.
/Bo
I think there's a bug with the eaon switch devices. Because it doesn't look right.
Should look someting like this:
But what are u trying to do? Also put a email message in the rule to see where it stops.
I think there's a bug with the eaon switch devices. Because it doesn't look right.
Should look someting like this:
But what are u trying to do? Also put a email message in the rule to see where it stops.
I want to control the Aeon Switch from two (or more) different wall switches.
The Aeon Switch is a simple on/off, so there is no intensity variable. Also, it is a bit confusing that it says "meter", since it does not have the capabilities of energy metering. It should be a simple ON/OFF, or 1/0.
/Bo
I want to control the Aeon Switch from two (or more) different wall switches.
The Aeon Switch is a simple on/off, so there is no intensity variable. Also, it is a bit confusing that it says "meter", since it does not have the capabilities of energy metering. It should be a simple ON/OFF, or 1/0.
/Bo
So if switch B1 or B2 are on then turn on the Aeon labs? and when off turn off the Aeon labs?
Try this:
When switch B1 = On or B2 = On
If Aeon Labs=Off (use sensor)
Turn Aeon Labs On
New rule
When switch B1 = Off or B2 = Off
If Aeon Labs=On (use sensor)
Turn Aeon Labs Off
So if switch B1 or B2 are on then turn on the Aeon labs? and when off turn off the Aeon labs?
Try this:
When switch B1 = On or B2 = On
If Aeon Labs=Off (use sensor)
Turn Aeon Labs On
New rule
When switch B1 = Off or B2 = Off
If Aeon Labs=On (use sensor)
Turn Aeon Labs Off
Yes! You nailed it. The trick is to use the Aeon Switch as a sensor, and not a meter.
Now it compiles. I can't test it, since I'm at not at home, but I am confident it works.
Thanks!
/Bo
Yes! You nailed it. The trick is to use the Aeon Switch as a sensor, and not a meter.
Now it compiles. I can't test it, since I'm at not at home, but I am confident it works.
Thanks!
/Bo
No-problem. Have fun!
No-problem. Have fun!
You dont happen to have a solution to my question number 2? A Z-wave battery powered wall switch?
/Bo
You dont happen to have a solution to my question number 2? A Z-wave battery powered wall switch?
/Bo
Nope, contact support about this. They can help you.
Nope, contact support about this. They can help you.
The problem with 433 based devices is that some of them flood the air with repeated packets for seconds. In your case, Zipabox is probably trying to get through that noise.
Try adding a 2s delay in your rule.
The problem with 433 based devices is that some of them flood the air with repeated packets for seconds. In your case, Zipabox is probably trying to get through that noise.
Try adding a 2s delay in your rule.
I did so, thank you for that!
Why the flooding? And how can that be a good thing, since they (Nexa) has their own system that seems to work ok, apart from the 1-directional communication?
The DIY:er in me want to modify the transmitter though. How hard could it be?
/Bo
I did so, thank you for that!
Why the flooding? And how can that be a good thing, since they (Nexa) has their own system that seems to work ok, apart from the 1-directional communication?
The DIY:er in me want to modify the transmitter though. How hard could it be?
/Bo
Well the messages are repeated just in order for them to get through - receivers usually have input stages with automatic gain control and it takes them a message or two (depending on how strong the signal is) to set their gain to a level which allows them to decode the packet.
This usually isn't a problem in a one way system, because no two devices are trying to transmit at the same time.
With Zipabox, you have a transceiver which hears the message from your switch, and tries to act on it ASAP, not being stringent enough while checking if the air is clear. Will be improved in the next firmware.
The situation is even worse if user, not getting an immediate feedback, tries the switch multiple times. With 433 devices (even without Zipabox), it's best to push the button firmly, wait a second, and repeat if unsuccessful.
Well the messages are repeated just in order for them to get through - receivers usually have input stages with automatic gain control and it takes them a message or two (depending on how strong the signal is) to set their gain to a level which allows them to decode the packet.
This usually isn't a problem in a one way system, because no two devices are trying to transmit at the same time.
With Zipabox, you have a transceiver which hears the message from your switch, and tries to act on it ASAP, not being stringent enough while checking if the air is clear. Will be improved in the next firmware.
The situation is even worse if user, not getting an immediate feedback, tries the switch multiple times. With 433 devices (even without Zipabox), it's best to push the button firmly, wait a second, and repeat if unsuccessful.
Thanks Tomislav, that's very explanatory!
The problem for me is that I don't have spring loaded push buttons, but ordinary switches, so I need to create a normal staircase setting. Now that I know that the 433 devices can send multiple times, I have to ensure that the Zipabox, one acted upon a trigger, does not do it again, on that same trigger. Therefore I solved it using a variable for each switch.
I might put some delays in there, if needed.
I still can't get around how much faster the lamp responds to a click on the ImperiHome app on my Android phone. I mean, that's a far longer route, and still faster by far.
Thanks Tomislav, that's very explanatory!
The problem for me is that I don't have spring loaded push buttons, but ordinary switches, so I need to create a normal staircase setting. Now that I know that the 433 devices can send multiple times, I have to ensure that the Zipabox, one acted upon a trigger, does not do it again, on that same trigger. Therefore I solved it using a variable for each switch.
I might put some delays in there, if needed.
I still can't get around how much faster the lamp responds to a click on the ImperiHome app on my Android phone. I mean, that's a far longer route, and still faster by far.
I have the same problem with Nexa WBT-912 (oddly another Nexa transmitter works fine).
Tomislav, could you explain in more detail where in the rule I should put the delay to help with the slowness.
I have the same problem with Nexa WBT-912 (oddly another Nexa transmitter works fine).
Tomislav, could you explain in more detail where in the rule I should put the delay to help with the slowness.
Nexa LMLT-711 has the same problem as WBT-912.
Nexa LKCT-614-2 and LWST-615 work fine.
Nexa LMLT-711 has the same problem as WBT-912.
Nexa LKCT-614-2 and LWST-615 work fine.
Replies have been locked on this page!