search

giejay / domoticz-gbridge-plugin

Domoticz plugin for the Kappelt gBridge
16 stars 4 forks source link

New devices won't show up in gBridge portal, gBridge neither in google home app #17

Closed pwitte closed 4 years ago

pwitte commented 4 years ago

New devices won't show up in gBridge portal, gBridge neither in google home app

2019-07-22 15:35:54.350 (gBridge) Debug logging mask set to: PYTHON 2019-07-22 15:35:54.351 (gBridge) onStart called 2019-07-22 15:35:54.351 (gBridge) MqttClient::init 2019-07-22 15:35:54.351 (gBridge) MqttClient::Open 2019-07-22 15:35:54.351 (gBridge) gBridgeClient::init 2019-07-22 15:35:54.351 (gBridge) DomoticzClient::init 2019-07-22 15:35:54.351 (gBridge) Starting sync 2019-07-22 15:35:54.353 (gBridge) Calling API for action: Fetching all devices from gBridge, url: https://gbridge.io/api/device 2019-07-22 15:35:54.859 (gBridge) Successfully executed action: Fetching all devices from gBridge, response: [] 2019-07-22 15:35:54.958 (gBridge) Linked devices: {} 2019-07-22 15:35:54.959 (gBridge) Domoticz devices available for gBridge: dict_keys(['Studiolamp', 'Wand verlichting', 'ALL', 'Studio Aan', 'Ganglamp', 'Sfeer verlichting']) 2019-07-22 15:35:54.960 (gBridge) Calling API for action: Try to create device Studiolamp for type 4 with traits [3], url: https://gbridge.io/api/device 2019-07-22 15:35:54.347 Status: (gBridge) Entering work loop. 2019-07-22 15:35:54.348 Status: (gBridge) Initialized version 0.0.14 2019-07-22 15:35:54.940 Status: Incoming connection from: 127.0.0.1 2019-07-22 15:35:55.343 (gBridge) Successfully executed action: Try to create device Studiolamp for type 4 with traits [3], response: [] 2019-07-22 15:35:55.343 (gBridge) Calling API for action: Try to create device Wand verlichting for type 4 with traits [3], url: https://gbridge.io/api/device 2019-07-22 15:35:55.774 (gBridge) Successfully executed action: Try to create device Wand verlichting for type 4 with traits [3], response: [] 2019-07-22 15:35:55.775 (gBridge) Calling API for action: Try to create device ALL for type 4 with traits [3], url: https://gbridge.io/api/device 2019-07-22 15:35:56.273 (gBridge) Successfully executed action: Try to create device ALL for type 4 with traits [3], response: [] 2019-07-22 15:35:56.274 (gBridge) Calling API for action: Try to create device Studio Aan for type 4 with traits [3], url: https://gbridge.io/api/device 2019-07-22 15:35:56.720 (gBridge) Successfully executed action: Try to create device Studio Aan for type 4 with traits [3], response: [] 2019-07-22 15:35:56.721 (gBridge) Calling API for action: Try to create device Ganglamp for type 4 with traits [3], url: https://gbridge.io/api/device 2019-07-22 15:35:57.098 (gBridge) Successfully executed action: Try to create device Ganglamp for type 4 with traits [3], response: [] 2019-07-22 15:35:57.099 (gBridge) Calling API for action: Try to create device Sfeer verlichting for type 4 with traits [3], url: https://gbridge.io/api/device 2019-07-22 15:35:57.513 (gBridge) Successfully executed action: Try to create device Sfeer verlichting for type 4 with traits [3], response: [] 2019-07-22 15:35:57.515 (gBridge) Done 2019-07-22 15:35:57.677 (gBridge) onConnect called 2019-07-22 15:35:57.678 (gBridge) MQTT connected !!!!successfully. 2019-07-22 15:35:57.678 (gBridge) MqttClient::Connect 2019-07-22 15:35:57.678 (gBridge) MQTT CONNECT ID: 'Domoticz_1563802557' 2019-07-22 15:35:57.728 (gBridge) Message from base 2019-07-22 15:35:57.728 (gBridge) Incoming message!{'Description': 'Connection Accepted', 'Verb': 'CONNACK', 'Status': 0} 2019-07-22 15:35:57.729 (gBridge) MqttClient::Subscribe['gBridge/u2011/#'] 2019-07-22 15:35:57.879 (gBridge) Message from base 2019-07-22 15:35:57.879 (gBridge) Incoming message!{'PacketIdentifier': 1, 'Verb': 'SUBACK', 'Topics': [{'Description': 'Success - Maximum QoS 0', 'Status': 0}]} 2019-07-22 15:35:57.880 (gBridge) onMQTTSubscribed

giejay commented 4 years ago

That's odd, I will try it myself tonight

giejay commented 4 years ago

Ok, so I tried it myself and a device was created instantly when I added the gBridge description. What happens when you create a dummy device in gBridge portal and press update in the hardware tab? What do you see in the log for this line: Fetching all devices from gBridge, response: []

pwitte commented 4 years ago

This is the log i get after a clean git cone and configuring the plugin in the hardware-tab: https://pastebin.com/Fd8Q8ejV

This is the log i get with a dummy file made in the gBridge portal: https://pastebin.com/cJ1ftSCN

Met vriendelijke groet,

Pepijn de Witte

Jonkers van Ossstraat 14 5346 RL Oss

T: + 31 6 40 66 75 68

Op di 23 jul. 2019 om 20:56 schreef GJ Compagner notifications@github.com:

Ok, so I tried it myself and a device was created instantly when I added the gBridge description. What happens when you create a dummy device in gBridge portal and press update in the hardware tab? What do you see in the log for this line: Fetching all devices from gBridge, response: []

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/giejay/domoticz-gbridge-plugin/issues/17?email_source=notifications&email_token=ABIXNSTCGPN23PTJMZNMLHLQA5H6XA5CNFSM4IFYX6OKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2UDAIY#issuecomment-514338851, or mute the thread https://github.com/notifications/unsubscribe-auth/ABIXNSXOYWIE257VYBRULMLQA5H6XANCNFSM4IFYX6OA .

giejay commented 4 years ago

Now it seems like a different issue, can you try port 8080 for domoticz? If you are using docker, you need the docker container port, not the host port

pwitte commented 4 years ago

Then the following rolls out from the log https://pastebin.com/MMshE09R

Met vriendelijke groet,

Pepijn de Witte

Jonkers van Ossstraat 14 5346 RL Oss

T: + 31 6 40 66 75 68

Op di 23 jul. 2019 om 21:49 schreef GJ Compagner notifications@github.com:

Now it seems like a different issue, can you try port 8080 for domoticz? If you are using docker, you need the docker container port, not the host port

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/giejay/domoticz-gbridge-plugin/issues/17?email_source=notifications&email_token=ABIXNSRRXVIFL66T6KP3FV3QA5OEVA5CNFSM4IFYX6OKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2UHSZA#issuecomment-514357604, or mute the thread https://github.com/notifications/unsubscribe-auth/ABIXNSQTPTDZSXTLG2QHR2DQA5OEVANCNFSM4IFYX6OA .

giejay commented 4 years ago

The gBridge URL is invalid, it should be https://gbridge.kappelt.net

pwitte commented 4 years ago

MANY THANKS! It finally works! It's just confusing because the gbridge mqtt address is gbridge.io, but the gbridge url still has to be the old one haha.

Just a quick tip: the package "python-dev" has to be installed first before cloning your github repo. Otherwise, the plugin won't show up in the list. Took me 4 hours yesterday to figure it out.

Met vriendelijke groet,

Pepijn de Witte

Op di 23 jul. 2019 om 22:00 schreef GJ Compagner notifications@github.com:

The gBridge URL is invalid, it should be https://gbridge.kappelt.net

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/giejay/domoticz-gbridge-plugin/issues/17?email_source=notifications&email_token=ABIXNSQSWQZZHRUA6HDIUTDQA5PNJA5CNFSM4IFYX6OKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2UIQUQ#issuecomment-514361426, or mute the thread https://github.com/notifications/unsubscribe-auth/ABIXNSSSK2FHSRA3Q4OTXGTQA5PNJANCNFSM4IFYX6OA .

giejay commented 4 years ago

Thats weird, should not be necessary to install python-dev, python3 should be sufficient. I will look into it.