Homeyduino: setCapabilityValue does not change Homey state?

[Satoer]

Hi, I have a simple homeyduino project. And I want to change a capability state in Homey. But Homey does not change the state.

In the setup I have:
Homey.addCapability("onoff", AlarmOnOff);
And this works fine to trigger the arduino.

But when I try to set the capablility inside Arduino and want to change the state in Homey, noting happens.
I tried:
Homey.setCapabilityValue("onoff", false);
or
Homey.setCapabilityValue("onoff", 0);
or
Homey.setCapabilityValue("onoff", "0");
None of them seem to change the state of the tile. What am I missing?

[rindler]

Homey.setCapabilityValue(“alarm_smoke”, (bool) false); works for me.

[robertklep]

Are you calling Homey.loop() from inside the loop() method? Have you called setClass()?

[Satoer]

@robertklep

Are you calling Homey.loop()

Yes (otherwise control from Homey would not work either)

@robertklep

Have you called setClass() ?

No, is this mandatory? According to the usage guide it defaults to “other”:

If your device is of a certain class then you can set the class by calling Homey.setClass("<class>"); from within setup() . By default the class is set to “other”, which means that none of the special features that certain classes provide are enabled.

I’ll set the setclass and report if it makes a difference.

@rindler

Homey.setCapabilityValue(“alarm_smoke”, (bool) false); works for me.

I shall try this syntax. Maybe “onoff” isn’t settable? (according to the documentation it is).

[Satoer]

@Satoer

@robertklep

Have you called setClass() ?

No, is this mandatory? According to the usage guide it defaults to “other”:

Well… it turns out it is. if I add:
Homey.setClass("socket");
it works…
But also when I change it to:
Homey.setClass("other");
So it does not default to other even when the documentation stated this.

[robertklep]

@Satoer

So it does not default to other even when the documentation stated this

Looking at the code, it does.

[Satoer]

Then I think it’s some kind of capability caching inside homey even though I removed the device and re-add it. (I did not change the name of the device). If I block out the setclass instruction (basically the old code again) it keeps on working… weird. Ill keep it to “socket” just to be safe.