-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Devices are not shown at homebridge #14
Comments
Same issue here. I feel like I missed something during installation. |
i have the same issue… It seems it does not detect any devices. (only 1, but is doesn't appear) I already reset room in the Teufel App - but no changes. I'm also grateful for any advice. Settings in Homebridge:{ Settings in Teufel RaumfeldLog-File from Homebridge:
|
In my current setup, I have one speaker per room. Could you try, just for testing, to place one speaker per room. So create 2 additional rooms and place 1 speaker in each room. At the moment I can not reproduce the issue, but I see, that many people see this behavior... |
I have 2 rooms with one speaker each. Its not working unfortunately... |
I have in total 3 rooms with one device each. 1x teufel Connect, 1xteufel connect, 1 x teufel oneS |
I will create a new debug version tomorrow, to investigate. |
@maxrad-nobrain Everything correct, the plugin should be almost auto-configured. Nothing todo for installation, instead of adding minimum 2 lines to config.json. Everyhing else should happen "magically" :) . Sadly not for you...
|
Could you please try the following:
|
Sorry for the dumb question, but how do I install this specific branch? Can I somehow do it via the homebridge ui? Do I have to remove my current teufel plugin beforehand? |
i copied the git repository~/node_modules/homebridge-teufel $ ls -l i restarted homebrige, here is the log[4/13/2020, 9:04:04 PM] [Config] Homebridge restart request received i changed things in teufel app, after the reset: |
@Tscheggi Line 40 in cc28558
but I don´t see it in your logs. This could mean 2 things:
Could you please double check for problem 1) ? See also below, new version released for easier debugging @maxrad-nobrain |
Hello, Started Node.js HomeKit Server. Or enter this code with your HomeKit app on your iOS device to pair with Homebridge:
[4/14/2020, 8:47:23 AM] [Teufel] ******* ISSUE 14 DEBUG: didFinishLaunching |
Thanks, could you please try to change something in your room configuration in the Teufel app, while having the log open? Please post any entry with [Teufel] ******* ISSUE 14 in it here, while doing this confguration changes... Thanks |
Hello, I renamed some rooms, than I delted one room, created a new room with a different name and added my device Teufel One S. |
In Raumserver, there is the event "zoneConfigurationChanged", which this plugin is build upon. Without this event, this plugin does not work. It seems that this event is not fired in your case. I will try to check out why, but as this is a Raumserver event, it may not be fixable by me. |
Thanks for you support. Unfortunately still not working for me as well. Nothing else... One question my platform "Config" (from homebridge) is set on port 8083. Is this causing a problem as Raumserver is working on port 8080? My Homebridge plugin itself is set n port: 51826 |
Could you try the following and post the log here in your homebridge directory?
if you see "address already in use :::8080", stop homebridge and try again. |
@maxrad-nobrain : Is it possible to change homebridge to 8080 and try again? Raumserver itself is communicating to Teufel on the port homebridge is running on. This may be an issue... |
info: [Raumserver] Welcome to raumserver v0.1.9 (raumkernel v1.2.22) |
[4/14/2020, 11:24:01 AM] [Config] Changes to config.json saved. |
Maybe I misunderstand something (story complete newbie here), but when I connect to my pi and open the node_modules folder I don't even have the teufel-homebridge folder. |
changing to the homebrdige config ui platform to port 8080 did not help btw |
@maxrad-nobrain : So your Teufel devices show up, when Port is changed to 8080? Everything fine? |
I may have the same issue as homebrdge is running on port 8081 cause shelly needs port 8080. I will see how I can change this. |
so my Homebridge is now running on port 8080, and the Homebridge Config UI X on port 8085. But still no Devices in Home APP when i do changes in Raumfeld App, the log shows following:
and after some time additional:
Thanks for your Support, it's very kind |
Changed in the meantime the Homebridge to port 8080 and UI to 8085. i@raspberrypi:/usr/local/lib/node_modules/homebridge-teufel/node_modules/node-raumserver $ npm start
info: [Raumserver] Welcome to raumserver v0.1.9 (raumkernel v1.2.22) |
changed Port of homebridge back 51826
info: [Raumserver] Welcome to raumserver v0.1.9 (raumkernel v1.2.22) |
No, no devices showing up. No change in comparison to previous port setup. Sorry :( |
I could not find any problem. I may need to rewrite the plugin, so you can add raumfeld speaker manually. But this will be a lot of work. Not sure when I will be able to do this |
Could you please test the new version, if the problem is fixed for you? Thanks |
It works :) |
Hello devices are not Popping up in Homebridge.
It seems it does not detect any devices.
I already reset room in the Teufel App - but no changes.
I am grateful for any advice.
Some information from the Log:
Started Node.js HomeKit Server.
[3/19/2020, 4:10:56 PM] Loaded config.json with 0 accessories and 4 platforms.
[3/19/2020, 4:10:56 PM] ---
[3/19/2020, 4:10:56 PM] Loaded plugin: homebridge-config-ui-x
[3/19/2020, 4:10:56 PM] Registering platform 'homebridge-config-ui-x.config'
[3/19/2020, 4:10:56 PM] ---
[3/19/2020, 4:10:56 PM] Loaded plugin: homebridge-shelly
[3/19/2020, 4:10:57 PM] Registering platform 'homebridge-shelly.Shelly'
[3/19/2020, 4:10:57 PM] ---
[3/19/2020, 4:10:59 PM] Loaded plugin: homebridge-teufel
[3/19/2020, 4:10:59 PM] Registering platform 'homebridge-teufel.Teufel'
[3/19/2020, 4:10:59 PM] ---
[3/19/2020, 4:10:59 PM] Loaded plugin: homebridge-tplink-smarthome
[3/19/2020, 4:10:59 PM] Registering platform 'homebridge-tplink-smarthome.TplinkSmarthome'
[3/19/2020, 4:10:59 PM] ---
[3/19/2020, 4:10:59 PM] Loading 4 platforms...
[3/19/2020, 4:10:59 PM] [Config] Initializing config platform...
[3/19/2020, 4:10:59 PM] [Config] Spawning homebridge-config-ui-x with PID 780
[3/19/2020, 4:10:59 PM] [Shelly] Initializing Shelly platform...
[3/19/2020, 4:10:59 PM] [TplinkSmarthome] Initializing TplinkSmarthome platform...
[3/19/2020, 4:10:59 PM] [TplinkSmarthome] homebridge-tplink-smarthome v4.0.1, node v12.16.1, homebridge v0.4.53
[3/19/2020, 4:10:59 PM] [Teufel] Initializing Teufel platform...
[3/19/2020, 4:11:00 PM] Loading 0 accessories...
[3/19/2020, 4:11:00 PM] [TplinkSmarthome] Configuring cached accessory: [Steckdose] 80066A532F85603668A26215D40A84111A060AF9 668ba3fb-dda1-46c8-8584-1a59c6753e4a
Setup Payload:
X-HM://0024D8MEUJ6G4
Scan this code with your HomeKit app on your iOS device to pair with Homebridge:
...
[3/19/2020, 4:11:00 PM] [Shelly] 5 accessories loaded from cache
[3/19/2020, 4:11:00 PM] Homebridge is running on port 51826.
[3/19/2020, 4:11:00 PM] [Shelly] Admin server is running on port 8080
(node:346) UnhandledPromiseRejectionWarning: Error: send ENETUNREACH 224.0.1.187:5683
at doSend (dgram.js:697:16)
at defaultTriggerAsyncIdScope (internal/async_hooks.js:311:12)
at afterDns (dgram.js:643:5)
at processTicksAndRejections (internal/process/task_queues.js:85:21)
(node:346) 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: 1)(node:346) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[3/19/2020, 4:11:04 PM] [Config] Homebridge Config UI X v4.13.0 is listening on :: port 8081
[3/19/2020, 4:11:10 PM] [TplinkSmarthome] New Device Online: [Steckdose] plug [80066A532F85603668A26215D40A84111A060AF9] 192.168.1.207 9999
[3/19/2020, 4:11:10 PM] [TplinkSmarthome] Adding: [Steckdose] plug [80066A532F85603668A26215D40A84111A060AF9]
homebridge : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/kill -9 1056
pam_unix(sudo:session): session opened for user root by (uid=0)
pam_unix(sudo:session): session closed for user root
[3/19/2020, 4:12:12 PM] [Config] Homebridge restart request received
[3/19/2020, 4:12:12 PM] [Config] Executing restart command: sudo -n systemctl restart homebridge
homebridge : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart homebridge
pam_unix(sudo:session): session opened for user root by (uid=0)
Stopping Node.js HomeKit Server...
[3/19/2020, 4:12:12 PM] Got SIGTERM, shutting down Homebridge...
homebridge.service: Main process exited, code=exited, status=143/n/a
homebridge.service: Failed with result 'exit-code'.
Stopped Node.js HomeKit Server.
homebridge.service: Found left-over process 780 (homebridge-conf) in control group while starting unit. Ignoring.
This usually indicates unclean termination of a previous run, or service implementation deficiencies.
homebridge.service: Found left-over process 1743 (sh) in control group while starting unit. Ignoring.
This usually indicates unclean termination of a previous run, or service implementation deficiencies.
homebridge.service: Found left-over process 1744 (sudo) in control group while starting unit. Ignoring.
This usually indicates unclean termination of a previous run, or service implementation deficiencies.
homebridge.service: Found left-over process 1749 (systemctl) in control group while starting unit. Ignoring.
This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Started Node.js HomeKit Server.
pam_unix(sudo:session): session closed for user root
[3/19/2020, 4:12:19 PM] Loaded config.json with 0 accessories and 4 platforms.
[3/19/2020, 4:12:19 PM] ---
[3/19/2020, 4:12:19 PM] Loaded plugin: homebridge-config-ui-x
[3/19/2020, 4:12:19 PM] Registering platform 'homebridge-config-ui-x.config'
[3/19/2020, 4:12:19 PM] ---
[3/19/2020, 4:12:19 PM] Loaded plugin: homebridge-shelly
[3/19/2020, 4:12:19 PM] Registering platform 'homebridge-shelly.Shelly'
[3/19/2020, 4:12:19 PM] ---
[3/19/2020, 4:12:20 PM] Loaded plugin: homebridge-teufel
[3/19/2020, 4:12:20 PM] Registering platform 'homebridge-teufel.Teufel'
[3/19/2020, 4:12:20 PM] ---
[3/19/2020, 4:12:20 PM] Loaded plugin: homebridge-tplink-smarthome
[3/19/2020, 4:12:20 PM] Registering platform 'homebridge-tplink-smarthome.TplinkSmarthome'
[3/19/2020, 4:12:20 PM] ---
[3/19/2020, 4:12:20 PM] Loading 4 platforms...
[3/19/2020, 4:12:20 PM] [Config] Initializing config platform...
[3/19/2020, 4:12:20 PM] [Config] Spawning homebridge-config-ui-x with PID 1775
[3/19/2020, 4:12:20 PM] [Shelly] Initializing Shelly platform...
[3/19/2020, 4:12:20 PM] [TplinkSmarthome] Initializing TplinkSmarthome platform...
[3/19/2020, 4:12:20 PM] [TplinkSmarthome] homebridge-tplink-smarthome v4.0.1, node v12.16.1, homebridge v0.4.53
[3/19/2020, 4:12:20 PM] [Teufel] Initializing Teufel platform...
[3/19/2020, 4:12:20 PM] Loading 0 accessories...
[3/19/2020, 4:12:20 PM] [TplinkSmarthome] Configuring cached accessory: [Steckdose] 80066A532F85603668A26215D40A84111A060AF9 668ba3fb-dda1-46c8-8584-1a59c6753e4a
Setup Payload:
X-HM://0024D8MEUJ6G4
Scan this code with your HomeKit app on your iOS device to pair with Homebridge:
....
[3/19/2020, 4:12:20 PM] [Shelly] 5 accessories loaded from cache
[3/19/2020, 4:12:20 PM] Homebridge is running on port 51826.
[3/19/2020, 4:12:20 PM] [Shelly] Admin server is running on port 8080
[3/19/2020, 4:12:20 PM] [TplinkSmarthome] New Device Online: [Steckdose] plug [80066A532F85603668A26215D40A84111A060AF9] 192.168.1.207 9999
[3/19/2020, 4:12:20 PM] [TplinkSmarthome] Adding: [Steckdose] plug [80066A532F85603668A26215D40A84111A060AF9]
[3/19/2020, 4:12:23 PM] [Config] Homebridge Config UI X v4.13.0 is listening on :: port 8081
The text was updated successfully, but these errors were encountered: