Oh sorry @Masssssy, hadn’t noticed your edit until now.
Sure there can be differences between used APIs. There seems to be no on mode, so for my lights I have to use movie mode to turn on. Perhaps your lights don’t support it.
Please ensure all your devices are up to date, please turn your refresh on (if not already), link your mode channel and note, which mode is shown when your device is powered on. You can send this mode as String to the channel then to turn your lights on.
Only tested a little bit but it seems the “Dimmer” works for both turning on and off the light.
Using the switch however does only turn it off, then it has to be started again with the dimmer.
It seems that the one that fully responds runs mode “movie” while the other one runs “effect”. I’m not sure what the difference is to be honest. The official app says effect and both run the same firmware version. Maybe effect = shades of white only for the “gold” edition?
Seems one improvement here could be for the binding to use on/off events for the dimmer. Then the switch could be scrapped altogether. Right now I can only dim using google assistant, not turn on or off.
I assume so… my device seems to ignore the effect mode.
Probably you could create a virtual Switch with a rule to send effect to the mode channel if turned on and off if turned off. You can also use a classic command options button for your sitemap (required options will be autofilled):
Sure, I will play around with it a little bit. I’m not sure if you saw the last thing I added about Google Assistant.
Now if I would add the switch I would only be able to turn on/off. If I add the dimmer I would only be able to dim, not turn on/off. The optimal would be to bind the dimmer to Google Assistant but then the binding would have to be changed to use these on/off events I think.
Because I do not need to care if it’s movie/effect when using the dimmer slider. It simply works on both devices. If that could be sorted out I think the experience would be better I can see if I have to to have a look as well some day. Time is rare…
rule "Gold Switch"
when
Item GoldSwitch received command
then
if (receivedCommand == ON) {
GoldMode.sendCommand("effect")
} else {
GoldMode.sendCommand("off")
}
end
Sorry, I couldn’t reproduce your issue on my setup. My main server is stable after many restarts, long runtime, plugging and unplugging the lights. On a clean OH 3.2 it starts with offline lights without any issues.
This binding is pretty basic and I’m not aware of any possible conflict with OH core.
Uninstalling the binding should not leave any junk behind.
As I’ve read, you had some other small issues, maybe the impossible stuff combined
If anyone else encounters the same issue, please enable debug and send me an excerpt.
Strange thing…
What happened was that I cleared away X-mas so the Twinkly became offline.
A few days later, when I was hit be JJS OOM error, I did the first reboot after removing Twinkly.
I tried numerous reboots, power-cycles. Upgraded to latest snapshot, downgraded again, because the snapshot is unstable. Many restart once again.
Always ended up in the same state:
213 │ Active │ 75 │ 3.2.0 │ openHAB Core :: Bundles :: Thing XML
214 │ Active │ 80 │ 3.2.0 │ openHAB Core :: Bundles :: Transformation Service
215 │ Active │ 80 │ 3.2.0 │ openHAB Core :: Bundles :: UI
216 │ Active │ 80 │ 3.2.0 │ openHAB Core :: Bundles :: UI Icon Support
217 │ Active │ 80 │ 3.2.0 │ openHAB Core :: Bundles :: Voice
218 │ Active │ 80 │ 3.2.0 │ openHAB UI :: Bundles :: Main UI
225 │ Active │ 80 │ 1.0.0.201802012106 │ org.osgi:org.osgi.service.jaxrs
226 │ Active │ 80 │ 1.5.0 │ ThreeTen-Extra
227 │ Active │ 80 │ 1.27.0 │ SnakeYAML
228 │ Active │ 80 │ 2.1 │ SI Units
229 │ Active │ 80 │ 2.1.0 │ SI Quantities
230 │ Active │ 80 │ 4.2.1 │ Stax2 API
231 │ Active │ 80 │ 2.1.2 │ Units of Measurement Reference Implementation
232 │ Active │ 80 │ 2.1.0 │ Units of Measurement Common Library for Java
233 │ Active │ 80 │ 1.4.18 │ XStream Core
234 │ Active │ 80 │ 3.2.0.202112051225 │ openHAB Add-ons :: Bundles :: TwinklyTree Binding
235 │ Starting │ 80 │ 5.9.0 │ jna
236 │ Resolved │ 80 │ 5.9.0 │ jna-platform
237 │ Resolved │ 80 │ 1.6.2 │ JavaMail API
238 │ Resolved │ 80 │ 1.0.1 │ IO.Socket Engine Client
239 │ Resolved │ 80 │ 1.0.1 │ IO.Socket Socket Client
240 │ Resolved │ 80 │ 20180813.0.0 │ JSON in Java
241 │ Resolved │ 80 │ 5.2.1 │ nrjavaserial
242 │ Resolved │ 80 │ 3.7.2 │ Apache Commons Net
243 │ Resolved │ 80 │ 3.8.1.1 │ Apache ServiceMix :: Bundles :: okhttp
244 │ Resolved │ 80 │ 1.13.0.1 │ Apache ServiceMix :: Bundles :: okio
245 │ Resolved │ 80 │ 2.0.0 │ Californium (Cf) Core
246 │ Resolved │ 80 │ 2.0.0 │ Californium (Cf) Element Connector
247 │ Resolved │ 80 │ 2.0.0 │ Californium (Cf) OSGi
248
As soon as I disabled the Twinkly addon in the GUI, the system jumped to life (live, no restart, just Twinkly disable), rule engine started, but many addons was still inn the Resolved state.
One thing I wonder: why did the Twinkly addon start so early, long before the other addons?
(Can’t check now since I have uninstalled it)
Since my Twinkly is now in the Attic, it is a topic for the next X-mas season
I’m still in for the coincidence theory. Bindings stuck at Resolved seems to be a known issue on old setups / upon migration: link, link, link. Perhaps the addons had been resorted upon upgrade so this binding was started before its dependencies. I don’t know… but I do hope I will be there next Christmas and able to provide you any support
Hi @Koechi
You might need to send another command to your mode Channel instead of using switch.
In your sitemap you can create a new cell with Send Command action for this Channel, which should probably be on or effect
rule "Twinkly Strings On"
when Item TwinklyString_Onoffswitch changed from OFF to ON
then
TwinklyString_Modeselection.sendCommand("effect")
end
rule "Twinkly Strings Off"
when Item TwinklyString_Onoffswitch changed from ON to OFF
then
TwinklyString_Modeselection.sendCommand("off")
end
Now it works
With the sitempap it is possible to turn it off and on too:
if you follow the link above, you will find the full API.
As of now, only API calls listed as channels are supported, Alexa should work for the switch (or you might need to create a dummy switch if you need to send another mode):
You should be able to set the mode with mode channel. According to the API:
Hardware can operate in one of following modes:
off - turns off lights
color - shows a static color
demo - starts predefined sequence of effects that are changed after few seconds
movie - plays predefined or uploaded effect. If movie hasn’t been set (yet) code 1104 is returned.
rt - receive effect in real time
effect - plays effect with effect_id
playlist - plays a movie from a playlist. Since firmware version 2.5.6.
This release is compiled on OH4.1.0-SNAPSHOT and tested with OH4.0.4-STABLE.
Due to migration to OH4 some issues are possible, feedback is very appreciated!
To test it, you need to uninstall the marketplace version. Then download and copy the jar file into the addons folder of your Openhab nstallation. You will need to recreate your Thing to be able to use a new Color channel (Items can be kept and relinked again later).