This object is in archive! 

Virtual switches do not work anymore (newly created)

Pascal Verstappen shared this problem 10 years ago
Known

Hi,


I have created a virtual switch. After creation it properly shows on the dashboard. I have synchronised after the creation as well.


When I now toggle the switch to 'On' via the dashboard, it sets itself back to off.


In order to ensure that no other rule (or whatever) is causing this I have created a new switch and synchronised again. This new switch has exactly the same behaviour.


Can you please advise?


Thx

Pascal

Replies (6)

photo
1

I had the same problem With a virtual sensor yesterday.

I created it and the tried to change it using the URL, but nothing happened.

Then just 5 min later after some additional tries it just started to work as expected... Strange!

photo
1

Same here.


(edit) Same here as in Virtual Switches doesn't change the state through URL.

photo
1

Hi,


So when you create a virtual SWITCH your state doesn't change using the URL.

I was already wondering since i thought this used to be there.

I just created a Virtual SWITCH but don't see URL at all, only an ON/OFF buttin (see attached)


What also happens (not always) is that if you create a Virtual Meter or Sensor (yes i do have http here) that after a reset or refresh of the control center the API suddenly dissapears. I have several meters that i used with IFTTT and XBMC where i copied those URL's in the configuration, but after sometime they stopped working and it seams that the API key is gone in the Control Center of these devices.


More starting to look like an unstable product where people have various issues with the same firmware.

photo
1

Slashroot,


Did you contact support about this? I'm having the same problems.

photo
1

Yes i have a ticket open but no answer yet

photo
1

I got this:


currently we have problem with newly created virtual devices, first state change is not recorded. However in your case looks like value on box was stuck on 13 and setting it again on 13 didn't do anything. I just changed it to another value and now it works.Both problems will be solved in the next firmware update (probably this weekend).

Leave a Comment
 
Attach a file