Skip to content
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

stuck on: mqtt homekit/connected 0 0 #155

Open
Kevin-De-Koninck opened this issue Aug 9, 2019 · 2 comments
Open

stuck on: mqtt homekit/connected 0 0 #155

Kevin-De-Koninck opened this issue Aug 9, 2019 · 2 comments

Comments

@Kevin-De-Koninck
Copy link

First time using this project but I'm unable to get it working reliably.
I've the following config file:

{
  "a": {
    "id": "a",
    "name": "b",
    "manufacturer": "b",
    "model": "b",
    "serial": "b",
    "topicIdentify": "b",
    "category": 1,
    "payloadIdentify": false,
    "services": [
      {   
        "name": "n",
        "service": "ContactSensor",
        "topic": {
          "statusContactSensorState": "zigbee2mqtt/DoorSensor1",
          "statusLowBattery": "", 
          "statusTampered": "", 
          "statusActive": "", 
          "statusFault": ""
        },  
        "json": {
          "statusContactSensorState": "contact",
          "statusLowBattery": "", 
          "statusTampered": "", 
          "statusActive": "", 
          "statusFault": ""
        },  
        "payload": {
          "onContactDetected": true,
          "invertLowBattery": false,
          "invertTampered": false,
          "invertActive": false,
          "invertFault": false
        },  
        "config": {}, 
        "props": {}
      }   
    ]   
  }
}

And when I start homekit2mqtt I receive the following:

pi@raspberrypi:~ $ homekit2mqtt -u mqtt://192.168.1.10:1883 --username CC:22:3D:E3:CE:FE -v debug
2019-08-09 12:20:01.595 <info>  homekit2mqtt 1.1.2 starting
2019-08-09 12:20:01.656 <info>  mqtt trying to connect mqtt://192.168.1.10:1883
2019-08-09 12:20:03.513 <info>  using hap-nodejs version 0.4.47
2019-08-09 12:20:03.660 <debug> mqtt subscribe #
2019-08-09 12:20:03.914 <info>  http server listening on port 51888
2019-08-09 12:20:04.740 <debug> mqtt unsubscribe #
2019-08-09 12:20:04.765 <info>  loading HomeKit to MQTT mapping file /usr/local/lib/node_modules/homekit2mqtt/example-homekit2mqtt.json
2019-08-09 12:20:04.787 <debug> creating new accessory "b" "a" 86f7e437-faa5-4a7f-8e15-d1ddcb9eaeae
2019-08-09 12:20:04.819 <debug> loading services/ContactSensor.js
2019-08-09 12:20:04.837 <debug> adding service ContactSensor to accessory b
2019-08-09 12:20:04.870 <debug> mqtt subscribe zigbee2mqtt/DoorSensor1
2019-08-09 12:20:04.932 <debug> addBridgedAccessory b
2019-08-09 12:20:04.941 <info>  hap created 0 Camera Accessories and 1 Bridged Accessories.
2019-08-09 12:20:05.156 <debug> hap publishing bridge "MQTT Bridge" username=CC:22:3D:E3:CE:FE port=51826 pincode=031-45-154 setupURI=X-HM://001408XXE74KD
2019-08-09 12:20:05.260 <debug> > mqtt homekit/connected 2
2019-08-09 12:20:05.267 <info>  hap Bridge listening on port 51826

Scan this code with your HomeKit app on your iOS device to pair with the bridge                       

2019-08-09 12:20:06.579 <info>  mqtt connected mqtt://192.168.1.10:1883
2019-08-09 12:20:06.706 <debug> < mqtt zigbee2mqtt/bridge/state online online
2019-08-09 12:20:06.713 <debug> < mqtt zigbee2mqtt/bridge/config {"version":"1.5.1","commit":"ac3b924","coordinator":20190608,"log_level":"info","permit_join":true} {"version":"1.5.1","commit":"ac3b924","coordinator":20190608,"log_level":"info","permit_join":true}
2019-08-09 12:20:06.717 <debug> < mqtt homekit/connected 0 0

Sometimes, after killing and restarting it, I get:

2019-08-09 12:18:06.717 <debug> < mqtt homekit/connected 1 1

Followed by all mqtt messages and then it works. but most of the time, it's stuck in state '0'.

What is the cause of this and how can I fix this?

@Kevin-De-Koninck
Copy link
Author

Disabling the webserver does the trick to get it reliably working. Any idea about the cause?

@mattsheffiel
Copy link
Contributor

Are other devices able to connect to the MQTT broker without issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants