Problem with control of some accessories about homebridge-zway HOT 12 CLOSED

Hello,

I need a copy of your devices output. You'll need to login to the Z-Way standard UI--e.g. at http://your.pi.i.p:8083/, and then from that same browser window hit http://your.pi.i.p:8083/ZAutomation/api/v1/devices (replacing your.pi.i.p with your device's IP address of course), and attach or post the contents here.

Funny, the dimmer definitely should have worked, but I have no roller shutters, so I probably need to make some changes to get that to work.

from homebridge-zway.

Thanks!
So, here I attached the devices.txt.
comments:
1.Fibar Group Switch 2-0 -> works (Fibar Wall-Plug)
2.Switch 3-0 Everspring -> not working (Fibar Roller Shutter, weird because titel is named "Evererspring", but it is really the Fibar Roller Shutter)
3. Fibar Group Dimmer (15.0) -> not working (Fibar Dimmer Switch)
Edit: Now, i´m not aware why, the Dimmer works! :) ...Roller Shutter still can´t be controlled with HomeKit.
Edit2: Made a new device Interview from z-way expert UI with the Roller Shutter, and now i can control it too! :)

Hope this information will help.

btw:

• where can i find the "/accessories" from HomeBrige instance? is this useful too?
• Is there a way to check and add supported accessories to the HomeBridgezway-plugin?

devices.txt

from homebridge-zway.

Hmm.

Everything here looks correct. Can you try something for me: the way homebridge-zway controls accessories is to call the URLs defined in the Z-Way server API. If those are working, then the problem is in my code. If they don't work, then there's some problem on the Z-Way side...or they have changed something in rc6.

Try this: after logging into the Z-Way web UI--like you did to get the devices file--in the same browser, hit this URL:

http://your.pi.i.p:8083/ZAutomation/api/v1/devices/ZWayVDev_zway_3-0-37/command/on

or

http://your.pi.i.p:8083/ZAutomation/api/v1/devices/ZWayVDev_zway_3-0-37/command/off

Does that raise and lower your window shutters?

Or, do these:

http://your.pi.i.p:8083/ZAutomation/api/v1/devices/ZWayVDev_zway_15-0-38/command/on
http://your.pi.i.p:8083/ZAutomation/api/v1/devices/ZWayVDev_zway_15-0-38/command/off

Turn on and off the dimmer?

If those don't work, did you get any error text in the browser window? If they do work, let me know and I'll give you the next troubleshooting steps.

from homebridge-zway.

Hi,
i tried the commands, and every command works.
As i edited my post, now its working also with the home kit app and siri. :)
So, i have no idea, why it is working now. only think i have done again was a device interview for both devices.

from homebridge-zway.

Hmm. Okay, we'll leave this open for a bit--in case it acts up again we can troubleshoot further. But good news!

from homebridge-zway.

It would be interesting to se your device list now after new Interview of your shutter to see if it has changed from a switchbinary to something else. Can you upload your device list again?

from homebridge-zway.

I've got a similar issue after upgrading to 0.4.0 and ZWay 2.2.2. My dimmers don't have any controls (on/off or dimming), only switches (binary lights) work. Using the direct URL hit works (as described above). Any suggestions?

[4/17/2016, 11:16:57 PM] Initializing platform accessory 'Master Bedroom Spot Lights'...
  ZWayServer Got typeKey switchMultilevel.multilevel for vdev ZWayVDev_zway_151-0-38 +10ms
  ZWayServer { deviceType: 'switchMultilevel', probeTitle: undefined, probeType: 'multilevel' } +1ms
  ZWayServer WARN: Only the InformationService was successfully configured for ZWayVDev_zway_151-0-38! No device services available! +2ms

devices.txt

from homebridge-zway.

@Fingerz Your problem is that you've upgraded to Z-Way 2.2.2. They changed one little field--probeType--in 2.2.2 but they changed it on a BUNCH of device types, if not all of them. 😡 Looks like it's time for me to upgrade and royally break myself just so I can see what all the heck they did.

from homebridge-zway.

What version of ZWay should I roll back to until you’ve had time to implement a workaround? I was on 2.2.0 before…is 2.2.1 safe? Is their version roll back process reliable or am I hosed?

On Apr 18, 2016, at 8:59 AM, SphtKr [email protected] wrote:

@Fingerz https://github.com/Fingerz Your problem is that you've upgraded to Z-Way 2.2.2. They changed one little field--probeType--in 2.2.2 but they changed it on a BUNCH of device types, if not all of them. 😡 Looks like it's time for me to upgrade and royally break myself just so I can see what all the heck they did.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub #13 (comment)

from homebridge-zway.

Update: as expected rolling back to ZWay v2.2.1 has resolved the issues I was having.

from homebridge-zway.

Great! Glad to hear it, but of course I do intend to support those changes in 2.2.2 soon. And the way I handle those, it should be backwards compatible so you won't have to switch to 2.2.2 immediately after I release 0.5.0.

from homebridge-zway.

Closing as it appears this issue resolved and did not recur.

from homebridge-zway.