Aeotec Multisensor 6

csteele · September 16, 2020, 7:53pm

Two thoughts...

The error will simply halt the program execution at that point. Effectively ignoring the fact it got a message.
It will not crash the hub. These errors occur in Development every day, and don't impact the hub. The hub just moves on to the next message/Event.

The built-in drivers are all supported by Hubitat and I'd suggest entering a Ticket at support@hubitat.com There's no enough detail to troubleshoot from one line, but the ticket process should allow you to give plenty. And really, there seems to be TWO problems, the Cast exception and the "stops responding" -- the 2nd is much much more critical.

kesnalawrence · December 27, 2020, 8:41pm

I'm having an issue with the Aeotec M6. It is reporting a consistent crazy value for temperature (-3276.8) and humidity (-1).

See screenshot below.

This happens several times a day and something several times an hour. When this happens, it triggers my heater to come which is expensive and troublesome in South Florida.

Any thoughts on what is happening?

I'm using v2.0.0 of Csteele's driver.

kesnalawrence · December 28, 2020, 2:12pm

@csteele Do you think it is possible to filter out these crazy values at the driver level? Maybe via a parameter where the user defines an acceptable range of values for each sensor and values outside of that range are ignored?

NoWon · December 28, 2020, 8:37pm

did you try updating Aeotec Multisensor 6 to the latest firmware version 1.13?

csteele · December 28, 2020, 8:55pm

Yes.

github.com

HubitatCommunity/AeotecMultiSensor6/blob/master/AeotecMultiSensor6.groovy

/*
 * IMPORT URL: https://raw.githubusercontent.com/HubitatCommunity/AeotecMultiSensor6/master/AeotecMultisensor6.groovy
 *
 *  Copyright 2015 SmartThings
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *
 *
 *         v2.1.0   Added in optional Auto No Motion timer.
 *                    Remove UpdateCheck, rely on HPM to check for a new version.
 *                    Refactor methods using createEvent to use sendEvent.
 *
 *         v2.0.2   Extended Motion Sensitivity to allow 0 (zero) which might be "off" depending on firmware.

This file has been truncated. show original

kesnalawrence · December 29, 2020, 4:03pm

Things seem good so far. I'll keep you posted.

kesnalawrence · December 29, 2020, 7:39pm

I updated the driver and the problem continues.

NoWon · December 29, 2020, 7:42pm

Did you update the firmware?
Which firmware are you running?

kesnalawrence · December 29, 2020, 7:48pm

That was a typo. I meant to say I updated the firm to 1.13 and the problem continues.

P.S.
Thank you for showing me how to update firmware OTA!!!

NoWon · December 29, 2020, 8:19pm

NP
I would power cycle the sensor after updating the firmware just to be sure.

I have 3 Aeotec Multisensor 6 sensors.
So far I only have seen one of the sensors read slightly high (28 Celsius/82 Fahrenheit) but I was not home at the time to check if it was legit or not. It is in a bathroom with a steam shower.
I created a RM rule to notify me if any of my sensors exceeds a set temp.

Also are your sensors battery powered or plugged in? (if battery maybe try a new battery)
Mine are all plugged in.

kesnalawrence · December 29, 2020, 8:36pm

My sensor is plugged in.

erktrek · December 29, 2020, 8:55pm

When you updated the firmware did you exclude and reinclude? You might have to do that if not.

NoWon · December 29, 2020, 10:25pm

only other suggestion is to preform a reset or health check as per the manual

Testing Health Connectivity.

Note - Health test does not test for routing communication health, only tests for direct communication with your gateway to determine if it has a healthy direct connection.

You can determine the health of your MultiSensor 6s connectivity to your gateway using a manual button press, hold, and release function which is indicated by the LED color.

Press and hold MultiSensor 6 Action button
Wait until the RGB LED turns into a Purple Color
Release MultiSensor 6 Action Button

The RGB LED will blink its Purple color while sending ping messages to your gateway, when it has finished, it will blink 1 of 3 colors:

Red = Bad Health

Yellow = Moderate Health

Green = Great Health

Be sure to watch for the blink, as it will only blink once very quickly.

Manually Factory Reset MultiSensor 6.

This method is not fully advised unless your gateway has failed, and you do not yet have another gateway to perform a general unpair on MultiSensor 6.

Press and hold MultiSensor 6 Action button
Wait until the RGB LED turns from:

Yellow
Purple
Red - blinks faster and faster
Green - You can let go here, it will continue to the next (Rainbow Cycle)
Rainbow Cycle

If your MultiSensor has been successfully factory reset from its previous network, the RGB LED will be active with a colourful gradient for 3 seconds. When you press the Action Button on MultiSensor, its green LED will blink. If the removal was unsuccessful, the green LED will stay solid for a few seconds when you press the Action Button.

kesnalawrence · December 29, 2020, 11:04pm

I'm trying an update to Csteele's driver where he corrected the filter statement. I hope the works!!!

kesnalawrence · December 30, 2020, 3:13pm

The technique you describe seems to be appropriate for when the device is not communicating. It is communicating after the firmware updated. It just produces wild values sometimes. It happens frequent enough to be an issue.

erktrek · December 30, 2020, 3:16pm

If you haven't done so already you might still give it a shot. Firmware updates can be kind of funky depending upon the device. I don't really think it's your issue though.

sync · January 5, 2021, 5:37pm

I just started setting up my Hubitat. I added a new MS6. I then moved an older MS6 from ST. The older one - probably about two years old - doesn't report lux, The new one does. The new one is on batteries. The old one is on USB power. I installed the driver mentioned earlier in this thread and set it to report a lux change of one. The old one reports motion so I know it works somewhat. Could this be a firmware issue? How can I find out the version? The older one didn't work on ST for lux either.

##Update
I just noticed on the driver page under state variables: firmware; 1.08
The new sensor just reported the version. It's 1.12

erktrek · January 6, 2021, 2:41am

And the latest and greatest looks like 1.13

You can update the firmware via the system firmware updater app but you will probably have to re-pair the sensor again.

ymerj · January 6, 2021, 3:31pm

I received a new M6 a few days ago. It reports firmware version 1.14

NoWon · January 12, 2021, 2:52am

Contacted Aeotec support.
website updated with 1.14 firmware.

Aeotec multisensor 6 firmware updated to 1.14