A homebridge plugin for Hatch Baby Rest night light
License: MIT License
This repo contains unofficial homebridge plugins for the Hatch Rest/Restore line of sounds machines
The homebridge-hatch-baby-rest plugin supports all Wifi models from the Hatch Rest/Restore lines
The homebridge-hatch-rest-bluetooth plugin supports the original Bluetooth Rest sound machine
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
After restarting homebridge, the first changes to the Hatch will take effect and connect successfully, but all subsequent requests are met with the titular error message.
Have attempted resetting the Rest but received the same issue.
I only have a Rest+, with homebridge running with bare minimum components the system i have it on does not have bluetooth and i get these errors related to loading noble.
ERROR LOADING PLUGIN homebridge-hatch-baby-rest: [4/5/2020, 8:49:27 PM] Error: EAFNOSUPPORT, Address family not supported by protocol at new Hci (/homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/lib/hci-socket/hci.js:74:18) at new NobleBindings (/homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:25:15) at Object.<anonymous> (/homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:546:18) at Module._compile (internal/modules/cjs/loader.js:1158:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10) at Module.load (internal/modules/cjs/loader.js:1002:32) at Function.Module._load (internal/modules/cjs/loader.js:901:14) at Module.require (internal/modules/cjs/loader.js:1044:19) at require (internal/modules/cjs/helpers.js:77:18) at module.exports (/homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/lib/resolve-bindings.js:13:12)
Hi,
I've followed the instructions and updated to the newest version of the plugin and my bluetooth rest won't add to homekit. My wifi rest works fine. Can someone please help?
Thanks!
After configuring Hatch Rest with Name and MAC Address the following error is shown after Homebridge restart.
[6/15/2021, 11:11:43 AM] [HatchBabyRest] Error connecting to API
[6/15/2021, 11:11:43 AM] [HatchBabyRest] Error: EAFNOSUPPORT, Address family not supported by protocol
at new Hci (/homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/lib/hci-socket/hci.js:80:18)
at new NobleBindings (/homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:25:15)
at module.exports (/homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/lib/resolve-bindings.js:13:12)
at Object. (/homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/index.js:2:51)
at Module._compile (internal/modules/cjs/loader.js:1137:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1157:10)
at Module.load (internal/modules/cjs/loader.js:985:32)
at Function.Module._load (internal/modules/cjs/loader.js:878:14)
at Module.require (internal/modules/cjs/loader.js:1025:19)
at require (internal/modules/cjs/helpers.js:72:18) {
errno: 97,
code: 'EAFNOSUPPORT',
syscall: 'socket'
}
Trying to install on a raspberry pi 3 using the command as provided
As well as with root privilege
Both attempts seem to have permission issues with /usr/lib/node_modules/. Any suggestions?
I love the idea of being able to control my rest+ on Homekit but I have deployed HOOBs and everytime I try and go into the advanced configuration in HOOBs and add the platforms entry is fails epically. I get the error
"Unable to save.
Please fix the following errors.
Invalid JSON."
Can you provide some guidance on where I should be adding this in Hoobs or what I have missed here?
Just upgraded to v3 yesterday. I have a Hatch Rest that I had successfully working on v2.
I've set up a Scene to: set the color, track and switch to "on". It will work one time after starting up homebridge then won't connect again.
Seems like it's trying to connect to the device multiple times initially, then just ignores all commands after that:
Feb 09 08:17:00 homebridge homebridge[1656]: [2/9/2021, 8:17:00 AM] [HatchBabyRest] Turning on James Night Light
Feb 09 08:17:00 homebridge homebridge[1656]: [2/9/2021, 8:17:00 AM] [HatchBabyRest] Connecting to Hatch Rest...
Feb 09 08:17:00 homebridge homebridge[1656]: [2/9/2021, 8:17:00 AM] [HatchBabyRest] Connecting to Hatch Rest...
Feb 09 08:17:00 homebridge homebridge[1656]: [2/9/2021, 8:17:00 AM] [HatchBabyRest] Connected to Hatch Rest
Feb 09 08:17:00 homebridge homebridge[1656]: [2/9/2021, 8:17:00 AM] [HatchBabyRest] Connected to Hatch Rest
Feb 09 08:17:06 homebridge homebridge[1656]: [2/9/2021, 8:17:06 AM] [HatchBabyRest] Disconnected from Hatch Rest
Feb 09 08:17:24 homebridge homebridge[1656]: [2/9/2021, 8:17:24 AM] [HatchBabyRest] Turning off James Night Light
Feb 09 08:17:24 homebridge homebridge[1656]: [2/9/2021, 8:17:24 AM] [HatchBabyRest] Connecting to Hatch Rest...
Feb 09 08:19:51 homebridge homebridge[1656]: [2/9/2021, 8:19:51 AM] [HatchBabyRest] Turning on James Night Light
Feb 09 08:19:51 homebridge homebridge[1656]: [2/9/2021, 8:19:51 AM] [HatchBabyRest] Connecting to Hatch Rest...
Feb 09 08:20:26 homebridge homebridge[1656]: [2/9/2021, 8:20:26 AM] [HatchBabyRest] Turning off James Night Light
Feb 09 08:20:26 homebridge homebridge[1656]: [2/9/2021, 8:20:26 AM] [HatchBabyRest] Connecting to Hatch Rest...
Feb 09 08:20:43 homebridge homebridge[1656]: [2/9/2021, 8:20:43 AM] [HatchBabyRest] Turning on James Night Light
Feb 09 08:20:43 homebridge homebridge[1656]: [2/9/2021, 8:20:43 AM] [HatchBabyRest] Connecting to Hatch Rest...
I had it working well with the first gen via bluetooth, but now that I've upgraded to the second gen Hatch Rest, this config seems to have stopped working.
Whenever I update other plugins, I now see this message, and it takes a fair amount of time to complete. I am not well versed with npm, so I am unclear why an unrelated plugin update is causing new binaries to be built for dependencies of this plugin. Any ideas how to avoid this from happening? I am using Docker homebridge, in case that's relevant. Here is an example of what I see when updating another plugin:
> [email protected] install /homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/usb
> prebuild-install --verbose || node-gyp rebuild
prebuild-install info begin Prebuild-install version 5.3.3
prebuild-install info looking for cached prebuild @ /root/.npm/_prebuilds/509042-usb-v1.6.3-node-v72-linuxmusl-arm.tar.gz
prebuild-install http request GET https://github.com/tessel/node-usb/releases/download/v1.6.3/usb-v1.6.3-node-v72-linuxmusl-arm.tar.gz
prebuild-install http 404 https://github.com/tessel/node-usb/releases/download/v1.6.3/usb-v1.6.3-node-v72-linuxmusl-arm.tar.gz
prebuild-install WARN install No prebuilt binaries found (target=12.16.3 runtime=node arch=arm libc=musl platform=linux)
make: Entering directory '/homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/usb/build'
CC(target) Release/obj.target/libusb/libusb/libusb/core.o
I believe I've done everything correctly, but I keep getting the following error on repeat when I launch homebridge: "Failed to reach Hatch Baby server at https://data.hatchbaby.com/public/v1/login. Trying again in 5 seconds..."
I can't tell if this is an error on their side or mine.
I updated to v2.0 of the plugin earlier and started seeing this error. I uninstalled and reinstalled (in the interim I think you rolled back the version to 1.3.1?) and the error still persists. Here is what I am seeing in the log file.
[4/6/2020, 1:48:18 PM] ERROR LOADING PLUGIN homebridge-hatch-baby-rest:
[4/6/2020, 1:48:18 PM] Error: Cannot find module '/homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/binding.node'
Require stack:
- /homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/bluetooth-hci-socket/lib/native.js
- /homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/bluetooth-hci-socket/index.js
- /homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/lib/hci-socket/hci.js
- /homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/lib/hci-socket/bindings.js
- /homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/lib/resolve-bindings.js
- /homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/index.js
- /homebridge/node_modules/homebridge-hatch-baby-rest/lib/hatch-baby-rest.js
- /homebridge/node_modules/homebridge-hatch-baby-rest/lib/accessories/hatch-baby-rest.js
- /homebridge/node_modules/homebridge-hatch-baby-rest/lib/index.js
- /usr/local/lib/node_modules/homebridge/lib/plugin.js
- /usr/local/lib/node_modules/homebridge/lib/server.js
- /usr/local/lib/node_modules/homebridge/lib/cli.js
- /usr/local/lib/node_modules/homebridge/bin/homebridge
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:982:15)
at Function.Module._load (internal/modules/cjs/loader.js:864:27)
at Module.require (internal/modules/cjs/loader.js:1044:19)
at require (internal/modules/cjs/helpers.js:77:18)
at Object.<anonymous> (/homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/bluetooth-hci-socket/lib/native.js:6:15)
at Module._compile (internal/modules/cjs/loader.js:1158:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)
at Module.load (internal/modules/cjs/loader.js:1002:32)
at Function.Module._load (internal/modules/cjs/loader.js:901:14)
at Module.require (internal/modules/cjs/loader.js:1044:19)
at require (internal/modules/cjs/helpers.js:77:18)
at Object.<anonymous> (/homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/bluetooth-hci-socket/index.js:8:20)
at Module._compile (internal/modules/cjs/loader.js:1158:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)
at Module.load (internal/modules/cjs/loader.js:1002:32)
at Function.Module._load (internal/modules/cjs/loader.js:901:14)
at Module.require (internal/modules/cjs/loader.js:1044:19)
at require (internal/modules/cjs/helpers.js:77:18)
at Object.<anonymous> (/homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/lib/hci-socket/hci.js:6:28)
at Module._compile (internal/modules/cjs/loader.js:1158:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)
at Module.load (internal/modules/cjs/loader.js:1002:32)
[4/6/2020, 1:48:18 PM] ====================
I'm using an old Mac Mini as a server for Homebridge. The OS is Yosemite. It's working fine with Homebridge and other plugins, but I keep getting an error with the Hatch Baby Rest plugin. Here is an excerpt from the error log:
2301 error errno 1
2302 error @abandonware/[email protected] install: `node-gyp rebuild`
2302 error Exit status 1
2303 error Failed at the @abandonware/[email protected] install script.
2303 error This is probably not a problem with npm. There is likely additional logging output above.
2304 verbose exit [ 1, true ]
I tried a manual install with npm i -g homebridge-hatch-baby-rest in terminal and am running into the same problems.
Hey, thanks for making this awesome library. I don't have Homekit stuff, but I'm trying to use your HatchBabyApi as a client for the API to do some automation. I'm hoping to implement a gradual volume fade over a certain period of time. Just being able to turn it on / off would be nice too.
I've got your Rest Plus example working. But now I'm trying to add in a statement to adjust the volume:
async function example() {
light.onBrightness.subscribe((i) => console.log("Brightness", i));
light.onVolume.subscribe((i) => console.log("Volume", i));
light.onIsPowered.subscribe((i) => console.log("Is Powered", i));
light.onAudioTrack.subscribe((i) => console.log("Audio Track", i));
light.onBatteryLevel.subscribe((i) => console.log("Battery", i));
light.setVolume(25);
}and getting:
Unable to Update {Hatch Name} - No MQTT Client Registered
Since reading the API works, I'm guessing I'm just not doing this in an async way. I also notice that these error log message happens before the console logging. I see that the client gets created in the getDevices call. Is there something I need to wrap the setVolume / update call in to make it run only once the client is initiated?
Sorry if this is a very basic question. I never really got the hang of async and promises.
Since the latest update - my hatch devices (Rest+ & Restore) are ignoring (or not recieving) HB commands. A simple reboot of the Hb instance restores functionality.
Both devices have a static IP and for some reason in a rollback of a previous version of the plugin seems to maintain stability although 3.2.3 only updated dependancies.
I've recently stood up a Synology NAS with Homebridge installed to assist me to explose devices that are not natively supported by HomeKit.
I've successfully installed other plugins, however, when it comes to this plugin (homebridge-hatch-baby-rest), I get the following error message:
USER: homebridge
DIR: /volume1/@appdata/homebridge
CMD: npm install -g homebridge-hatch-baby-rest@latest
npm ERR! code 1
npm ERR! path /volume1/@appdata/homebridge/lib/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble
npm ERR! command failed
npm ERR! command sh -c node-gyp rebuild
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using [email protected]
npm ERR! gyp info using [email protected] | linux | x64
npm ERR! gyp info find Python using Python version 3.8.8 found at "/usr/bin/python3.8"
npm ERR! gyp info spawn /usr/bin/python3.8
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args '/volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
npm ERR! gyp info spawn args 'binding.gyp',
npm ERR! gyp info spawn args '-f',
npm ERR! gyp info spawn args 'make',
npm ERR! gyp info spawn args '-I',
npm ERR! gyp info spawn args '/volume1/@appdata/homebridge/lib/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/build/config.gypi',
npm ERR! gyp info spawn args '-I',
npm ERR! gyp info spawn args '/volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
npm ERR! gyp info spawn args '-I',
npm ERR! gyp info spawn args '/var/packages/homebridge/home/.cache/node-gyp/16.13.2/include/node/common.gypi',
npm ERR! gyp info spawn args '-Dlibrary=shared_library',
npm ERR! gyp info spawn args '-Dvisibility=default',
npm ERR! gyp info spawn args '-Dnode_root_dir=/var/packages/homebridge/home/.cache/node-gyp/16.13.2',
npm ERR! gyp info spawn args '-Dnode_gyp_dir=/volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/node-gyp',
npm ERR! gyp info spawn args '-Dnode_lib_file=/var/packages/homebridge/home/.cache/node-gyp/16.13.2/<(target_arch)/node.lib',
npm ERR! gyp info spawn args '-Dmodule_root_dir=/volume1/@appdata/homebridge/lib/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble',
npm ERR! gyp info spawn args '-Dnode_engine=v8',
npm ERR! gyp info spawn args '--depth=.',
npm ERR! gyp info spawn args '--no-parallel',
npm ERR! gyp info spawn args '--generator-output',
npm ERR! gyp info spawn args 'build',
npm ERR! gyp info spawn args '-Goutput_dir=.'
npm ERR! gyp info spawn args ]
npm ERR! gyp ERR! build error
npm ERR! gyp ERR! stack Error: not found: make
npm ERR! gyp ERR! stack at getNotFoundError (/volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/which/which.js:10:17)
npm ERR! gyp ERR! stack at /volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/which/which.js:57:18
npm ERR! gyp ERR! stack at new Promise ()
npm ERR! gyp ERR! stack at step (/volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/which/which.js:54:21)
npm ERR! gyp ERR! stack at /volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/which/which.js:71:22
npm ERR! gyp ERR! stack at new Promise ()
npm ERR! gyp ERR! stack at subStep (/volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/which/which.js:69:33)
npm ERR! gyp ERR! stack at /volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/which/which.js:80:22
npm ERR! gyp ERR! stack at /volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/isexe/index.js:42:5
npm ERR! gyp ERR! stack at /volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/isexe/mode.js:8:5
npm ERR! gyp ERR! System Linux 4.4.180+
npm ERR! gyp ERR! command "/volume1/@appstore/homebridge/app/bin/node" "/volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
npm ERR! gyp ERR! cwd /volume1/@appdata/homebridge/lib/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble
npm ERR! gyp ERR! node -v v16.13.2
npm ERR! gyp ERR! node-gyp -v v8.3.0
npm ERR! gyp ERR! not ok
npm ERR! A complete log of this run can be found in:
npm ERR! /var/packages/homebridge/home/.npm/_logs/2022-03-09T16_03_17_609Z-debug.log
Command failed. Please review log for details.
Has anyone else experienced this? Apologies if this is a duplicate topic, I wasn't able to find the same issue in other topics.
Thanks!
Does this also support the Rest+ if I add the WiFi MAC?
Thank you for creating this plugin!
I'm having an issue connecting to the Hatch itself. I'm running homebridge on a RP4. I have the first Hatch with only bluetooth. I will get the following commands on startup..
[10/23/2020, 11:41:15] [*** Hatch] Initializing HatchBabyRest accessory...
[10/23/2020, 11:41:15] [*** Hatch] Waiting for bluetooth to power on
[10/23/2020, 11:41:17] [*** Hatch] Scanning for device
It stops there. It will show the command "Turning on" and "Turning off", but nothing is happening since it does not say "connected" like I saw you mention in another closed issue.
I'm also running into this problem..
pi@homebridge:/var/lib/homebridge $ sudo setcap cap_net_raw+eip $(eval readlink -f which node)
unable to set CAP_SETFCAP effective capability: Operation not permitted
I've been searching and cannot figure out how to allow permission for setcap.
Any solutions you can think of?
Hi, I'd like to see if I can get a bit of assistance. I have 2 original Hatch Rest lights and have gone through the setup procedure. I have added 1 of the units into the config with the mac I have set it up with 50% audio default light color and stream as the "audio track". When I go to turn the accessory on I can see it status that the device is recognized then it connects and after approx. 1-3 seconds it disconnects but nothing is happening with the Hatch....
Here is the log after restart and trying to power on the Hatch. (MAC shows in log but I have removed it here)
[1/9/2021, 9:44:06 AM] [HB Supervisor] Starting Homebridge with extra flags: -I
[1/9/2021, 9:44:06 AM] [HB Supervisor] Started Homebridge v1.1.7 with PID: 3532
[1/9/2021, 9:44:06 AM] Loaded config.json with 1 accessories and 1 platforms.
[1/9/2021, 9:44:06 AM] ---
[1/9/2021, 9:44:06 AM] Loaded plugin: [email protected]
[1/9/2021, 9:44:06 AM] Registering platform 'homebridge-config-ui-x.config'
[1/9/2021, 9:44:06 AM] ---
[1/9/2021, 9:44:07 AM] Loaded plugin: [email protected]
[1/9/2021, 9:44:07 AM] Registering accessory 'homebridge-hatch-baby-rest.HatchBabyRest'
[1/9/2021, 9:44:07 AM] Registering platform 'homebridge-hatch-baby-rest.HatchBabyRest'
[1/9/2021, 9:44:07 AM] ---
[1/9/2021, 9:44:07 AM] Loading 1 platforms...
[1/9/2021, 9:44:07 AM] [Config] Initializing config platform...
[1/9/2021, 9:44:07 AM] [Config] Running in Service Mode
[1/9/2021, 9:44:07 AM] Loading 1 accessories...
[1/9/2021, 9:44:07 AM] [Bishop's Room] Initializing HatchBabyRest accessory...
[1/9/2021, 9:44:07 AM] [Bishop's Room] Waiting for bluetooth to power on
[1/9/2021, 9:44:07 AM] Homebridge is running on port 51143.
[1/9/2021, 9:44:07 AM] [Bishop's Room] Scanning for device
[1/9/2021, 9:44:09 AM] [Bishop's Room] Found device Bishop’s Room with address :
[1/9/2021, 9:48:00 AM] [Bishop's Room] Turning on
[1/9/2021, 9:48:00 AM] [Bishop's Room] Connecting to Bishop’s Room...
[1/9/2021, 9:48:02 AM] [Bishop's Room] Connected to Bishop’s Room
[1/9/2021, 9:48:07 AM] [Bishop's Room] Disconnected from Bishop’s Room
Is it possible to extend this plugin to work with the hatch restore?
Hi!
Im really excited about this plug in! I have a rest and a rest+ that will be so nice to have in homekit. I keep getting an error though when I go to install that I would love some help with.. Below is what happens in terminal
Do I need to have code on the mac for this to work?
sethbarstow@GC-Audio ~ % npm i -g homebridge-hatch-baby-rest-volume
@abandonware/[email protected] install /usr/local/lib/node_modules/homebridge-hatch-baby-rest-volume/node_modules/@abandonware/noble
node-gyp rebuild
No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.
No receipt for 'com.apple.pkg.DeveloperToolsCLILeo' found at '/'.
No receipt for 'com.apple.pkg.DeveloperToolsCLI' found at '/'.
gyp: No Xcode or CLT version detected!
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)
gyp ERR! stack at ChildProcess.emit (events.js:315:20)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)
gyp ERR! System Darwin 19.6.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/local/lib/node_modules/homebridge-hatch-baby-rest-volume/node_modules/@abandonware/noble
gyp ERR! node -v v14.15.3
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @abandonware/bluetooth-hci-socket@^0.5.3-5 (node_modules/homebridge-hatch-baby-rest-volume/node_modules/@abandonware/noble/node_modules/@abandonware/bluetooth-hci-socket):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @abandonware/[email protected]: wanted {"os":"linux,android,freebsd,win32","arch":"any"} (current: {"os":"darwin","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @abandonware/[email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @abandonware/[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! /Users/sethbarstow/.npm/_logs/2020-12-21T22_25_43_865Z-debug.log
sethbarstow@GC-Audio ~ %
Should the Master On/Off Switch successfully turn off the device when toggled to Off if both the Light & Fan accessories were enabled by toggling it on?
Is this a known issue with the Bluetooth only Rest?
I installed v2.0.4, configured it through Homebridge UI and after Homebridge restarted it won't boot back up because of the error below:
Error: EAFNOSUPPORT, Address family not supported by protocol
at new Hci (/homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/lib/hci-socket/h
ci.js:74:18)
at new NobleBindings (/homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/lib/hc
i-socket/bindings.js:25:15)
at Object.<anonymous> (/homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/lib/h
ci-socket/bindings.js:546:18)
at Module._compile (internal/modules/cjs/loader.js:1133:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)
at Module.load (internal/modules/cjs/loader.js:977:32)
at Function.Module._load (internal/modules/cjs/loader.js:877:14)
at Module.require (internal/modules/cjs/loader.js:1019:19)
at require (internal/modules/cjs/helpers.js:77:18)
at module.exports (/homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/lib/resol
ve-bindings.js:13:12)
at Object.<anonymous> (/homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/index
.js:2:49)
at Module._compile (internal/modules/cjs/loader.js:1133:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)
at Module.load (internal/modules/cjs/loader.js:977:32)
at Function.Module._load (internal/modules/cjs/loader.js:877:14)
at Module.require (internal/modules/cjs/loader.js:1019:19)
at require (internal/modules/cjs/helpers.js:77:18)
at new HatchBabyRest (/homebridge/node_modules/homebridge-hatch-baby-rest/lib/hatch-baby-rest.js:30:22)
at new HatchBabyRestAccessory (/homebridge/node_modules/homebridge-hatch-baby-rest/lib/accessories/hatch-baby-re
st.js:20:20)
at /usr/local/lib/node_modules/homebridge/src/server.ts:357:50
at Array.forEach (<anonymous>)
at Server._loadAccessories (/usr/local/lib/node_modules/homebridge/src
I didn't realize that I disabled bluetooth on my RPi and when I went to run this plugin it crashed Homebridge:
[2/23/2021, 7:15:01 PM] [HatchBabyRest] Waiting for bluetooth to power on (node:15389) UnhandledPromiseRejectionWarning: Error: ENODEV, No such device at Hci.init (/usr/local/lib/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/lib/hci-socket/hci.js:114:35) at NobleBindings.init (/usr/local/lib/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:82:13) at Noble.get (/usr/local/lib/node_modules/homebridge-hatch-baby-rest/node_modules/@abandonware/noble/lib/noble.js:72:26) at HatchBabyRest.<anonymous> (/usr/local/lib/node_modules/homebridge-hatch-baby-rest/lib/hatch-baby-rest.js:68:56) at Generator.next (<anonymous>) at /usr/local/lib/node_modules/homebridge-hatch-baby-rest/lib/hatch-baby-rest.js:13:71 at new Promise (<anonymous>) at __awaiter (/usr/local/lib/node_modules/homebridge-hatch-baby-rest/lib/hatch-baby-rest.js:9:12) at HatchBabyRest.getPeripheralByAddress (/usr/local/lib/node_modules/homebridge-hatch-baby-rest/lib/hatch-baby-rest.js:65:16) at new HatchBabyRest (/usr/local/lib/node_modules/homebridge-hatch-baby-rest/lib/hatch-baby-rest.js:31:39) (Use node --trace-warnings ...to show where the warning was created) (node:15389) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag--unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
As a stop gap until a Python version can be made, I want to use Homebridge --> HomeAssistant (via HomeKit Controller component). But, HomeAssistant cannot handle accessories without a serial number/unique identifier specified (currently set to Unknown). See this issue for same concern with another Homebridge plugin.
Can the MAC address (or some other stable identifier) be used for the serial number?
Can you add a checkbox for not deploying the additional accessories? I've only found use of the master switch so far.
config.schema.json
"includeExtraAccessories": {
"title": "Include Extra Accessories",
"type": "boolean",
"description": "Include Soundtrack Fan, Volume, and Light Accessories (where applicable)",
"placeholder": "zInclude Extra Accessories",
"default": "true",
"oneOf": [
{ "title": "Yes", "enum": ["true"] },
{ "title": "No", "enum": ["false"] }
],
"required": false
},
was planning a PR but wasn't sure where to implement in platform.ts - maybe lines 105:115?
Or maybe you could help me customize out the extra accessories?
I updated my HomeBridge Node to v16.13.1 and filled the HB Node upgrade guide but it could not recompile the Rest plugin and generates the following error on load.
[1/3/2022, 3:48:24 PM] [homebridge-hatch-baby-rest] Configuring 0 Rest, 1 Rest+, 0 Rest Mini, and 1 Restore Devices
(node:81434) [node-fetch#buffer] DeprecationWarning: Please use 'response.arrayBuffer()' instead of 'response.buffer()'
(Use node --trace-deprecation ... to show where the warning was created)
@dgreif THANK YOU so much for making this homebridge plugin! I've been waiting since earlier this year for someone smarter than me to figure out how to do a plugin for the hatch baby rest
I was able to add the config, and it shows up in my home app. When I tap to turn on/off the button on the home app changes on/off, the logs on homebridge show like this:
[11/24/2019, 12:22:10 AM] [Hatch Baby Rest] Turning on
[11/24/2019, 12:22:15 AM] [Hatch Baby Rest] Turning off
[11/24/2019, 12:22:18 AM] [Hatch Baby Rest] Turning on
[11/24/2019, 12:22:24 AM] [Hatch Baby Rest] Turning off
[11/24/2019, 12:22:24 AM] [Hatch Baby Rest] Turning on
[11/24/2019, 12:22:26 AM] [Hatch Baby Rest] Turning off
yet the hatch baby rest is not changing state (it keeps on if it was on, or keeps off if it was off)
Homebridge is running in a raspberry pi 3 b+, homebridge config includes volume, audioTrack, color, and my unit's MAC address, and I got the older hatch baby rest (not the newer one with wifi)
Any insights of what could be going wrong, or what else can I check?
Thank you so much again!
I work for Hatch, and I wanted to report some bugs that apparently are coming from your plugin.
You have one user that is stuck in an endless loop issuing requests to /public/v1/login every 5 seconds. Their client has issued almost 500,000 requests in the last 10 days! Interestingly, the logins are successful, not failure. I cannot see in the code where this error might be coming from, but I don't know about homebridge.
Ps, if you want assistance with the APIs, I can offer help, although it certainly looks like you've reverse engineered most of them!
Hi,
I installed the plug in for my hatch baby rest, and it successfully loaded into my apple home app, but it doesn't actually turn the nightlight on. This is for my bluetooth night light, and I also have a wifi rest+ and when I try to paste the code in terminal I receive the below error. Can someone please give me some guidance? Thanks!
bash: platforms:: command not found
bash: platform:: command not found
bash: email:: command not found
bash: password:: command not found
bash: ]: command not found
Hi @dgreif ,
First off, sorry, I know this is not the right place for this question, but I could not find another way to contact you. Second, great work on this project! I don't actually use homebridge, but I love working on Amazon IOT platform and home automation.
I am actually wondering if you have any additional details on the HatchBaby API. I'd like to write some code to pull my baby's stats and plot things in Google Docs to find trends like certain times of the day our little one eats more than other times. I can export the data from the app, but I have to manually do that every time I want to update my stats, so I'm hoping to find an API to pull the data. I stumbled upon your project in my search. How did you find details about the API to control the Rest+? Is there Swagger docs or similar for the HatchBaby API? I'm hoping if they have the Rest+ API they might have API to get my data stored in the platform as well.
If I can find the time, I think I'll also setup a custom Alexa smart skill for my Rest+ so that it shows up as a normal Alexa smart device. I'm not sure why HatchBaby didn't do that to begin with. I hate having to say "Alexa, tell hatchbaby too..." instead of just "Alexa turn on rest". Also I'd like to add the Rest+ to some routines :)
If you'd prefer to chat over email, shoot me an email using my git-hub username + @gmail.com
Thanks for your time and contributions to the community!
I am trying to get this working on Homebridge on a Windows 10 machine. I was able to add the device to Homekit, but when I turn it off an on from within Homekit, nothing actually happens. Looking at the Homebridge logs, I get the following error each time:
UnhandledPromiseRejectionWarning: Error: No compatible USB Bluetooth 4.0 device found!
at BluetoothHciSocket.bindUser
at BluetoothHciSocket.bindRaw
at Hci.init
at NobleBindings.init
at Noble.get
at HatchBabyRest.
at Generator.next
etc...
I have a bluetooth 4.0 compatible adapter in my PC, so I'm not sure what to think of that error message. Any ideas?
Regarding the Lightbulb service representing the light function on a Hatch Rest+:
If I set the color to "none" within the Hatch app, the HomeKit status is displayed as white (RGB = 255, 255, 255) color and retains previous brightness value even though the light on the physical Rest+ is turned off.
Can this be fixed to show the lightbulb as "off" when the "none" color option is selected within the Hatch app?
Any suggestions as to how to fix the "Waiting for bluetooth to power on" I'm seeing when starting HomeBridge. I see:
[Homebridge] [12/12/2019, 15:29:50] [Bedtime] Initializing HatchBabyRest accessory...
[Homebridge] [12/12/2019, 15:29:50] [Bedtime] Waiting for bluetooth to power on
I'm running on supported hardware, config is done correctly and Bluetooth is running on my Pi, but I cannot seem to get this to connect.
(As an aside, thank you for this!). Been waiting for almost a year for somebody smarter than me to get this up and running.
Great work on the Homebridge plugin, I'd love to get this into Home Assistant as well. Have you considered making a Python API for the Rest/Rest+? I could help with the Home Assistant integration side of it.
I tried both through the config UI X and just doing it in the command line but get the same result. Is there some sort of dependency that's failing? Let me know if there's anything I can do on my end, or if you need any of the actual log.
I have a wifi Rest+ and able to get this working when first installed, but after about a couple days, it stops working. I have to remove the plugin and re-add it for it to work again. Looking at the logs, I get the following error:
[5/2/2020, 9:21:23 PM] [HatchBabyRest] AWS Iot Error
[5/2/2020, 9:21:23 PM] [HatchBabyRest] Error: unexpected server response (403)
at ClientRequest. (/usr/lib/node_modules/homebridge-hatch-baby-rest/node_modules/ws/lib/WebSocket.js:653:21)
at ClientRequest.emit (events.js:210:5)
at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:583:27)
at HTTPParser.parserOnHeadersComplete (_http_common.js:115:17)
at TLSSocket.socketOnData (_http_client.js:456:22)
at TLSSocket.emit (events.js:210:5)
at addChunk (_stream_readable.js:309:12)
at readableAddChunk (_stream_readable.js:290:11)
at TLSSocket.Readable.push (_stream_readable.js:224:10)
at TLSWrap.onStreamRead (internal/stream_base_commons.js:182:23) {
type: 'error',
target: WebSocket {
_events: [Object: null prototype] {},
_eventsCount: 0,
_maxListeners: undefined,
readyState: 3,
bytesReceived: 0,
extensions: null,
protocol: '',
_binaryType: 'arraybuffer',
_finalize: [Function: bound finalize],
_closeFrameReceived: false,
_closeFrameSent: false,
_closeMessage: '',
_closeTimer: null,
_finalized: true,
_closeCode: 1006,
_receiver: null,
_sender: null,
_socket: null,
_ultron: null,
protocolVersion: 13,
_isServer: false,
url: 'wss://aacsjje0gbbcc-ats.iot.us-west-2.amazonaws.com/mqtt?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=ASIA6CHTNMDRBER6EUNJ%2F20200503%2Fus-west-2%2Fiotdevicegateway%2Faws4_request&X-Amz-Date=20200503T022123Z&X-Amz-SignedHeaders=host&X-Amz-Signature=25199f56d7db433e4dcea7eb2a8a7d1be868442f4747ce31f5e5d33b99487541&X-Amz-Security-Token='[OMITTED]',
_req: ClientRequest {
_events: [Object: null prototype],
_eventsCount: 4,
_maxListeners: undefined,
outputData: [],
outputSize: 0,
writable: true,
_last: true,
chunkedEncoding: false,
shouldKeepAlive: true,
useChunkedEncodingByDefault: false,
sendDate: false,
_removedConnection: false,
_removedContLen: false,
_removedTE: false,
_contentLength: 0,
_hasBody: true,
_trailer: '',
finished: true,
_headerSent: true,
socket: [TLSSocket],
connection: [TLSSocket],
_header: 'GET /mqtt?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=[OMITTED]us-west-2%2Fiotdevicegateway%2Faws4_request&X-Amz-Date=20200503T022123Z&X-Amz-SignedHeaders=host&X-Amz-Signature=25199f56d7db433e4dcea7eb2a8a7d1be868442f4747ce31f5e5d33b99487541&X-Amz-Security-Token=[OMITTED]
'Sec-WebSocket-Version: 13\r\n' +
'Sec-WebSocket-Key: 2R9F4Ja3MZsy0shSz8p8/g==\r\n' +
'Connection: Upgrade\r\n' +
'Upgrade: websocket\r\n' +
'Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits\r\n' +
'Sec-WebSocket-Protocol: mqttv3.1\r\n' +
'Host: aacsjje0gbbcc-ats.iot.us-west-2.amazonaws.com\r\n' +
'\r\n',
_onPendingData: [Function: noopPendingOutput],
agent: [Agent],
socketPath: undefined,
method: 'GET',
path: '/mqtt?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=[OMITTED]us-west-2%2Fiotdevicegateway%2Faws4_request&X-Amz-Date=20200503T022123Z&X-Amz-SignedHeaders=host&X-Amz-Signature=25199f56d7db433e4dcea7eb2a8a7d1be868442f4747ce31f5e5d33b99487541&X-Amz-Security-Token=[OMITTED],
_ended: false,
res: [IncomingMessage],
aborted: true,
timeoutCb: null,
upgradeOrConnect: false,
parser: null,
maxHeadersCount: null,
[Symbol(kNeedDrain)]: false,
[Symbol(isCorked)]: false,
[Symbol(kOutHeaders)]: [Object: null prototype]
}
}
}
Stops at scanning for device... pretty sure it’s a permissions issue like others have had but previous solutions aren’t helping I am running on a Mac mini...
Initially glance seems that "setTargetState" works fine but there's some bug with "getCurrentState" or "getTargetState" and multiple Rest+ devices.
I'm guessing that there's not many of us with multiple Rest+ so I'll be happy to test for you if needed.
I'm using this Homebridge in conjunction with Home Assistant to control my two Hatch Rest+ sound machines. Everything all of the devices and entities import into Home Assistant with the exception of volume control. Are there any plans to update to include volume control that would be compatible with Home Assistant? I have tried homebridge-hatch-baby-rest-volume plugin (a fork from this repository), however, it has not been updated and I am experience an issue only one device being imported and linked to the incorrect devices (explanation of issue here: home-assistant/core#50811). Thank you for creating this very useful plugin.
I have config.json setup and connects successfully:
"accessories": [
{
"accessory": "HatchBabyRest",
"name": "Charlie & Teddy",
"macAddress": "12:34:56:78:90:11",
"volume": 25,
"audioTrack": 3,
"color": { "r": 0, "g": 0, "b": 255, "a": 128 }
}
]
but get:
[12/15/2019, 11:27:44 PM] Homebridge is running on port 51826.
[12/15/2019, 11:27:44 PM] [C] Scanning for device
[12/15/2019, 11:28:55 PM] [C] Turning on
[12/15/2019, 11:28:57 PM] [C] Turning on
[12/15/2019, 11:29:00 PM] [C] Turning on
appears to be running correctly on my MacBook Pro (Retina, Mid 2012) but the turn on/off doesn't do anything.
using iphone 11, latest iOS, with the original Hatch Baby Rest. I have two of them and would love to setup automation and control from homekit with your code.
Any thoughts?
I have found that I am often getting into a state where the Rest+ stops responding to any commands from homekit (on/off, brightness, color change).
Looking at the logs, I see the following error when this occurs:
[3/5/2020, 1:08:32 AM] [HatchBabyRest] AWS Iot Error
[3/5/2020, 1:08:32 AM] [HatchBabyRest] Error: unexpected server response (403)
at ClientRequest.<anonymous> (/homebridge/node_modules/homebridge-hatch-baby-rest/node_modules/ws/lib/WebSocket.js:653:21)
at ClientRequest.emit (events.js:323:22)
at ClientRequest.EventEmitter.emit (domain.js:482:12)
at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:603:27)
at HTTPParser.parserOnHeadersComplete (_http_common.js:119:17)
at TLSSocket.socketOnData (_http_client.js:476:22)
at TLSSocket.emit (events.js:311:20)
at TLSSocket.EventEmitter.emit (domain.js:482:12)
at addChunk (_stream_readable.js:294:12)
at readableAddChunk (_stream_readable.js:275:11)
at TLSSocket.Readable.push (_stream_readable.js:209:10)
at TLSWrap.onStreamRead (internal/stream_base_commons.js:186:23) {
type: 'error',
target: WebSocket {
_events: [Object: null prototype] {},
_eventsCount: 0,
_maxListeners: undefined,
readyState: 3,
bytesReceived: 0,
extensions: null,
protocol: '',
_binaryType: 'arraybuffer',
_finalize: [Function: bound finalize],
_closeFrameReceived: false,
_closeFrameSent: false,
_closeMessage: '',
_closeTimer: null,
_finalized: true,
_closeCode: 1006,
_receiver: null,
_sender: null,
_socket: null,
_ultron: null,
protocolVersion: 13,
_isServer: false,
url: [*redacted*]
_req: ClientRequest {
_events: [Object: null prototype],
_eventsCount: 4,
_maxListeners: undefined,
outputData: [],
outputSize: 0,
writable: true,
_last: true,
chunkedEncoding: false,
shouldKeepAlive: true,
useChunkedEncodingByDefault: false,
sendDate: false,
_removedConnection: false,
_removedContLen: false,
_removedTE: false,
_contentLength: 0,
_hasBody: true,
_trailer: '',
finished: true,
_headerSent: true,
socket: [TLSSocket],
connection: [TLSSocket],
_header: [*redacted*]
_onPendingData: [Function: noopPendingOutput],
agent: [Agent],
socketPath: undefined,
method: 'GET',
insecureHTTPParser: undefined,
path: [*redacted*]
_ended: false,
res: [IncomingMessage],
aborted: true,
timeoutCb: null,
upgradeOrConnect: false,
parser: null,
maxHeadersCount: null,
reusedSocket: false,
[Symbol(kCapture)]: false,
[Symbol(kNeedDrain)]: false,
[Symbol(corked)]: 0,
[Symbol(kOutHeaders)]: [Object: null prototype]
},
[Symbol(kCapture)]: false
}
}
It appears that the only way to clear the issue when it occurs is to restart homebridge.
Hi there,
Thank you for your work on this plugin, I've been finding it very useful. I was just wondering if it would be possible to just expose a simple On/Off switch for each of my Hatch Sound Machines connected. They are already configured, I just want to be able to turn them on and off in HomeKit and to not see any of the other settings.
Thank you!
I have two Hatch devices, is it possible to hide one of them?
Wonder if you could look into doing this? This way you could actually provide named inputs for the sounds.
Hi, just wondering if you had looked into integrating this into Home Assistant? I'm most interested in integrating your Rest bluetooth library and integrating it into ESPHome such that an ESP32 could be used as the interface between the Rest and Home Assistant.
I first found about your project on the Home Assistant Forum, Hatch Baby Rest+, Home Assistant Forum
Would be nice if we could hide specific accessories like the fan.
We use our Rest lights in a sleep/wake configuration where the light is red + sound during the night, and green w/ no sound in the morning when it is time to wake.
I've attempted to set this up via configuring the light as two accessories but I'm not sure the plugin is handling this well. In the logs, when I attempt to turn on the 'wake' accessory for instance, I see entries for connecting to both the 'sleep' and 'wake' accessory. I'd guess because they share a mac address.
Curious if there is a supported method for using this plugin with a sleep/wake type configuration? If not, I may try and hack it in myself if you would be interested.
Completely ignorant is how to actually code it, but couldn't this device just act like a always-on LED strip (or at least the BR Rest, which we have one of). The power on could set it to a certain state, you could push hue variables, brightness variables, and the sound on and off could simply be controlled by a separate switch or "light" for on/off and volume?
Not sure how it's done in homebridge-adb, but it's able to define "inputs" and execute specific commands based them.
Can you, for the 11+off sound tracks, implement this kind of device, instead of a fan?
I've updated to 3.0 to get the ability to use as a wake light.
I did have one question though. Is it expected that the Home app or homebridge will sync its config with the actual state of the device at any point? I've configured the device with the plugin, then turned it to a favorite via the ring as I put my child in the crib but Home/homebridge still shows what I had set it to prior. I'm not sure if this is expected or not. The behavior is correct with regard to the plugin and homebridge not overriding my manual adjustment.
If not expected would it be possible to have this feature, configurable setting for how often it should sync?
Device: bluetooth
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.