Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hue outdoor motion sensor #1201

Closed
MattL0 opened this issue Jan 31, 2019 · 14 comments

Comments

Projects
None yet
6 participants
@MattL0
Copy link

commented Jan 31, 2019

@fsandblom77

This comment has been minimized.

Copy link

commented Feb 4, 2019

Hi @MattL0
I have two of these sensors. Bought them today.
It doesn´t work :) What would you like me to try?

@ebaauw

This comment has been minimized.

Copy link
Contributor

commented Feb 4, 2019

Could you pair one with deCONZ and post the screenshots as described in https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Request-Device-Support.

From what I read, they're very much like the regular motion sensors, probably just another Model Identifier.

@fsandblom77

This comment has been minimized.

Copy link

commented Feb 4, 2019

Thanks for very quick answer!
I think you are right. Thought it should work as the regular motion sensor but not.
Here are the screenshots...
hue-outdoor-clusterinfo
hue-outdoor-info
hue-outdoor-nodeinfo

@fsandblom77

This comment has been minimized.

Copy link

commented Feb 4, 2019

Model identifier is SML002 for outdoor motion sensor and SML001 for the regular one so @ebaauw you are spot on! :)

@ebaauw

This comment has been minimized.

Copy link
Contributor

commented Feb 4, 2019

Indeed, this looks all too familiar. Could you try and read the SW Build ID and Date Code (double-click on the attribute to get a popup window). Just need to whitelist the model identifier, at 17 places in the code...

ebaauw added a commit to ebaauw/deconz-rest-plugin that referenced this issue Feb 4, 2019

Hue outdoor motion sensor
_Model Identifier_ SML002 (vs SML001 for the regular motion sensor).  See dresden-elektronik#1201.

ebaauw added a commit to ebaauw/homebridge-hue that referenced this issue Feb 4, 2019

@fsandblom77

This comment has been minimized.

Copy link

commented Feb 4, 2019

Thanks!
New C
hue-outdoor-clusterinfo3
luster Info screenshot..

@ebaauw

This comment has been minimized.

Copy link
Contributor

commented Feb 4, 2019

That does seem to be different (newer?) firmware. My regular Hue motion sensors report 6.1.0.18912.

manup added a commit that referenced this issue Feb 4, 2019

Hue outdoor motion sensor
_Model Identifier_ SML002 (vs SML001 for the regular motion sensor).  See #1201.
@fsandblom77

This comment has been minimized.

Copy link

commented Feb 4, 2019

Yes, you are correct. I compared firmware version with my other regular motion sensors and I have the same version as you 6.1.0.18912 so it seems like they have a new firmware on the new outdoor motion sensor.

@fsandblom77

This comment has been minimized.

Copy link

commented Feb 5, 2019

Just an update..
Updated to latest commit(Deconz)
I can now add the sensors from Phoscon. It is not visable in Phoscon but I can see it in Rest API. Also get presence detection, temperature and brightness.
So I'm happy because I'm using the Rest API.
Thanks @ebaauw for your effort!

@ebaauw

This comment has been minimized.

Copy link
Contributor

commented Feb 8, 2019

Also added support in homebridge-hue v0.11.14.

@NedSin

This comment has been minimized.

Copy link

commented Feb 14, 2019

Hello together,
is there any News or Information about an update for Phoscon who make the new Sensor Running ?

Phoscon Version: 262F0500

Best Greetings

@olemr

This comment has been minimized.

Copy link

commented Feb 27, 2019

on .59
Just added the HUE outdoor sensor from PWA.
Had one regular HUE sensor already added still with its default name: Motion Sensor.
After including the new outdoor sensor, the name of the original was changed to: Motion Sensor (2) and the newly included was not shown.
Had to rename the original and re-add. Now it works fine:
image

@mrmoritz01

This comment has been minimized.

Copy link

commented Mar 6, 2019

Hi, I can confirm that the Outdoor Sensor is running fine with Phoscon Version: 262F0500 and deconz-2.05.59-qt5.deb from https://www.dresden-elektronik.de/rpi/deconz/beta/deconz-2.05.59-qt5.deb.

I updated using Step 4 described here: https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Update-deCONZ-manually

And added the motion sensor from the Phoscon Web App, worked perfect.
It did not work on .58.

@stale

This comment has been minimized.

Copy link

commented Jul 4, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jul 4, 2019

@stale stale bot closed this Jul 11, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.