you need to force build the HomeBridge Dockers so they build with the new base image

2 hours ago, spl147 said:

you need to force build the HomeBridge Dockers so they build with the new base image

I already set up automated build, when the Dockerfile change, it will build automaticaly, it just finished building now 🙂

Updated, works!


Sent from my iPhone Xs Max using Tapatalk Pro

Updated, works!


Sent from my iPhone Xs Max using Tapatalk Pro

I'm getting this after updating homebridge:

terminate called after throwing an instance of 'std::bad_alloc'

 

Any ideas? 

 

Thanks!

9 minutes ago, mbezzo said:

I'm getting this after updating homebridge:

terminate called after throwing an instance of 'std::bad_alloc'

 

Any ideas? 

 

Thanks!

Log or screenshot please

 

is this what you're looking for?  the error would be the last line - takes awhile to show up so it's not in this one.

 

thanks!

homebridge.log

14 minutes ago, mbezzo said:

is this what you're looking for?  the error would be the last line - takes awhile to show up so it's not in this one.

 

thanks!

homebridge.log 68.69 kB · 1 download

Can you screen shot me where you see the errors messages?

these are the 3 errors.  the one from my OP just reads as text (not colored).

 

thanks!

1 minute ago, mbezzo said:

these are the 3 errors.  the one from my OP just reads as text (not colored).

 

thanks!

Seem like some plugins are causing problem try to pinpoint them down by removing it one by one

I've narrowed it down to the Nest plugin.  No changes whatsoever related to my Nest config - anybody have any ideas?  I've completely removed the docker/nuked its appdata folder and completely rebuilt.  Same issue - if I remove nest it works great. WTF! lol

 

I've even issued a new api token!

 

Anybody hear of any issues with Nest?  I can't seem to find much...  

 

thanks all!

And while I'm at it, has anybody figured out how to configure the Homebridge docker to see the log from the Homebridge gui?

 

 

2 minutes ago, mbezzo said:

I've narrowed it down to the Nest plugin.  No changes whatsoever related to my Nest config - anybody have any ideas?  I've completely removed the docker/nuked its appdata folder and completely rebuilt.  Same issue - if I remove nest it works great. WTF! lol

 

I've even issued a new api token!

 

Anybody hear of any issues with Nest?  I can't seem to find much...  

 

thanks all!

nest is converting to google single signon crap....api is changing, plugin most likely needs updating

2 minutes ago, mbezzo said:

And while I'm at it, has anybody figured out how to configure the Homebridge docker to see the log from the Homebridge gui?

 

 

im also waiting for this to be fixed properly! never worked for me

yeah, I'm aware of the massive Nest changes - but none of them have hit yet.  That's all happening later this year (and now they've sort of rescinded and are saying existing API use will not be disabled - you just can't make any new ones)

 

So... that doesn't quite explain it.  

 

Curious if anyone else using this docker still has Nest working?

Hello,

 

i have a problem to get a Homebridge-Zigbee Plugin working.

 

I dont know the reason

 

Error Log:

serialport.target.mk:110: recipe for target 'Release/obj.target/serialport/src/serialport.o' failed
make: Leaving directory '/usr/lib/node_modules/homebridge-zigbee/node_modules/serialport/build'
make: *** [Release/obj.target/serialport/src/serialport.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack at ChildProcess.emit (events.js:196:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:257:12)
gyp ERR! System Linux 4.19.43-Unraid
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/lib/node_modules/homebridge-zigbee/node_modules/serialport
gyp ERR! node -v v12.2.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: `prebuild-install || node-gyp rebuild`
npm ERR! Exit status 1


npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-05-28T20_30_47_335Z-debug.log

8 hours ago, loxar said:

Hello,

 

i have a problem to get a Homebridge-Zigbee Plugin working.

 

I dont know the reason

 

Error Log:

serialport.target.mk:110: recipe for target 'Release/obj.target/serialport/src/serialport.o' failed
make: Leaving directory '/usr/lib/node_modules/homebridge-zigbee/node_modules/serialport/build'
make: *** [Release/obj.target/serialport/src/serialport.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack at ChildProcess.emit (events.js:196:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:257:12)
gyp ERR! System Linux 4.19.43-Unraid
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/lib/node_modules/homebridge-zigbee/node_modules/serialport
gyp ERR! node -v v12.2.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: `prebuild-install || node-gyp rebuild`
npm ERR! Exit status 1


npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-05-28T20_30_47_335Z-debug.log

I don't think unraid docker have USB pass through yet.

13 hours ago, Siwat2545 said:

I don't think unraid docker have USB pass through yet.

USB is Passthrought with the Command --device=/dev/ttyACM0 and Privileged:  ON

 

No chance to get it working

Please install homebridge-zigbee and Tell me about your resault.

On 5/25/2019 at 7:00 PM, mbezzo said:

I've narrowed it down to the Nest plugin.  No changes whatsoever related to my Nest config - anybody have any ideas?  I've completely removed the docker/nuked its appdata folder and completely rebuilt.  Same issue - if I remove nest it works great. WTF! lol

 

I've even issued a new api token!

 

Anybody hear of any issues with Nest?  I can't seem to find much...  

 

thanks all!

Trying to set up the homebridge GUI using this repo as well. Homebridge runs fine until Nest spits out the token. Can’t access the GUI and I’m stuck with the same std bad_alloc. 

 

Cant be related to the new Nest api changes because they haven’t hit yet. Homebridge nonGUI from adair21 repo still works fine. 

Edited June 3, 20197 yr by spencers

1 hour ago, spencers said:

Trying to set up the homebridge GUI using this repo as well. Homebridge runs fine until Nest spits out the token. Can’t access the GUI and I’m stuck with the same std bad_alloc. 

 

Cant be related to the new Nest api changes because they haven’t hit yet. Homebridge nonGUI from adair21 repo still works fine. 

Can I have your full log?

Hi, I cant seem to get this working at all. I can see homebridge-tuya-web isn't loading but I'm not sure why.

 

Also haven't been able to register with homekit... also not sure why.

 

Thanks

 

Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:5 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [900 kB]
Get:6 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [1247 kB]
Fetched 2399 kB in 2s (1517 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 118 not upgraded.
/usr/local/lib
`-- [email protected]

[7/25/2019, 2:46:28 AM] Loaded config.json with 0 accessories and 1 platforms.
[7/25/2019, 2:46:28 AM] ---
[7/25/2019, 2:46:28 AM] ====================
[7/25/2019, 2:46:28 AM] ERROR LOADING PLUGIN homebridge-tuya-web:
[7/25/2019, 2:46:28 AM] /usr/local/lib/node_modules/homebridge-tuya-web/lib/tuyawebapi.js:212
catch {
^

SyntaxError: Unexpected token {
at createScript (vm.js:80:10)
at Object.runInThisContext (vm.js:139:10)
at Module._compile (module.js:616:28)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/usr/local/lib/node_modules/homebridge-tuya-web/lib/switch_accessory.js:1:82)
[7/25/2019, 2:46:28 AM] ====================
[7/25/2019, 2:46:28 AM] No plugins found. See the README for information on installing plugins.
[7/25/2019, 2:46:28 AM] Loading 1 platforms...
/usr/local/lib/node_modules/homebridge/lib/api.js:122
throw new Error("The requested platform '" + name + "' was not registered by any plugin.");
^

Error: The requested platform 'TuyaWebPlatform' was not registered by any plugin.
at API.platform (/usr/local/lib/node_modules/homebridge/lib/api.js:122:13)
at Server._loadPlatforms (/usr/local/lib/node_modules/homebridge/lib/server.js:316:45)
at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:86:36)
at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:45:10)
at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)

 

 

Here is my config

 

{
  "bridge": {
    "name": "Homebridge",
    "username": "CC:22:3D:E3:CE:30",
    "port": 51826,
    "pin": "031-45-154"
  },

  "description": "This is an example configuration file with one fake accessory and one fak>
  "ports": {
    "start": 52100,
    "end": 52150,
    "comment": "This section is used to control the range of ports that separate accessory >
  },
  "platforms": [
    {
    "platform": "TuyaWebPlatform",
    "name": "TuyaWebPlatform",
    "options": [
      {
        "username": "myusername",
        "password": "hunter2",
        "countryCode": "1",
        "platform": "tuya"
      }
               ]
   }
               ]
}

 

 

Siwat, I'm trying out your newish AdGuard Home container but have run into an error during install:

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='AdGuardHome' --net='bridge' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -p '3000:3000/tcp' -p '53:53/tcp' -v '/mnt/user':'/unraid':'rw' -v '/mnt/user/appdata/adguard_home/workingdir':'/opt/adguardhome/work':'rw' -v '/mnt/user/appdata/adguard_home/config':'/opt/adguardhome/conf':'rw' 'siwatinc/adguard_home'

132f753f0b6f9ca10d4b59b6238abed73d4f072809e3a6b16713ea13bf481b34
/usr/bin/docker: Error response from daemon: error while creating mount source path '/mnt/user/appdata/adguard_home/workingdir': mkdir /mnt/user/appdata: no medium found.

The command failed.

 

Any direction is appreciated.

Siwat, I'm trying out your newish AdGuard Home container but have run into an error during install:
 
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='AdGuardHome' --net='bridge' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -p '3000:3000/tcp' -p '53:53/tcp' -v '/mnt/user':'/unraid':'rw' -v '/mnt/user/appdata/adguard_home/workingdir':'/opt/adguardhome/work':'rw' -v '/mnt/user/appdata/adguard_home/config':'/opt/adguardhome/conf':'rw' 'siwatinc/adguard_home'
132f753f0b6f9ca10d4b59b6238abed73d4f072809e3a6b16713ea13bf481b34
/usr/bin/docker: Error response from daemon: error while creating mount source path '/mnt/user/appdata/adguard_home/workingdir': mkdir /mnt/user/appdata: no medium found.

The command failed.
 
Any direction is appreciated.

Sounds like your cache drive may be read only. Post your diagnostics

Ashamed to admit that I no longer live up to my teenage ethos of "it's better to burn out than fade away"

1 hour ago, Squid said:

Sounds like your cache drive may be read only. Post your diagnostics

...as requested!

unserver-diagnostics-20190822-1819.zip