Thank you although it does not work for 0258-0003-0083 like DTH did, where changes in ambient light were shown immediately in illuminance on device weboage. When I tried change settings, there is some message about device associations and that i have to delete device afterwards, In DTH I was able make changes. @JDRoberts Still DTH was more intuitive, I did not have to read any FAQ as I recall, I just logged in to ide.smartthings.com

no model number, only fingerprint: [image] samsungproblems: 0258-0003-0083 i tried also wink motion sensor WNK-MOT1P as someone in other thread and got similar garbled text in settings [image] Wink Motion Sensor Device Handler Devices & Integrations Hello, I did some searching and could not find an answer. I recently purchased a Wink Motion Sensor (WNK-MOT1P) to use with SmartThings. The device pairs without and issue and looks to be using the generic Z-WAVE Motion Sensor driver. One thing I don’t like about the device is that there’s a large blue LED that flashes whenever it senses motion. I did some research and it looks like when using it with a Wink hub that can actually be turned off. I then looked at the device spec on the Z-Wave Alliance registry (Link) and it looks like there’s actually a lot of configuration parameters (including the a parameter to turn off the LED) that we don’t have access to with the generic driver. I was wondering if there’s a specific Wink device handler (edge) that allows some of these settings to be c… either i did sth wrong but what? both sensors use “z-wave sensor and child thermostat mc” both fingerprints are listed in fingerprints.yml on Mariano’s github. both report motion correctly, both do NOT report illuminanace correctly, when i power cycle sensor illuminanace readings initially react to ambient light changes (tried test with flashlight) then illuminance gets stuck at 0% and no reaction to flashlight

[image]Post Requests for Zwave Edge Drivers Here (community-created) no model number, only fingerprint: [image] samsungproblems: 0258-0003-0083 Is there no model number on a physical sticker on the back of the unit? Any identifying information on the unit itself?

[image] samsungproblems: both report motion correctly, both do NOT report illuminanace correctly, when i power cycle sensor illuminanace readings initially react to ambient light changes (tried test with flashlight) then illuminance gets stuck at 0% and no reaction to flashlight This sounds like it reports this data using some non standard method. Without a device in hand to develop with I won’t be of much other help. My suggestion is to purchase newer generation (700/800 series) sensors from a vendor that is supported on ST.

Does not sound right to replace as both fingerprints are in database and others do not report errors. Everything worked perfectly with DTH from forum. Neo does not print model number, Wink prints on battery cover Same issue on two different brands: Neo coolcam 0258-0003-0083 and Wink WNK-MOT1P yet other people do not complain. [image] Edge for neo-coolcam-multi sensor? Connected Things Looking for Edge driver. Neo multi sensor Errors I get: [IMG_0317] [IMG_0316] [IMG_0318]

You can thank the ST dev team for those errors. There are a few posts about it, starting at the source: [image]SmartThings Android App Updates - Version 1.8.13.22 (Mar ‘24) The team has removed this for security reasons, inserting HTML in this way was not planned and it doesn’t have support, the content limit is 2 lines, regardless of the length of the string. Also, see here: [image] [Feature Request] Allowing HTML in Custom Capabilities Features & Feedback It used to work, but due to recent update in the app, the support to HTML was removed. For details, SmartThings Android App Updates - Version 1.8.13.22 (Mar ‘24) - #12 by AlejandroPadilla Here is how it is being displayed after the breaking change related above… [Raw HTML] If the reason is really security, it would be great to have a whitelist of safe tags and attributes that could be used. Everything else would be sanitized and wouldn’t show up. Suggestions Tags: table, thead, tbody, tfoot, tr, th, td Attributes: style, colspan, rowspan, align [edit: removed] :crazy_face:

The HTML display issue is one problem, but I believe the OP is primarily concerned about not getting all the sensor values: [image] samsungproblems: both report motion correctly, both do NOT report illuminanace correctly, when i power cycle sensor illuminanace readings initially react to ambient light changes (tried test with flashlight) then illuminance gets stuck at 0% and no reaction to flashlight I would note that it is very common for inexpensive batterypowered lux sensors to only sample the light value once every 15 minutes or so, so you generally can’t test them just by using a flashlight and briefly altering the light level. You have to turn on an overhead light and then wait for the next reporting period or put them in a dark closet and again wait for a while. They aren’t intended for instant response because that would use up too much battery life.

Oops, my bad! That’s what I get for rushing through the thread. I saw the screenshot and jumped to a partially-correct conclusion.

[image] JDRoberts: They aren’t intended for instant response because that would use up too much battery life. The defaults listed on the spec PDFs attached above set the lux reporting frequency parameter at 180 seconds, and the delta at 100lux. I would figure the neo coolcam model implementation to be similar. Hopefully @samsungproblems tested outside of that range, I would assume they did. The html issue on the Mc drivers would need to be addressed by @Mariano_Colmenarejo and doesn’t have anything to do with the lux reporting issue.

how would i test if i cant get to settings because of html errors. please enlighten and how come others do not have html errors? eventually i googled others with same problems: same happens with wink (illuminance or temperature does not matter LOL pun intended) so please JDRoberts tell me how much you want me to spend illuminanace sensor that works like Kevin’s DTH worked with cheap one (aka for worse of us i presume you meant), which one? So thank you Mariano for your kindness and genorosity but it is not sensor that gives problems. Why everybody gets likes for not helping me? Is this some bot? Gee what a mess, I feel like talking to kids

[image] samsungproblems: how would i test if i cant get to settings because of html errors. please enlighten and how come others do not have html errors? If you are using Mariano’s Z-Wave Device Config Mc to try and change the settings, it will not work because of the ST HTML issues. @JDRoberts @csstup and I have all suggested you try Mariano’s Z-Wave Sensor Mc driver for your sensor. It has the fingerprint for your device which identifies it as a sensor with motion and illuminance sensors and is battery powered. - id: "NEOCoolcam/0083" deviceLabel: NEO Coolcam Motion/Light Sensor manufacturerId: 0x0258 productType: 0x0003 productId: 0x0083 deviceProfileName: motion-battery-illuminance That profile also appears to allow for changing the illuminance value: name: motion-battery-illuminance components: - id: main capabilities: - id: motionSensor version: 1 - id: battery version: 1 - id: illuminanceMeasurement version: 1 config: values: - key: "illuminance.value" range: [0, 32000] - id: refresh version: 1 categories: - name: MotionSensor It’s not clear to me that you have tried that driver from your previous posts. If you have and it’s not working, then we will need some additional info about what specifically is not working and will probably want driver logging from your hub to help diagnose any issue. [image] samsungproblems: Why everybody gets likes for not helping me? Is this some bot? Gee what a mess, I feel like talking to kids I can assure you that the individuals that have been attempting to help you are not kids or bots and are some of the most skilled ST users and developers. The people “liking” their posts are confirming that the advice supplied can point you in the right direction. You continue to refer to the old architecture and whining about the new architecture. Follow the directions that these individuals are providing and post any requested data that might be needed to figure out how to get your device working correctly. Frankly, if you continue your combative tone, I expect everyone will simply ignore your future posts.

Problems with Neo Coolcam Zwave Sensor reports

Devices & Integrations Community Created Drivers

samsungproblems July 13, 2024, 1:56am 22

Hello
Would you please add 0258-0100-1027 neo haozee plug?
Kevin says these are the same:

in this thread post 125:

Topic		Replies	Views
[Edge drivers] Cannot connect NEO Coolcam NAS-PD02ZT device Developer Programs	32	1997	August 3, 2023
[OBSOLETE] Neo Coolcam Motion Sensor (NAS-PD01ZU-T) Community Created Drivers dth_motionsensor , dth_luxsensor , dth_temperature	88	8045	April 7, 2024
Neo Coolcam motion sensor support? Devices & Integrations	54	15927	March 27, 2019
Fingerprint on zwave sensor Writing Edge Drivers	3	1254	December 29, 2021
[ST EDGE] Z-Wave Sensor Driver Channel - including specific Ecolink, FortrezZ, HomeSeer, Monoprice and Zooz models Community Created Drivers edge-device , edge_sensors	282	15815	October 14, 2026

Problems with Neo Coolcam Zwave Sensor reports

Related topics