Closed Mario-Greiner closed 4 years ago
Can you send me your homebridge log file? Particularly from startup (when devices are scanned) and when you try to change the state.
Devices not showing up on your phone sounds like an issue unrelated to the plugin. Do you have any other plugins? Do they work correctly?
The log folder is completley empty.
The issue with devices not showing up is a homebridge issue and has nothing to do with the plugin your right. But the state wont change.
Here the console if it helps
EDIT: The devices now showing up with "No response"
Could you pull the latest master, run homebridge in debug mode and capture the log again?
I've added some more logging to better debug unknown devices. So far I've only tested the plugin with my Occhio lamps so it's possible your lamps are somehow different. The new log should tell us if they are. The most important part starts with "Found x unit(s) in the network y".
Also, try to turn the lamps on/off using the switches on the lamps, while homebridge is running. The log in debug mode should show homebridge being notified about these events by the Casambi Cloud, which would confirm that the gateway is working properly and show us how they're reporting their new state.
Thanks for the help so far. Plugin is updated and debug mode is enabled.
Now it looks like this
You can see the protocol says unsupported control type.
These are the controlls in the app
Looks like you're not running the latest code. I probably wasn't clear that I wanted you to overwrite the plugin files with the latest from github instead of updating to the latest release.
To make this easier, I made a new release now, v0.2.3. You should be able to update to it using the homebridge web ui. Please make sure you're running v0.2.3 and try to get the debug log again.
Sorry for the confusion.
Yes, the device "Küche" is unsupported and shouldn't be showing up in homebridge/homekit. Right now, the plugin only supports devices of type "Luminaire" (a lamp) but this device is of type "Driver". What does it do exactly?
The other devices (PC, Bett, Tisch and HYPRO-F) are not throwing this error so they should be of type "Luminaire". Let's try to figure out why they don't work first.
Edit:
Hmm, your log does show the "Send controlUnit" messages which mean that commands are being sent to the devices to turn them on/off. Normally, this should be followed by a notification from the device that its state has changed. This is missing here. A common reason for this, from my experience, is a problem with the gateway device. Make sure that the app is open on the gateway and that the lamp you're trying to control is in the Bluetooth range of the gateway.
Oh im sorry i misunderstood your last reply
Here is the new log homebridge.log.txt
Now i noticed that sometimes i cant change the state of the luminare inside the app
The device "Küche" is also a luminare but it has a driver with integrated casambi module inside (like THIS) and the other luminaires only have the casambi module.
EDIT: Now its kind of working. I noticed that i dindt had the gateway option enabled. The device "Hypro" is now working but not the devicces "PC" and "Bett"
Here the new log NEWhomebridge.log.txt
Thanks for the logs.
All devices (except "Küche") should work. They all support the "dimmer" control which is used to set the brightness of the light.
It looks like the Driver lamp ("Küche") also exposes the "dimmer" control so adding support for it should be easy. I'll do that in the next version.
The reason why controlling the lights didn't/doesn't work seems to be a problem with communication between the lights and the gateway device.
Do you have a dedicated gateway device that you keep close to the lights? That's what I have, I bought a cheap Android tablet and have it hidden in a cabinet, plugged into a charger 24/7. It's running the Casambi app and it's configured as a gateway in the network settings of the Casambi app. Make sure you can control the lights from the gateway itself. This will tell you that the lights are in the Bluetooth range of the gateway.
If that works, the plugin should work as well.
Another way to test the gateway is to try to use the app on your phone to control the lights while you're not home. It should work now because the app will talk to the gateway device to control the lights. You can test this without leaving your home by disabling WiFi and Bluetooth on your phone and letting it use LTE.
The plugin basically does the same thing so it should work.
Ok now it almost works...
The only luminaire wich is not working is the "HYPRO" i think its because of the unsupported switch types.
But thanks for the support. If you have a paypal link or something simillar please send it to me i want to send you a little thank you :)
Hmm, I can see HYPRO working correctly in the log file:
[9/3/2020, 9:12:20 PM] [Casambi] Set characteristic On of unit HYPRO-F to true
[9/3/2020, 9:12:20 PM] [Casambi] Send controlUnit for HYPRO-F { Dimmer: { value: 1 } }
[9/3/2020, 9:12:20 PM] [Casambi] Received unitChanged for HYPRO-F {
controls: [
{ type: 'Dimmer', value: 1 },
The first line is the light being turned on in HomeKit, followed by a command being sent to the light and finally a confirmation coming back that the light is on now.
Btw, you should also be able to set the colour temperature for HYPRO through HomeKit.
The other switches (in-/direct, diffusion) are not supported because of HomeKit limitations.
And thank you for the kind offer but there's no need to give me anything. Have a nice weekend :)
Hi the devices are showing up on my homebridge but not on my phone. And on homebridge i cant change the state.
Im running homebridge on a synology rs1219+ indside docker