Multisensor 6 problems

  • 531 Views
  • Last Post 07 March 2017
Dignan17 posted this 09 February 2017

I just got a Multisensor 6, added it to my network, and changed the type from motion sensor to MultiLevelSensor (I'm assuming that's right...), and did an auto configure. Now I'm really confused.

Mainly, I'm puzzled by the readings on the sensor. I have temperature and humidity and stuff like that, but I also appear to have FIVE motion sensors listed on there for some reason. 3 of them show a value of 0 and two show a value of 255. Walking in front of the sensor doesn't appear to change these values.

Actually, the values don't really seem to change. I just turned on the light in the room where the sensor is, changing it from pitch black to illuminated by two 100W bulbs, and "luminance" still has a value of 0.

What's going on?

Order By: Standard | Newest | Votes
Dignan17 posted this 07 March 2017

So at support's request I went off/online again...and it works now. I have no idea why, even though I went off/online several times before, and even restarted the whole computer, but it works now. Thanks everyone for their help, especially Axial support.

Dignan17 posted this 05 March 2017

I've submitted a help ticket and Ryan is helping me with this.

The room is completely isolated with no windows, and I'm closing the door when I leave. There is no movement when I'm gone, and the room never switches to "Occupied," which is clearly the problem, and I'm not sure why. The other room I have this set up in worked fine before and works fine now, and it was set up the exact same way.

cowinger posted this 05 March 2017

My bad, you are correct it would not turn on unless that was done. Is the sensor being re-triggered? By a flickering light or through light from a window? If you move the sensor from that room to the same room your other sensor is in and set it next to the other one does it work then? Does the light go on in the other room and then off after no motion and the timeout?

Also, does it go to "occupancy" when there is motion detected and then to "no occupancy" (not sure of actual wording) when the sensor times out and then it should count down 2 min and shut off.

Dignan17 posted this 04 March 2017

Both those things are correct. If the motion weren't enabled, the scene wouldn't be able to turn the light on, no?

And the occupancy timeout is set to 2 minutes.

cowinger posted this 04 March 2017

The only two things I can think of are:

1. Make sure the motion sensing is turned on by way of the parameter (per previous post)

2. The value for the "occupancy timeout minutes" I believe must be >=1

Might be repeats but all I can think of.

nelis249 posted this 04 March 2017

Sweeeeeet (minion voice).

Dignan17 posted this 04 March 2017

All of that is correct. I've submitted a ticket.

rscott posted this 04 March 2017

Can you verify that you did the following:

  • added the laundry room light to it's own room
  • added the motion sensor to the same room
  • set the motion sensor as a device of type "MotionSensor"
  • double click the laundry room light, check "allow room manager use"
  • in the room setup, make sure that "Enable Room Occupancy Management" is checked

If you've done all that, toss us a support ticket and we can give you some more personalized support to troubleshoot the problem.

For the other sensor stats, that's how sensors are designed. Axial can't poll them because they are battery powered, so it just has to wait for the sensors to send the stats. Most of the time the default behavior for the sensors is to send them hourly (though it depends on the manufacturer). In almost all cases, you can change how each sensor works to get it to send more frequently but this will be at the cost of battery life. What happens is when you restart, Axial "forgets" all the values that were sent previously and can only show them again once that sensor decides to communicate with the system again.

Dignan17 posted this 04 March 2017

I'm approaching the end of my patience with Axial.

I ordered another Aeon Labs Multisensor 6. I placed it in my laundry room. I set up a scene and room just like I did in my garage. The scene turns the light on, and after a specified amount of time, the room occupancy monitor turns the light off.

But it's not working.

The scene turns the light on, but the room occupancy does not change, so the light stays on because there's no countdown to start.

I'm really frustrated by all these weird behaviors of the software. I set everything up exactly like I did before. The only thing I can think of that's messing Axial up is that prior to installing this second motion sensor, the laundry room light was part of the garage occupancy scene/room setup. But I removed it before I set the laundry room scene/light up.

I've turned the server off and on again, restarted the computer, whatever I could think of.

I've also noticed that when the server restarts, it takes forever for the other stats on the sensors to fill in. Like, dozens of minutes.

rscott posted this 04 March 2017

You can create a new device by clicking the icon next to the humidity reading. You can then use that device to trigger scenes.

nelis249 posted this 04 March 2017

With the multi-sensor, is there anyway to trigger off another sensor property than motion? For example, I have a sensor in my bathroom on the cieling (primarly for triggering lights) but I want to add an additional scene event to turn the exhaust fan on when humidity reaches a certain point.

rscott posted this 25 February 2017

That's right; once the sensor resets, the timeout starts to count-down and then turn off the lights once it hits 0.

Dignan17 posted this 25 February 2017

Interesting! Thanks for the heads up. I ran the auto configure and restarted the software a few times (for other reasons) and everything seems to be working fine now.

Ryan, am I correct in concluding that the "Occupancy timeout minutes" figure is added onto the motion sensor timeout? It seems like the occupancy timeout doesn't start until the motion sensor resets and doesn't still detect motion.

rscott posted this 24 February 2017

I actually do this too - if I want a light on, I use a scene to get it on. I let the room manager turn things off when the room is no longer occupied. 

Also for what it's worth, Aeon Labs has "motion sensing" turned off by default (why would they do that?!). Unless you turn it on by configuring the param, or use auto configure, it won't work out of the box.

cowinger posted this 18 February 2017

Well I am glad you have found a fix for your situation. Also glad that there is no more confusion.

Dignan17 posted this 18 February 2017

Not quite. I'm using a scene to turn the lights on, and the room feature to handle occupancy detection. It works better than just a scene.

cowinger posted this 17 February 2017

nelis249,

Dignan17 was trying to figure out how to use the room feature to turn on and off a light using motion. I was merely trying to help me get it to work. I did suggest the scene in an earlier post. He then decided to use a scene instead so in the end he got his scene to work and the room idea was forgotten.

Hope this straightens it out.

nelis249 posted this 17 February 2017

@cowinger Not really sure I understand the Rooms feature. Scenes would perform the same function, lights on with motion, lights off without motion, and seem easier to understand.

Dignan17 posted this 14 February 2017

No, I didn't need another device, the motion sensor was working finally.

I ended up creating a scene to turn the lights in the room on using the motion sensor. As I suspected, if the light is triggered on and then is turned off manually any time before occupancy ends, or even afterward it's turned on and off without triggering motion, the next time I walk in the room the light won't turn on. It keys off the last state. I can understand why this is, though.

Anyway, all is good now.

cowinger posted this 13 February 2017

We must have crossed paths. If you have it working then you can ignore the stuff below. Glad to hear it is working!

You may have to create another device. Highlight your multisensor and on the right side you should see a value called "motion". To the left of that is a small icon. Click on that icon and give it a name to correspond with motion. Wait for that device to appear and change it to a motion sensor. Erase the one you have in that room and put this one in it's place. Go offline and back online and try again to trip the motion sensor  -  remember to wait until room says it is "Unoccupied" first before you trip the sensor.

Show More Posts
Change Language
Categories
Search
Popular Tags
Hot Topics
Close