Brian Schlenker

There's a small bug with the workaround. Destructuring triggers the warning, accessing the property directly does not. ```ts // this still triggers the warning useEffect(() => { const { myFunction...

FWIW, es modules in node don't support __dirname or __filename either, with `import.meta.url` as the recommended alternative. https://nodejs.org/api/esm.html#esm_no_filename_or_dirname

Found an ugly workaround: monkey patch `Date.now` ```js Date.now = () => 0 ```

It looks like someone [created a fork](https://github.com/tonym97/homebridge-roku-client) that supports multiple devices. I will look into copying their changes once the iOS 12.2 stuff has been released. iOS 12.2 will have...

I released a beta of version 4.0.0, you can install with `npm install -g homebridge-roku@next`. It supports multiple devices, they’ll all show up in the remote app, and they’re auto...

I’m not sure what causes this. I switched to ATT fiber recently, and for a couple of days I was unable to auto discover my TV. But I tried again...

```json { "udn": "02780009-580a-1010-8036-ace010954e4e", "serial-number": "2N009F659510", "device-id": "4R6569659510", "vendor-name": "TCL", "model-name": "TCL 55FS3700", "model-number": "5115X", "model-region": "US", "screen-size": "55", "panel-id": "10", "tuner-type": "ATSC", "supports-ethernet": "false", "wifi-mac": "", "network-type": "wifi", "user-device-name":...

Can you try again with [v3.0.1](https://www.npmjs.com/package/homebridge-roku)? That UUID corresponds to a [TemperatureSensor](https://github.com/homebridge/HAP-NodeJS/blob/f3f032547f9c21f61c6338fbaf948b8258415012/src/lib/gen/HomeKit.ts#L4549-L4551), maybe it's coming from a different plugin?

Polling will be supported in the next major version. You can try it out now by installing `[email protected]`. The polling interval can be changed by setting [syncTimeout](https://github.com/bschlenk/homebridge-roku/blob/4.0/config.schema.json#L15-L21) in the config.

I just published 4.0.0-beta.3 which should fix this issue