You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firstly, awesome project and beautiful documentation. I didn't even need to change my Firmware as my Hub is using 2.43 (thankfully, I disabled the force updates on it).
Background information about my system:
RaspberryPi 4:
Setup run fine and my HUB + Cat Flap got published into MQTT in HASS just fine as well.
In my cat flap I've 3 options as switches CurfewKeepInand KeepOut. All three aren't enabled yet by default.
I tried to hit any of those switches and got this error in PHL:
2023-03-28 01:13:52,992 : [ERROR] : Task exception was never retrieved
future: <Task finished name='Task-2' coro=<mqtt_start() done, defined at /usr/local/lib/python3.9/site-packages/pethublocal/frontend.py:204> exception=TypeError("emit() got an unexpected keyword argument 'broadcast'")>
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/pethublocal/frontend.py", line 295, in mqtt_start
await asyncio.gather(*tasks)
File "/usr/local/lib/python3.9/site-packages/pethublocal/frontend.py", line 345, in parse_message
await sio.emit('web_message', data=parsed_result, broadcast=True, include_self=False)
TypeError: emit() got an unexpected keyword argument 'broadcast'
2023-03-28 01:13:49,956 : [ INFO] : MQTT: HA Message topic "pethub/ha/<Serial_Number> /Curfew" message "ON"
2023-03-28 01:13:49,957 : [DEBUG] : Generate Message Hub:<Serial_Number> Product:3, Operation:CURFEWS
2023-03-28 01:13:49,966 : [DEBUG] : Updating Curfews
2023-03-28 01:13:49,973 : [ INFO] : ToHub: Moving from current lock mode UNLOCKED to lock mode CURFEW
2023-03-28 01:13:49,975 : [DEBUG] : Generate Message Hub<Serial_Number> Product:3, Operation:CURFEW
2023-03-28 01:13:52,992 : [ERROR] : Task exception was never retrieved
future: <Task finished name='Task-2' coro=<mqtt_start() done, defined at /usr/local/lib/python3.9/site-packages/pethublocal/frontend.py:204> exception=TypeError("emit() got an unexpected keyword argument 'broadcast'")>
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/pethublocal/frontend.py", line 295, in mqtt_start
await asyncio.gather(*tasks)
File "/usr/local/lib/python3.9/site-packages/pethublocal/frontend.py", line 345, in parse_message
await sio.emit('web_message', data=parsed_result, broadcast=True, include_self=False)
TypeError: emit() got an unexpected keyword argument 'broadcast'
2023-03-28 01:14:01,975 : [ERROR] : packet queue is empty, aborting
2023-03-28 01:14:16,976 : [ INFO] : SIO: Disconnect <SIO>
I cleaned the log.
In the MQTT logs I get this:
1679968001: New connection from <IP>:54926 on port 1883.
1679968001: New client connected from <IP>:54926 as PetHubLocal (<cleared, not sure if needed>).
I'm kinda lost, and I've no clue where to debug, as it seems to work for you guys.
Maybe someone can help me with that or at least point me in a direction if it's my MQTT Broker or PHL.
Thank you
The text was updated successfully, but these errors were encountered:
Pr0mises
changed the title
HASS MQTT Cat Flap is not controllable, chaning the switch results in frontend.py Error
HASS MQTT Cat Flap is not controllable, changing the switch results in frontend.py Error
Apr 2, 2023
Firstly, awesome project and beautiful documentation. I didn't even need to change my Firmware as my Hub is using 2.43 (thankfully, I disabled the force updates on it).
Background information about my system:
RaspberryPi 4:
Setup run fine and my HUB + Cat Flap got published into MQTT in HASS just fine as well.
In my cat flap I've 3 options as switches
Curfew
KeepIn
andKeepOut
. All three aren't enabled yet by default.I tried to hit any of those switches and got this error in PHL:
Start up logs:
After pressing any Switch:
I cleaned the log.
In the MQTT logs I get this:
I'm kinda lost, and I've no clue where to debug, as it seems to work for you guys.
Maybe someone can help me with that or at least point me in a direction if it's my MQTT Broker or PHL.
Thank you
The text was updated successfully, but these errors were encountered: