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
service runs for 1-5 minutes then crashes. #2
Comments
Debug output: haiku2mqtt -b mqtt://192.168.5.14 -v debug TypeError: Cannot read property 'publish' of undefined |
The following events are published immediately before/after the crash. haiku:20:F8:5E:E0:B5:9F/connected 1 |
I saw the same type of error running latest version using node red with node-red-contrib-mqtt-broker. |
Any progress finding a resolution? |
Still looking for a resolution or another solution to integrate Big Ass products with mqtt. chris@mfi:~$ haiku2mqtt -b mqtt://192.168.5.14 TypeError: Cannot read property 'publish' of undefined |
Interested in a free Haiku light to fix this? |
@pponce , were you able to resolve? |
Nope. |
Not an expert here so this may well be user error... A bit more background. My haiku devices are all lights. The mqtt server is Mosquito and is shared with a number of devices.
Let me know if you need any more detail. Below is the console output.
Chris
root@haiku2mqtt:/home/pi# haiku2mqtt -b mqtt://192.168.5.14
server listening 0.0.0.0:31415
/usr/local/lib/node_modules/haiku2mqtt/dist/index.js:53
client.publish(getTopic(device, 'connected'), '2', STATUS_OPTS);
^
TypeError: Cannot read property 'publish' of undefined
at SenseMe.setupNewDevice (/usr/local/lib/node_modules/haiku2mqtt/dist/index.js:53:12)
at SenseMe.emit (events.js:160:13)
at SenseMe._handleDeviceFound (/usr/local/lib/node_modules/haiku2mqtt/node_modules/haiku-senseme/dist/SenseMe.js:110:22)
at Socket. (/usr/local/lib/node_modules/haiku2mqtt/node_modules/haiku-senseme/dist/SenseMe.js:233:28)
at Socket.emit (events.js:160:13)
at UDP.onMessage [as onmessage] (dgram.js:658:8)
root@haiku2mqtt:/home/pi#
The text was updated successfully, but these errors were encountered: