[Wiki] HTTP Features and Endpoints

[H_Local]

The initial post is a [WIKI] now.
Backlinked here

[Wiki] Where is the Wiki… [find what you are looking for]

A starting point for your search, below you find a selection of wikis, scattered throughout the forum. Some are marked [wiki] or (wiki) in their topic others are mentioned as “guide” or “howto” As with any wiki, if you have the rights, feel free to add, update or improve this post. ———————————————The Wiki Links ————————————— Most important i guess, getting started; by bobbyD (Hubitat staff) And by @rlithgow1 Also usefull, what devices have custom drivers available; by bobbyD as well O…

[rlithgow1]

@H_Local

EDIT: NOT WORKING ANYMORE

I think restart is gone as well...

[tray_e]

@H_Local

http://hubitat.local/hub/advanced/freeOSMemoryStatus

This one works for me as of 5 seconds ago

[WetCoaster]

Is there any endpoint that returns the date time when the hub starts from a reboot?

[Sebastien]

Are you looking to find out when the hub rebooted? If so, you can get this from the Logs under the -> Hub Events tab. You will see “systemStart” under “Name”.

[jlv]

@WetCoaster

Is there any endpoint that returns the date time when the hub starts from a reboot?

If you are looking for getting this date internal to the hub, you can see [RELEASE] Hub Information Driver v3. Install that and access the lastHubRestart or lastHubRestartFormatted via that device. Or you can look at the code to see how it computes it from location.hub.uptime.

[WetCoaster]

Thanks

[velvetfoot]

Is there a way to find out hub incoming voltage? Kind of like the /hub/advanced/internalTempCelsius command?

[gopher.ny]

@velvetfoot

Is there a way to find out hub incoming voltage?

No.

[velvetfoot]

Hey, it was worth a shot.

[jlv]

@velvetfoot

Is there a way to find out hub incoming voltage?

Note that the hub's power connection is micro-USB, so you'd only get a 5V reading (at best).

[velvetfoot]

@jlv

Note that the hub's power connection is micro-USB, so you'd only get a 5V reading (at best).

So? Plus, it's USB-C, I believe.

[dennypage]

@velvetfoot

Plus, it's USB-C, I believe.

The C-5 and C-7 are Micro USB.

[velvetfoot]

Ok, I guess I'm wrong.

[marktheknife]

The C8, which hasn’t been released yet, has a USB C connector according to the documents submitted to the FCC.

[velvetfoot]

I think I got messed up because of the title of the ups project.

[878a78cd3f530e07bfc6]

Hi everyone!
Is there an undocumented command to access cron on the hub (remove/finalize a particular job)? It doesn't seem to work in my system (after an upgrade from 2.2.8.156 to 2.3.5.141), no resolution has been found so far. Can't even list of things I've tried - going back to previous backups, soft reset, ...
It's a job with no name that stuck in the cron's schedule that prevents the service to continue running (can be seen via http://hubitat.local/logs --> Scheduled jobs).
Any other ideas how to kill that job?
Thanks in advance!

[bravenel]

I've forwarded this to one of the engineers. We'll look into it. Send my your hubID by PM.

[gopher.ny]

There isn't one right now, but I'll add one in the next build.

There are endpoints to delete all jobs for a given app/device, but they're not going to be useful in this scenario since the job is orphaned.

[878a78cd3f530e07bfc6]

Looking forward to any tool you can offer in the next build, thanks. Just FYI I've bumped into several more similar (if not identical) cases even through this community forum. Cron (internal) is really not easy to manage (without system access to the service which is a conceptual base for hubitat)