-
Notifications
You must be signed in to change notification settings - Fork 15
FYI: Chamberlain/MyQ is Still Broken #7
Comments
Shorten your Restart homebridge. Open and close the garage door and check the log |
I put this in the exact place as instructed; however Homebridge just crashes now: [10/23/2016, 7:59:54 PM] Homebridge is running on port 51826. Thanks, but I'm beginning to think this is just beyond my ability/patience. I've been screwing with this for the better part of this weekend and I'm basically nowhere (and I work in IT). |
My bad. Please put If you decided to give up, it's your choice. But if you are willing to stick with me, I believe we can make it working. It's been working for a lot of people already, including my self. The problem is that there's never an official API for MyQ and we really need the community's help to make it working for everyone. |
Thanks, but that made no changes. I can open the door; however it shows closed and telling it to close does nothing. Basically, I have to tell it to open to open and open to close it. Asking status always returns closed whether closed or open. Home also shows the same; however this time it clearly showed 'Opening' while opening (but the state immediately changes to closed). |
My fault, didn't mean to close. |
I know it's not fixing anything yet. I just need the log to see what's the state reported by the server. |
I think the state's 2: [10/23/2016, 8:21:30 PM] [MyQ] Logged in with MyQ user ID 0 Which I assume is closed? |
Can you please add and post your log afterwards? |
ChildrenMyQDeviceIds: '', |
I actually need the log prior to that as well. It should starts with something like |
Any way to take this offline? There's quite a bit of info I'm uncomfortable posting in-the-blind (email, SN, device ID). |
You can always email me at luisiam@gmail.com |
You can also remove those sensitive information. I just want to know the whole structure of the object. |
[10/23/2016, 9:09:15 PM] Homebridge is running on port 51826. |
[10/23/2016, 9:21:56 PM] Homebridge is running on port 51826. This shows that door was CLOSED, I set to OPEN (state changed), but then to close it again its state is OPEN again. The entire time it was OPEN, Home reported as CLOSED. |
I believe something went wrong with the state reporting and conversion. HomeKit always reports the state as closed. Therefore, you can never close the garage door since HomeKit thinks that it's always closed. Can you install with the following command: Restart homebridge afterwards. Have the garage door closed, open the garage door. Post the log afterwards. Thanks. |
Cannot run (presented with the following errors): npm ERR! node v6.8.1 npm ERR! Error: EACCES: permission denied, access '/usr/local/lib/node_modules' npm ERR! Please include the following file with any support request: I'm on RPi3 logged in as Pi. |
Did you use |
I did and this didn't change anything (same as before: always shows state of CLOSED and have to tell it to OPEN to open and OPEN to close). Thanks for your time, but I officially give up. Nothing is worth this this many wasted hours (especially this). I appreciate all the devs work on projects like this, but I work IT (and have for 25y) and couldn't get this working after wasting over 20h on it. I honestly cannot imagine someone non-IT literate ever getting something like this working (and that's a problem, because nothing should be this hard/impossible to deploy). Again, ultimate fault/blame lies with both Apple (for their lack of Homekit 'seriousness') and Chamberlain (for their non-existent Homekit implementation). |
Well, I am still pinpointing the problem. I still need to log for troubleshooting. Anyways, it's your choice. |
I have a Chamberlain (with separate MyQ hub) and this unfortunately didn't fix my issue.
Open/Close report states are still useless (door can be open and it thinks it's closed, Siri 'open the garage' opens the door, but 'close the garage' does nothing).
I'd like to thank the dev for working on this, but at this point I really wish Chamberlain/Apple would just get their crap together and give me a working solution.
The text was updated successfully, but these errors were encountered: