Timeouts when using getElementByPath in v0.2.2

[phillipivan]

When using version 0.2.2 I get timeouts when using the getElementByPath method, reverting to 0.2.1 the same code works ok.

This has been replicated connecting to two different Stagetec Ember Plus providers.

[mint-dewit]

Do you have more info about your usage of getElementByPath? Like what type of element are you using it on?

0.2.2 has made a change because the ember+ document is a bit ambiguous so it's possible your provider has interpreted in a slightly different way and is not responding to our request now.

[phillipivan]

Hi @mint-dewit, this is from the companion module which you have also worked on. I can test again tomorrow and take some more detailed notes, but I was trying both String and Integer elements.

[phillipivan]

Here is an extract from the logs when using companion module version 2.4.3 which uses emberplus-connection 0.2.2

Module-host accepted registration
debug: Connecting 172.20.146.247:9000
info: Connected to 172.20.146.247:9000
debug: Start parameter registration
debug: Attempt to subscribe to 1.2
debug: Registered for path "1.2"
error: Failed to subscribe to path "1.2.0.7": Error: Request timed out
error: Failed to subscribe to path "1.2.0.7": Error: Request timed out
error: Failed to subscribe to path "1.2.6.1": Error: Request timed out
error: Failed to subscribe to path "System.Firmware.Version": Error: Request timed out
error: Failed to subscribe to path "Audio.Processing.InputProcessing#15.Gain": Error: Request timed out

I don't observe any problems with these elements using 0.2.1

I have also attached the Ember Tree for the device exported from Ember Plus Viewer.

nexus-compact.zip

[mint-dewit]

I was trying both String and Integer elements.

So you are working with parameters. Maybe your device does not support getDir commands on Parameters which would be off-spec but not entirely unexpected. Can you try to do a getDir manually on one of your Parameters? Preferably you would also just have this library cloned and be able to add some console.log statements in the getElementByPath status.

Here is an extract from the logs

These logs are just output from companion, they are unfortunately not actually helpful in the development of this library :)

[phillipivan]

I was trying both String and Integer elements.

So you are working with parameters. Maybe your device does not support getDir commands on Parameters which would be off-spec but not entirely unexpected. Can you try to do a getDir manually on one of your Parameters? Preferably you would also just have this library cloned and be able to add some console.log statements in the getElementByPath status.

I can look at trying this, but wont be for a couple of weeks as I will be away.

Here is an extract from the logs

These logs are just output from companion, they are unfortunately not actually helpful in the development of this library :)

Of course.

[phillipivan]

Sorry for the delay. I created a fork where I could disable the get dirDir on parameters, and behavior returns to normal.

Perhaps this behaviour can be optionalised like I have done so in this fork. If this is an amenable solution I could create a PR with just this change (ie a client config option to defeat the behaviour).

https://github.com/phillipivan/sofie-emberplus-connection/blob/9cae20d3ae488f9d19366e6298930cc5a0d68151/src/Ember/Client/index.ts#L462-L466