dale3h / hue-mqtt-bridge Goto Github PK

Would be great to be able to have config.json file somewhere else instead, by specifying an option argument or have hue-mqtt-bridge looking in default *unix folders such as /etc or such.

Hello,

is it possible to change the port of the mqtt server? xxx.xxx.xxx.xxx:1234 does not work.

Greetings

Daranto

followed the instructions
when running command
./bin/hue-mqtt-bridge
it produces and repeats the following error
"MQTT Error: Error: premature close"
running homeassistant not hassio on raspberry pi 3
any solutions?

Hi,
I've been using this on my laptop running ubuntu 16.10 and it's working great. Can't fault it!
However, I've decided it's time to move to a RP3.

Having set it all up the process runs fine when I run the command: ./bin/hue-mqtt-bridge

It also runs fine when I run the command: pm2 start index.js --name hue-mqtt-bridge

When I then listen for the topics using: mosquitto_sub -h localhost -p 1883 -u pi -P raspberry -v -t '#'
nothing gets returned. I set it up exactly the same way as on my laptop so I'm a bit stumped. I've double checked the config.json settings - they also use "pi/raspberry" log in details and the hue username is definitely the same as in phue.conf

Is there any way to find out what's going wrong?

Hue Motion sensors seem to not be fully working using hue-mqtt-bridge when integrated into Home Assistant. The sensors values are pushed on the brokers but the binary_sensors are not updated into HA.

Everything ran nicely for some time after #12 was fixed. Now suddenly the problem seems to have come back. I've set up logging to see what happens this time. As there isn't anything else on the state as buttonevent and lastupdate my guess is the fix requires checking the timestamp in some way as suggested by @danpowpow on #12 discussions.

Assuming an old timestamp is returned, comparing it to the server time to decide if a message should be published is not without its issues:

• timestamp sent by the hub does not seem to be timezone adjusted
• using the timestamp as part of the code would assume both the hub and server/computer have time/timezone in sync

A simpler approach would be to only compare if the lastupdated value has changed as the switch seems occasionally trigger two events with different buttonevent values + occasionally some scene cycle events. This will only work though if the lastupdated on the ghost trigger is the same as the previous one. I'll update when I get it caught on the logs. This has been occurring 1-3 times a day during the last week so it should not take too long.

I updated hass to 0.40.0 and now the bridge doesnt work anymore. hue is reachable username still the same but when watching mosquitto or if i start the bridge manually .. no hue dimmer clicks are recognised :(

I was looking for a stand-alone application and thought this was a good fit until I got down to the installation section of the readme where is says it requires Home Assistant (I'm not running HA so useless for me). It's a HA plugin/module so this should be stated in the description or at least the first line of the readme.

I recently added a 4th and 5th dimmer remote to my hass system. Your bridge has been working flawlessly, but now one of the new remotes (number 4) is listed in the mqtt flow as being pressed everyone or 5 minutes.
Interestingly the last_updated message has the correct timestamp (ie I will get a pair of messages, the 'button event'and directly after a 'last updated', but the last updated will show a time in the past which correlates with the last physical button press)
I removed the new remotes and found that things calmed down for a day, but then the error / fake events switched over to an older remote!
I've disabled your bridge on my pi hass and setup a separate pi3 with the latest node (8.9.1?) and only your bridge on it. The problem remains.
I've tried renaming the remotes in the hue app. The name change is reflected in the mqtt flow, but I'm still getting random firings. The hue app shows no extra activity.
I've deleted and re-added the remotes in the hue app numerous times but that isn't helping.
The new remotes I've added have different printing on the back, but the same model number. Here's a link to an image:
https://drive.google.com/file/d/1MxXZlZdiyxURuGdWOE7bEWmu2KstOcy8/view?usp=drivesdk
Can you advise where to look for logs, or suggest what could possibly be happening? I'm stumped, and my lights keep turning on and off!

I'm running my mqtt broker on a non-default port. The hue-mqtt-bridge has port 1883 hardcoded. Can this be made configurable ?

Hey,

it would be cool, if you'd create a addon repository, (Someone already built a docker image https://hub.docker.com/r/ajclarkson/hue-mqtt-bridge/) It would make it much more easier to install.

Furthermore I have some problems with the used mqtt protocoll version. When I try to use the delivered pub / sub client hass.io always tells me, that I come with version 3.1. Hass.io naturally delivers version 3.1.1 and seems not to be compatible backwards.

Have a nice day,
Pascal

Hi,

I use this Docker repository with your service (https://hub.docker.com/r/ajclarkson/hue-mqtt-bridge/) to use with my Home Assistant and now this service are stoped after 10 minuts after run it..., today I updated my HUE Bridge firmware to v1801260942, do you know if with this firmware we are some incompatibility?, Its possible?

Thank you.