search

TheMrBooyah / hassio-dirigera-client

4 stars 0 forks source link

Can't see events appearing in MQTT (via MQTT Explorer) #9

Closed Timmwardion closed 1 year ago

Timmwardion commented 1 year ago

Hi there, I can't see the Dirigera events appear in MQTT (using MQTT Explorer). Seems like connection to core-mosquitto works fine as I don't see any errors in the logs but the events that I see in the Dirigera logs don't appear.

What topic should the be published under? All I see is $SYS.

TheMrBooyah commented 1 year ago

The topics used in the addon are generated as follows: PREFIX + Type of component + Gateway ID + device ID + SUFFIX

Which would look as follows: homeassistant/light/{Dirigera ID}/{device ID}/availability

Availability in this example is the suffix

sbr2004 commented 1 year ago

Same here, client connects to mqtt but no events are published and devices to not appear in Home Assistant.

Example: there is some error in log, when I press Ikea switch.

2023-04-13 12:14:23.817 DEBUG 65 --- [or-http-epoll-5] d.d.i.d.c.m.hass.HassDeviceEventHandler : Received device state changed event: {"deviceType":"light","id":"6d0155ec-4f7b-48b8-9bf0-a8e8f0f2349e_1","type":"light","deviceType":"light","createdAt":"2022-11-22T15:45:24","isReachable":true,"lastSeen":"2023-04-13T12:14:23","attributes":{"isOn":false},"remoteLinks":["0f4d4395-5905-4745-83cf-d705d97c042c_1"]} 2023-04-13 12:14:23.889 ERROR 65 --- [or-http-epoll-5] d.d.i.dirigera.client.api.WebSocketApi : Error while listening to websocket events: block()/blockFirst()/blockLast() are blocking, which is not supported in thread reactor-http-epoll-5 2023-04-13 12:14:24.891 INFO 65 --- [oundedElastic-2] d.d.i.d.client.api.http.ClientApi : Finished ping thread: id=31, name=boundedElastic-2 2023-04-13 12:14:24.891 INFO 65 --- [oundedElastic-1] d.d.i.dirigera.client.api.WebSocketApi : Finish event handler thread: id=21, name=boundedElastic-1 2023-04-13 12:14:24.895 INFO 65 --- [oundedElastic-1] d.d.i.dirigera.client.api.WebSocketApi : Start event handler thread: id=21, name=boundedElastic-1 2023-04-13 12:14:25.012 INFO 65 --- [oundedElastic-2] d.d.i.d.client.api.http.ClientApi : Start ping thread: id=31, name=boundedElastic-2 2023-04-13 12:14:27.217 DEBUG 65 --- [or-http-epoll-3] d.d.i.dirigera.client.api.WebSocketApi : Received Dirigera event: type=DEVICE_STATE_CHANGED, id=730e3d27-190c-443a-96ff-9ff1853ca647, source=urn:com:ikea:homesmart:iotc:zigbee, time=2023-04-13T12:14:27 2023-04-13 12:14:27.218 DEBUG 65 --- [or-http-epoll-3] d.d.i.d.c.m.hass.HassDeviceEventHandler : Received device state changed event: {"deviceType":"light","id":"6d0155ec-4f7b-48b8-9bf0-a8e8f0f2349e_1","type":"light","deviceType":"light","createdAt":"2022-11-22T15:45:24","isReachable":true,"lastSeen":"2023-04-13T12:14:27","attributes":{"isOn":true},"remoteLinks":["0f4d4395-5905-4745-83cf-d705d97c042c_1"]} 2023-04-13 12:14:27.223 ERROR 65 --- [or-http-epoll-3] d.d.i.dirigera.client.api.WebSocketApi : Error while listening to websocket events: block()/blockFirst()/blockLast() are blocking, which is not supported in thread reactor-http-epoll-3 2023-04-13 12:14:28.224 INFO 65 --- [oundedElastic-1] d.d.i.dirigera.client.api.WebSocketApi : Finish event handler thread: id=21, name=boundedElastic-1 2023-04-13 12:14:28.225 INFO 65 --- [oundedElastic-1] d.d.i.dirigera.client.api.WebSocketApi : Start event handler thread: id=21, name=boundedElastic-1 2023-04-13 12:14:28.224 INFO 65 --- [oundedElastic-2] d.d.i.d.client.api.http.ClientApi : Finished ping thread: id=31, name=boundedElastic-2

TheMrBooyah commented 1 year ago

The issue you're facing seems to be related to the actual client.

I've not heard of seen any activity from the repository owner. I'll see what I can find out myself soon!

Closing this issue since it's not related to the actual add on.

Link to issue on base software https://github.com/dvdgeisler/DirigeraClient/issues/77