Ben Hardill

Just to come back to this, It turns out it's not the Object Cache, but the Page Cache that is the problem. Also using Redis rather than Disk: Enhanced appears...

Yep, it's the prevCursor value, just need to work out how to set it correctly as it comes from the backend

As a hack I can remove the option to scroll back when jumping to a time, but it does feel useful to be able to back up if you get...

That is probably a question for the node-serial developers.

What I meant was both those nodes make use of `node-serial` (https://www.npmjs.com/package/node-serial) to list the available serial ports.

The list of available ports is generated by this code: https://github.com/node-red/node-red-nodes/blob/442576e838a267cde7ee3dd2fad634ea39eb5b0d/io/serialport/25-serial.js#L580-L590 Which just asks the node-serial code to list the available ports.

@Steve-Mcl the doc update was done by including the swager comment before the new functions, so the API doc has been updated.

@Steve-Mcl The timestamp is what we get back from the auditlog sanitizer (the thing that should be converting all the ids to hashes), we would need to re-parse them to...

The network tab in the console didn't show anything other than 200 status and it works with Chrome

This feels very like the problem I fixed yesterday, e.g. the posthog api calls not being wrapped in try/catch blocks