Maker API Error - "Cannot invoke method getAt() on null object"

🛎️ Get Help
1

I was having some troubles with my Maker API yesterday so spent a bit of time troubleshooting today. It is returning:

{"error":true,"type":"java.lang.Exception","message":"An unexpected error occurred."}

to every request.

This isn't a big deal for the requests that are to do something - the action still gets executed. But it is seen as an error by the applications requesting, and in the case of sensor data requests, there is no data returned.

For kicks, I created a new Maker API instance, in case it was an issue with old instances. That didn't improve. With debugging turned on, I get these logs:

[app:1205](http://192.168.77.221/logs#app1205)2020-07-25 12:18:52.106 [error](http://192.168.77.221/installedapp/configure/1205)java.lang.NullPointerException: Cannot invoke method getAt() on null object on line 815 (listDevices)
[app:1205](http://192.168.77.221/logs#app1205)2020-07-25 12:18:52.097 [debug](http://192.168.77.221/installedapp/configure/1205)deviceItem called
[app:1205](http://192.168.77.221/logs#app1205)2020-07-25 12:18:52.091 [debug](http://192.168.77.221/installedapp/configure/1205)listDevices called

when this is called:
http://192.168.77.221/apps/api/1205/devices?access_token=REMOVED

The getAt() error is visible for any call to any of my MakerAPI instances.

Running HE version 2.2.2.127.

Any thoughts?

2

@doctorkb
2.2.2.127 was pulled as a release because of known problems with MakerAPI.

3
4

I see this as well for multiple HE versions with old non-zwave plus Jasco dimmers, for another point of data.

5

Thanks guys... I searched first but obviously not well enough!