MQTT-Explorer VS hass-workstation-service

Quote from MQTT Explorer

Sounds like you're on a good path tracking the problem to aws, not the esp. First of all, I'd try to make it work with a "proven" solution, then move on to your own implementation. I have had good success using http://mqtt-explorer.com/ on windows to diagnose a similar situation. Mqtt explorer gives you very granular control over endpoints and topics, so might be helpful to you too.

I would suggest using Mqtt explorer (http://mqtt-explorer.com/) to see how often the sensor updates its values. This as a first step to narrow down the problem.

Here are a few alternatives: http://mqtt-explorer.com/ https://mqttx.app/

Use MQTT Explorer to view and generate messages: http://mqtt-explorer.com/

For MQTT debugging, I like MQTT explorer

You can write test programs to send very specific messages to simulate errors, or simulate entire components that aren't written yet. There are also free programs like MQTT Explorer that will let you browse the message traffic, generate messages manually, log whatever you cant, and even graph your values if you happen to send numerical values (that is really cool when you do some long-term testing).

To use a local server can let you control all details of your full messaging chain. Try other clients can make you away from the ill behaviors or bugs of specific client. I recently demonstrate how easy a free MQTT client (MQTT explorer) send to a free MQTT database on Windows 10 in my video.

A useful tool is MQTT Explorer. You can connect to your broker and see what changes when you use the light through an app or switch or whatever. This should help you understand the manner in which the light talks with mqtt. Once you think you have understood it, you can use explorer to publish test messages to see if it works as desired.

Using Hass Workstation on my desktop and laptop

I use Hass Workstation Service to do that. I configured it to detect when the mic and/or webcam were being used and automate certain actions from Home Assistant

I'm using hass workstation service. The last release included my PR to make a sensor showing what programs are using your microphone. It's now deprecated, but still the only windows program that says WHAT is using the microphone. So my automation runs when that sensor string includes "Teams.exe" or "zoom.exe"

I run HASS Workstation Service on my computer to upload data about my computer's sensors to Home Assistant. When I turn on my computer microphone, the IKEA switch connected to my desk fan turns off automatically

I'm using Hass Workstation Service to achieve this: https://github.com/sleevezipper/hass-workstation-service

I use the HASS workstation service (https://github.com/sleevezipper/hass-workstation-service) for this - it publishes various state entities to HA and I use that to drive the state of a coloured light. I use mic on, video on as the primary drivers for orange or red light, and then time for other colours.

For Home Assistent there is a great software that transmits your PCs microphone and webcam status to HA - https://github.com/sleevezipper/hass-workstation-service

For the automation I use HA with node-red and HASS Workstation Service to detect when mic and webcam are active. When mic only is active, the green light turns on, when the webcam is active it turns red (thanks to u/plasticarmyman for the idea).

I do something similar but using HASS Workstation Service. I detect when the mic is active (which 99% of the times happens when I'm on a meeting) and then change some lights.

No link to original content anymore.. But you can do a bit similar setup with Hass workstation service. https://github.com/sleevezipper/hass-workstation-service If mic or webcam is in use then light goes red. Doesn't take any other statuses, but works for meetings quite fine.