Routing Info 0.1.1

Hi Jwi,

I ran it and was a little surprised. There are some that jump 3 or 4, even though it is very close to HC2. In addition, it does not have a battery.

2 Mobilus shutter motors have just been installed. It writes an error on these, stating that they are without a template. Could it have anything to do with it?

 

With the HC3 support for ZigBee that well know for routing issues it might be cool to have this related to used protocol , 

Hey there mate,

 

Just tried running your script - everything in my new HC3 network is reporting no neighbours and no routes...but it's all 'working' as a script run. Anything there that might be the cause?

Just noticed this also:
 

Last WRRT for device 134: 10:00:00  - 01 Jan. 70 

 

And crosschecking my swagger, it's not your script - it's reporting 'facts'...but that can't be right if everything is working can it?

 

 

Also, if you wanted to offer a version with english messaging, I threw your script at chatGPT and it replaced the german phrases quickly and accurately without changing the code - if not publishing a version in English, it may be a helpful suggestion to include in the description above? Whoops! I had gotten your script from a forum thread but redownloading it here gave me an English version....the issue above is still present though...

Edited November 17, 2024 by MrNoTip

On 11/17/2024 at 6:59 AM, MrNoTip said:

Hey there mate,

 

Just tried running your script - everything in my new HC3 network is reporting no neighbours and no routes...but it's all 'working' as a script run. Anything there that might be the cause?
..

 

Hi,

 

Have you ever found what was the problem with the script running it on a HC3?

I have the same problem over here...

 

Philippe

I did! ...if you have set up your HC3 to use the 3.0 zwave engine, at least. See the linked post.

If you interact via swagger or other API approach, you'll eventually find functions that 'work'  but don't actually work on the new engine. A lot does work, but the functionality behind this script certainly doesn't....but.....if you scroll right down to the bottom of the definitions list in swagger, you'll see a definition called 'Zwave engine API' and in there you will find wayyyyy more calls than you see in any of the other definitions.....they've basically put anything specific to the new engine into its own single category, even though the range of functions you will find there cuts across many of the other definitions in the list. I am not sure of any totally clear and complete doco on what works and what doesn't, but late last year I know I found some calls there that could be stitched together to do this kind of thing....way above my pay grade! But you could poke around in there and probably get this info on a device by device basis without too much technical know how....doing it myself is somewhere on the to-do list unless @jwi gives us an early birthday present and creates a new engine version of this script. (@jwi I know this is you doing stuff in your own time mate, so I understand you may just be sharing something you did for your own use....but the new engine users would be very grateful if you or someone else with the skills did find the time!)
 

On 1/4/2025 at 10:50 PM, Top Vlaanderen said:

 

Hi,

 

Have you ever found what was the problem with the script running it on a HC3?

I have the same problem over here...

 

Philippe

 

12 hours ago, MrNoTip said:

I did! ...if you have set up your HC3 to use the 3.0 zwave engine, at least. See the linked post.

If you interact via swagger or other API approach, you'll eventually find functions that 'work'  but don't actually work on the new engine. A lot does work, but the functionality behind this script certainly doesn't....but.....if you scroll right down to the bottom of the definitions list in swagger, you'll see a definition called 'Zwave engine API' and in there you will find wayyyyy more calls than you see in any of the other definitions.....they've basically put anything specific to the new engine into its own single category, even though the range of functions you will find there cuts across many of the other definitions in the list. I am not sure of any totally clear and complete doco on what works and what doesn't, but late last year I know I found some calls there that could be stitched together to do this kind of thing....way above my pay grade! But you could poke around in there and probably get this info on a device by device basis without too much technical know how....doing it myself is somewhere on the to-do list unless @jwi gives us an early birthday present and creates a new engine version of this script. (@jwi I know this is you doing stuff in your own time mate, so I understand you may just be sharing something you did for your own use....but the new engine users would be very grateful if you or someone else with the skills did find the time!)
 

Thanks for your reaction!