@DigiH Thanks! Last thing. I see that the instructions require a Mac to get the IRK of the device. Are there any other methods for those of us without a Mac?
Let us know how you get on with these instructions
but I have to admit I havenât personally tried any of these myself so far.
For the Theengs Gateway integration the IRK would need to be in base64, which you can convert from any hex format you might get with an online converter.
Hi again!
I recently had to switch my govee lights integration to govee2mqtt, as there was a required component that interfeered with another integration (roborock). Now all of my Govee sensors are being picked up by govee2mqtt, but the Smart Air Quality Monitor only displays the temp and humidity, no pm2. I know that this is supported by theengs, but I am unsure if the govee2mqtt integration is causing an issue with theengs being the preferred integration since it supports all of the deviceâs parameters. Is there any way to ensure that is the case, or is this a conflict between the two mqtt integrations?
I donât have any experience with the govee2mqtt integration, but I would think that you do get two distinctly separate auto-discovered MQTT entries for them. Just make sure you only;y use the Theengs one and you should be fine.
It did re-appear in mqtt eventually, but still via the govee integration. Not sure if its limiting the device to only one integration method because of a common MAC address.
Edit: I just noticed I had â[IBEACON]â still in the filter. Removing it and restarting HA just put it back into my dashboards.