Maker API

🛎️ Get Help Apps
1

Background...
Elevation 7.
64 devices, all Z-Wave. Mostly GE Enbrighten.
All linked to Home Control Assistant ("HCA") via Hubitat Maker API.

Struggled to include 2-Zooz Motion ZSE18 Sensors.
Both finally installed using the same procedure.
The first installed as Source=System.
The second installed as Source=User.
Installed community driver.

Problem...
Cannot get Maker API to recognize either of the Zooz Motion ZSE18 Sensors, i.e., they aren't listed with the previously installed 64 devices.
(Therefore, I cannot set up an interface with them from HCA.)

Any suggestions?

2

You clicked into the instance of Maker API in Apps and selected the 2 new devices under " Allow Endpoint to Control These Devices"?

3 Likes
3

Yes, I clicked into the instance of Maker API in Apps.
However, like I said above, the two motion sensors "aren't listed". They don't even appear in the list of devices under "Allow Endpoint to Control These Devices". Therefore, I can't click on them.

4

When you go to the Hubitat device page for each of these motion sensors, which driver is selected?

1 Like
5

This may sound silly, but you did change from Device to this driver and save? And did you hit "Configure" on the device settings page to bring the sensors attributes into the hub? Then set the parameters and save again?

What do the States on the top of the device's settings page show? Is the sensor working otherwise? (ignoring Maker for a minute)

1 Like
6

Assuming that the driver name is 1) in parentheses below the given device label, and 2) is also set forth in the column titled "Type", then motion sensor [1]'s driver is "Zooz Motion Sensor ZSE18" and motion sensor [2]'s driver is "Zooz Motion Sensor ZSE18 Advanced".

I presume that "Zooz Motion Sensor ZSE18" is the generic driver as it only shows 9 State Variables and that "Zooz Motion Sensor ZSE18 Advanced" is the community driver that I downloaded from Hubitat and shows 12 State Variables.

7

This may sound silly, but you did change from Device to this driver and save?
[Your question "change from Device to this driver and save" is not clear.]

And did you hit "Configure" on the device settings page to bring the sensors attributes into the hub?
[There is no "Configure" button on the device detail page for Motion Sensor [1] (Zooz Motion Sensor ZSE18).
[Yes, I did hit the "Configure" button on the device detail page for Motion Sensor [2] (Zooz Motion Sensor ZSE18 Advanced).

Then set the parameters and save again?
[If by "parameters" you mean "Preferences" (as there is not section labeled parameters), then the answer is yes.]

What do the States on the top of the device's settings page show?
Motion Sensor [1] shows:

Current States

  • acceleration : inactive
  • battery : 95
  • motion : inactive

State Variables (no values set)

  • configVal15 :
  • configVal14 :
  • configVal12 :
  • configVal19 :
  • configVal18 :
  • configVal17 :
  • lastBattery :
  • configVal32 :
  • configVal20 :

Motion Sensor [2] shows:

Current States

  • acceleration : inactive
  • battery : 85
  • motion : inactive
  • powerSource : battery

State Variables

  • configVal15 : 0
  • isConfigured : true
  • configVal14 : 0
  • configVal12 : 8
  • configVal19 : 0
  • configVal18 : 30
  • configVal17 : 1
  • pendingRefresh : false
  • assocNodeIds : []
  • lastWakeUp : 1689664667428
  • configVal32 : 10
  • configVal20 : 1

Is the sensor working otherwise? (ignoring Maker for a minute).
[Yes. Both will show * motion : active when motion is detected.

8

Rebooted the Hub and the motion sensors finally showed up.
Not sure why rebooting was necessary, but I should have done it in the first place.
Thanks for the help.

9

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.