-
-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Priority route not visible with "star" #3492
Comments
But did you set that priority route manually or what? |
Yes we both added routes manually. We did mainly the same things. Just add some priority routes. I use those to have a more stable situation. Since I use priority routes it works better. My friend want those too but isn't seeing any "stars". I know that there are newer versions but my friend hasn't got any "stars" for months now. And I do. The only difference is I run a separate docker and my friend has the hassio addon. Very strange, we use the same version and the same hardware zwave dongle. |
This explanation alone doesn't give me enough context to tell you what's going on there, what I can think is that for some reason he did a route update and the priority route has been removed and it became a LWR route instead |
No, the priority route isn't removed. It's still there. But I see all small "stars" in the network graph view but in his network graph no starts are visible. |
I dunno, if your friend has such issue he should upload nodes json so I can give it a look |
nodes_dump.json |
The only one with an application route set is node 22 and it has:
Does he see the star on the link from 22 to the controller? I have a feel if he doesn't it could be because the nlwr mathes the application route |
He doesn't see any star, no stars at all. And when he sets more priority routes they don't stick. After he sets a priority route and leave the popup and click the node again the priority route is gone. Only on node 22 it stays. Setting priority routes is not going well and he doesn't see any star. Nodes with priority: |
I need driver logs that show the tries of setting a priority route |
zwave-js-ui-store.zip |
Them are correct. Thanks. I need to ask @AlCalzone to review them. Anywat could you also try to upgrade to latest ? 9.6.0? |
I only see a successfull try in logs and no fail:
|
I can't update to a newer version, because I use hassio addon |
Again, in my opinion it has nothing to do with the version because I use the same version in a docker. I see beautiful "stars". :-) |
@robertsLando how are the stars drawn? Are they text/emojis or SVG? Can we somehow confirm whether Z-UI sees the routes as priority routes? In other words, can we confirm whether this is a pure display issue? |
|
It's not only a display issue. The priority routes @jeroen84s is making are not saved. He can set a route (and back) but after closing the node and opening the node the priority route is gone. |
Ok I'll try to look at the logs tonight. Maybe I'll see something. |
@AlCalzone them are SVG and as said I don't see any error in the logs he uploaded above. Anyway IMO this seems to me a display issue but I may be wrong |
Not only a display issue!! I already said: |
@jeroen84s is showing that several communication attempts succeed using the priority routes, e.g.
and that several priority routes are known, e.g.:
Also, assigning the routes works too:
What might be happening: This node is a sleeping node, so there are no route statistics yet to draw the route. I think Z-UI isn't handling the case where there are no statistics, but the priority route is known. @robertsLando |
@AlCalzone Can you see the routes back also? The route back isn't shown in the Node when you open it again in the Network Graph after setting it. And why do I see "stars" and @jeroen84s not? I think it's all very strange. Why this complete other reaction than I have. I also set priority routes with sleeping Nodes. Also setting prio routes between Nodes with power (non sleeping Nodes) isn't displaying any "star". Am I the only one with visible "stars"? Lucky guy I am. ;-) |
The routes back require communication with the node, which doesn't happen when the node is asleep. It has to be woken up for the return route to actually be saved. As for routes to and from powered nodes: I need to see a log of that. |
Your vision about the sleeping nodes looks correct. Both wall plugs has a priority route (also return route). And the star in is not showing up in the graphic |
No stars. Maybe with Christmas. Just wait. ;-) |
I've never seen stars either. I saw the legend, but never knew what I was missing. My priority routes are still there when I drill down and the diagram has changed-- just no stars. All my priority routes involve powered devices. This is one of those features that is probably rarely used or missed. BTW, the 'Node properties' popup gets clipped by Daniel's donation footer. The [Ping] button is obscured. |
@nmpu can't you just drag the dialog a bit higher? it can be moved where you want |
@robertsLando yes, that does work. I'm not used to web dialogs being moveable. Pretty fancy. Once you know there's a [Ping] button, you can blindly click on the top edge. Should I also see stars in the app? I don't. The 'Show return routes' and 'Show priority routes' checkboxes get disabled in the global view, but are enabled in the node view. However, the previous state remains when grayed. Is that how it's supposed to work? |
The https://github.com/zwave-js/zwave-js-ui version has a star: |
star should be in |
This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this issue entirely you can add the no-stale label |
It's still not fixed in the latest release. Please fix. |
I sincerly have no clue how to fix this as it's working on all my instances |
The star.svg is not available in his environment. How can he fix this? |
I cannot help so much as the error seems to be on addon side, only @frenck could help here and I already tagged him |
This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this issue entirely you can add the no-stale label |
Please help us with this problem. @frenck isn't available??? |
I give up. My separate zwave docker is working fine. I see stars. My friend doesn't have stars in his HA zwave addon. If the developers of zwave and the HA addon are not able to fix it, I give up. |
@frenck says:
I can confirm that it does not work when packaged as the HA Add-on. |
The star svg path is passed in this way:
Same for the logo you see in top left corner: Line 18 in 37dfcd3
The logo is working and the star is not. So sincerly I dunno why the star request doesn't respect the X-External-Path. It could be that for some reason vis-network is loading it in a wrong way? |
Looks like |
it will be great if we can see the stars :-) |
I guess nobody is going to fix this for the HA addin users. Just run zwave separate in a docker and you can see beautiful stars. :-) |
@AlCalzone I was looking at vis-network code, wondering if using https://github.com/visjs/vis-network/blob/master/lib/network/CachedImage.js#L7 cold work. Let me try |
Works 🎉 |
Nice! i'm still waiting for an update via hassio add-on |
Hassio Addin Version 3.9.3 is available.
…On Tue, 6 Aug 2024, 17:29 hugo-leij, ***@***.***> wrote:
Nice! i'm still waiting for an update via hassio add-on
—
Reply to this email directly, view it on GitHub
<#3492 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXIR3XBO7ZTHNJAXQPLHUULZQDTXJAVCNFSM6AAAAABA4RGZIGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZRGU3TGOBSHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I see! uhm, the update is not (yet) available via home assistant. Hopefully, tomorrow |
My friend and I both have the same zwave-js-ui 9.3.2 version. I can see all the Priority routes, visible with "star" in the network graph. My friend isn't seeing any "star".
How is that posible?
The text was updated successfully, but these errors were encountered: