Why is DMR Net now yellow?
Posted: Fri Mar 12, 2021 4:38 pm
If its yellow, one or more of your DMR Services is failing to login, if you are using BrandMeister, make sure you have your hotspot security password set in BM Self Care.
My Pi-Star "DMR Net" status on the hotspot goes from green to yellow. I verified it's the same Hotspot Password that I setup last November. When I apply "DMR Configuration" changes, the status goes back to green and later on back to yellow. I did this a few times. Do we need to update the Hotspot password periodically?
KE7FNS wrote: ↑Thu Mar 18, 2021 8:52 pmNo, you do not.
You do not have to go back and reset any passwords.
If Pi-star is detecting issues with your connection to a DMR master, it will display the yellow warning indication. That doesn't automatically mean there is an issue with your password, as it might be network issues with your specific ISP, or problems at the DMR master itself that are completely out of your control.
For anyone else reading this:
If you see it is yellow, and have NOT entered a hotspot security password, then enter a hotspot security password as it is now required.
If you see it is yellow and have already entered a hotspot security password previously, then there are network issues. If the issue resolves itself then the yellow indication will go away on its own.
If you are super impatient you can try changing to a different master and see if that solves the issue.
I agree. A check within the 5 lines needs to added to the function:f1rmb wrote: ↑Thu Mar 18, 2021 10:27 pm Not entirely true, as the new function checkDMRLogin() is wrong by design: it's checking if a disconnection has happened in the last 5 lines of the log (MMDVMHost or DMRGateway), but it doesn't check if a reconnection did happened afterward.
So, "yellow" state can falsely remains on screen for a while (even longer while using DMRGateway).
In the DMRGateway case, that's a real problem, as alsmost only connection/disconnection events are logged.KE7FNS wrote: ↑Fri Mar 19, 2021 1:28 amBy using simple deductive reasoning you already know it reconnected. When it reconnects then the log is going to contain new entries pushing the disconnect message past the last 5 lines so it will no longer be true when checking for the existence of that message.f1rmb wrote: ↑Thu Mar 18, 2021 10:27 pm Not entirely true, as the new function checkDMRLogin() is wrong by design: it's checking if a disconnection has happened in the last 5 lines of the log (MMDVMHost or DMRGateway), but it doesn't check if a reconnection did happened afterward.
So, "yellow" state can falsely remains on screen for a while (even longer while using DMRGateway).
Code: Select all
W: 2021-03-18 12:16:37.077 BM_2081_France, Login to the master has failed, retrying login ...
D: 2021-03-18 12:16:47.299 BM_2081_France, Sending authorisation
D: 2021-03-18 12:16:47.494 BM_2081_France, Sending configuration
M: 2021-03-18 12:16:47.659 BM_2081_France, Logged into the master successfully