Sonos remote VD 1.0.1 just stopped working

[AndyHam 2]

Hello!

 

I've been using this VD for 2-3 years without any problem. Everything has worked perfectly until yesterday.

Nothing in the setup has been changed, neither the network.

 

The IP is correct and the port 1400.

 

when i debug the Play button it first gaved me following error: line 5: attempt to index local 'f' (a nil value) [

the VD shows that the speaker is stopped and if i hit play on the Sonos remote APP, then the state will change to Playing and will also show wich station.

So the VD have some contact with Sonos.

 

But i cannot do anything in the VD, Stop, play - nothing works.

 

Then i searched the forum and someone said, delete the x_sonos_object variable and install the VD again.

So i tried that, but the VD doesn't create the variable again.

 

I tried to manually create the variable but then i receive:

 

[DEBUG] 09:00:25: No data found!
[ERROR] 09:00:25: line 5: attempt to index local 'f' (a nil value)
[ERROR] 09:02:53: line 5: bad argument #1 to 'len' (string expected, got nil)
[ERROR] 09:03:03: line 5: bad argument #1 to 'len' (string expected, got nil)
[ERROR] 09:05:33: line 5: bad argument #1 to 'len' (string expected, got nil)
[ERROR] 09:08:59: line 5: bad argument #1 to 'len' (string expected, got nil)
[ERROR] 09:13:58: line 5: bad argument #1 to 'len' (string expected, got nil)
[ERROR] 09:18:35: line 5: bad argument #1 to 'len' (string expected, got nil)

 

I also read that it could have to do with a new sonos update?, that the API has been closed by sonos?.

Really hope that it can be fixed, i have a sonos speaker in each room and by movement sensor i turn on the speaker automatically as long there is movement in that room, but now it's so quiet in my house :(..

 

Thankyou!

 

[AndyHam 2]

12 hours ago, AndyHam said:

Hello!

 

I've been using this VD for 2-3 years without any problem. Everything has worked perfectly until yesterday.

Nothing in the setup has been changed, neither the network.

 

The IP is correct and the port 1400.

 

when i debug the Play button it first gaved me following error: line 5: attempt to index local 'f' (a nil value) [

the VD shows that the speaker is stopped and if i hit play on the Sonos remote APP, then the state will change to Playing and will also show wich station.

So the VD have some contact with Sonos.

 

But i cannot do anything in the VD, Stop, play - nothing works.

 

Then i searched the forum and someone said, delete the x_sonos_object variable and install the VD again.

So i tried that, but the VD doesn't create the variable again.

 

I tried to manually create the variable but then i receive:

 

[DEBUG] 09:00:25: No data found!
[ERROR] 09:00:25: line 5: attempt to index local 'f' (a nil value)
[ERROR] 09:02:53: line 5: bad argument #1 to 'len' (string expected, got nil)
[ERROR] 09:03:03: line 5: bad argument #1 to 'len' (string expected, got nil)
[ERROR] 09:05:33: line 5: bad argument #1 to 'len' (string expected, got nil)
[ERROR] 09:08:59: line 5: bad argument #1 to 'len' (string expected, got nil)
[ERROR] 09:13:58: line 5: bad argument #1 to 'len' (string expected, got nil)
[ERROR] 09:18:35: line 5: bad argument #1 to 'len' (string expected, got nil)

 

I also read that it could have to do with a new sonos update?, that the API has been closed by sonos?.

Really hope that it can be fixed, i have a sonos speaker in each room and by movement sensor i turn on the speaker automatically as long there is movement in that room, but now it's so quiet in my house :(..

 

Thankyou!

 

I solved it!

 

Totally removed the current VD, then added it again and then it started to work.

Very strange, but as long as it works i'm happy

 

/A

[AndyHam 2]

2 hours ago, AndyHam said:

Strange, i thought i solved it by removing the VD and installing it again.

Even if the IP are correct, to that specific speaker it  turns on all speakers in system.. 

Feels like Sonos have made some changes?

 

2 hours ago, AndyHam said:

 

 

[tangman 0]

HI There, I have just come across this - did uninstalling and re-installing fix this ?