Ad blocker detected:
Our software and support is 100% free. This website is not.
You can donate in 2 ways, by turning off your ad blocker or by pressing the Donate button.
************ NOTICE ************
UPDATE YOUR BOOKMARKS!!!
We have an issue that there is no way around as of yet.
I have done all I can to try and prevent this from happening.
We are going to be losing the .com, .org and .de domains.
We have not been able to contact the original author of EventGhost
(the person that owns those domains) to redirect them to the new web server.
I set in motion when we first moved a redirection from the old server to the new server.
I also put in markers so that search engines would see this change and update any pointers
they have. We still have the .net domain for the production site. and the .rocks for the test site.
For the past few months you have been getting redirected to the .net site if you used one of the 3
domains mentioned above. I just wanted to tell everyone so they can make any changes needed.
that's not possible, if your broker is installed on your RPi it means it's listening on some port, I gave you the default ones earlier but maybe you have changed them ? what port is set in EG ? Are you sure your broker is installed on your RPi ? it looks like you are using an external broker and that your RPi and EG have subscribed to the same topic and communicate with each other through this external broker. What broker is set in your EG ?
I ran netstat on Raspberry PI and it showed me the port that it is listening to 1883 (default). So I guess this means that the server side is local and os running on the Pi.
EG also seem ok since I run the same settings: Pi's local IP address, default port, username and password, topic and , message.
So why does it take more then 2 seconds? This is driving me crazy. When I use the MQTT.FX as I sayed before, the command is recived almost instantly, although you must be connected to the the server and you can't just send a message and hang up.
Maybe that is because it's faster? because it is always connected?
raspberry pi's are not exactly the fastest thing in the world.
This is what I am understanding
you have EG set up on a PC and you have HomeAssistant set up on a Raspberry Pi.
Now. Raspberry Pi's are pretty handicapped in the resources department. And opening and closing ports does take some effort. HomeAssistant does take some time to do things if it is not a core process. it kind of gets placed on the back burner until i gets to it. so the opening and closing of a port is really going to take more time if you have HomeAssistant doing it. if you have an always open port connection the data being sent through it is going to be processed by HomeAssistant much faster.
Now you can test this and see if the issue lies with EG and the plugin or on the RPi side of things by setting up 2 instances of EG on 2 different PCs and have them send the message back and forth between them. and see if it takes 2 seconds. if it does not then the problem lies on the side of the RPi.
If you like the work I have been doing then feel free to