wbravin
(william bravin)
August 25, 2024, 5:31am
1
Hello all
During the last month i had several issues with my home server environment.
I have HAOS running as a vm on proxmox. (all updated)
I have aeotec multisensors 6 that controls shelly lights.
In the past motion was detected light turn on within a slit second (perfect).
Since rebuilding my zwave and my shelly environment i have issues. (maybe the heat is causing ghost to appear in my environment LOL)
Now the motion sensors work and the lights work.
However when motion is now detected the light turn on after 4 - 6 seconds. (Not good)
I do not see any settings in the multisensor of the light that could cause this
Please help guide me on how to trouble shoot
Thank you for your help
wbravin
(william bravin)
August 25, 2024, 9:29am
3
@nickrout
Thank you so much Nick for your prompt reply. This is part of what makes HA great.
In my node red flow I had both selected the device and the entity for the light to be turned on.
I removed the entity and left the device name in place and I increased the level of luminosity high enough to cause the flow to activate an all seem to be back in excellent working order
once again thank you for your help
wbravin
(william bravin)
September 8, 2024, 8:17pm
4
@nickrout
Hello Nick for the most part all is working fine.
However once in a while the symptom described above still reappear for no reason.
once i need this automation again it works fine (without doing anything)
How can i diagnose this issues? (the logs do not say anything constructive)
Thank you
nickrout
(Nick Rout)
September 8, 2024, 9:10pm
5
Sorry, I have no experience with node red.
rodak
September 8, 2024, 9:23pm
6
Are you using gen 1 Shellies?
Integrate Shelly devices
wbravin
(william bravin)
September 9, 2024, 3:57am
7
Hello all
Thank you for the quick response
Yes most of my lights are gen 1 and have their firmware updated
Again thank you
rodak
September 9, 2024, 5:41am
8
You said this, do you mean you reset your Shellies? If yes, have you checked your Shelly settings according to the link I posted?
wbravin
(william bravin)
September 9, 2024, 7:32am
9
@rodak
Yes i did resbuild my zwave solution and i did re-set all the shelly lights at that time.
The CoIoT peer is enabled and mcast is selected
Thank you for your help
nickrout
(Nick Rout)
September 9, 2024, 9:37am
10
So you don’t have it configured as recommended. You should try …
1 Like
rodak
September 9, 2024, 10:28am
11
Then try unicast as suggested.
Type ip of your Home Assistant server and the port (5683).
I have some gen 1 lights and they respond instantly with those settings:
Also make sure that your lights actually can reach the server/port in your firewall.
Prior activating unicast I had similar delays as you are describing.
wbravin
(william bravin)
September 9, 2024, 10:58am
12
Thank you folks for your recommendations.
I have amended it to read my HAOS IP:8123 and rebooted all the lights
See how it will perform tonight
Thank you all again for your help and patience
rodak
September 9, 2024, 11:02am
13
Still wrong, will not work, please use the correct port 5683 and reboot the lights again.
nickrout
(Nick Rout)
September 9, 2024, 11:14am
14
Hard to have patience with someone who has been repeatedly referred to docs, but doesn’t read them.
wbravin
(william bravin)
September 9, 2024, 1:48pm
15
Sorry folks
I have a problem to read because of my mental issues. I do not do it out of laziness.
Once again sorry
rodak
September 9, 2024, 5:37pm
16
No worries, did you update the settings to the correct port?
wbravin
(william bravin)
September 9, 2024, 9:00pm
17
hi folks
yes i did. i changrd the ports to 5683 as mentionned and all is workin well thank you.
BTW it was also working with the ha port 8123 maybe this was just luck.
thank you once againfor understanding.
you all be well now
1 Like
nickrout
(Nick Rout)
September 9, 2024, 9:14pm
18
I’m sorry to hear that. Sorry if I was too blunt.
wbravin
(william bravin)
September 9, 2024, 9:50pm
19
@nickrout
No worries mate. it happens when one gets older LOL