This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Closed Official
[App] Fibaro by Athom (v1.5.18)
This discussion has been closed.
Comments
I'm realy looking foward to this update so I'm able to include a lot of relay switches
it's just an educated guess, it doesn't change much of the internal coding (it's mostly all the same coding way), so not that much testing is needed before being accepted into the store.
While we're joking about it, they seem to have accept you pull request
https://github.com/athombv/com.fibaro/commit/dda3ad148276950902a6d30cdf11ba31282eac62
Hope it will survive their acceptance tests (assuming there are).
that's exactly the reason why i said today or tomorrow.
If the pull request wasn't accepted it would have been a longer periode
i'm not on slack, so no i was not aware.
But, really? i couldn't think of a way yet to make it work properly with both switches and outputs.
What do you use to "listen" to both multichannelnodes of the multilevel_switch command class
Maybe you can contact him to see if his method can be of help for your relays?
This is the list of classes you asked for a couple of days ago:
@caseda it is just a basic implementation (just up/down), but the multilevel_switch cc you speak of, are you certain the device supports this? I can not find it in the documentation, and neither does the device advertise it is capable of this cc.
ah i see, the FGRM-222 uses binary switch, definitely need to look at more repositories when trying to create drivers
I've been looking at the supported class shown on pepper and openhab, and they both use/say MultiLevel Switch cc when "controlling" the roller blind, this is for both the FGR-221 and FGRM-222
and got the node info from @viktor yesterday, from the FGRM-222 (Roller Shutter 2), and it also states:
and
so even homey itself is stating it when giving the node info (not the debug)
kinda weird it's different for the node_info (general device when no driver) and the debug log
It absolutely supports it, I used it like that before with my main controller (paired as a dimmer)
It also reports its percentage.
@Fire69 does it report is percentage on homey as well? As in, can you see that percentage incoming in the logging? If yes, what command class does it use to report this?
the multilevel sensor cc is a totally different command class then the multilevel switch cc.
The switch cc is ment for dimmer purposes (almost the same as Binary Switch CC, just uses different data types)
The sensor cc for multi purposes, like door/window contacts (which is called a sensor), and any data like temperature
but until now it seems like all command classes have been implemented.
I meant implemented in the driver @RobinBolscher made for the fgrm-222.
Yep, either by community or once we receive one at the office ourselves!
I haven't found a clear function for it so i haven't ordered it yet.
@Robin, in my case i might not need the S2 switch at all times (Fibaro single relay), how do i get rid of the S2 device in Homey?
What do you mean with superseded, makes no sense.
Fgrm-222 = fgrm-222 which has been implemented in 1.0.9.
That came in the app store yesterday
FGR-221 = Roller Shutter (so v1)
FGRM-222 = Roller Shutter 2 (and always been)
Dimmer is about the same:
FGD-211 = Dimmer (v1)
FGD-212 = Dimmer 2
So maybe just a re-package but the version is still 2.2-2.4 (2.5 only since shortly)
no expert either, but not really a simple user as well
Homey 0.9.3 app 1.0.9
@cnvisser can you run the app from command line and PM me the console logging?
EDIT: missed your mention of FGR. The app supports FGRM, not sure what the difference is yet.
I've been googling around, there is not that much information about it..
but seems like the FGR-222 is the newer version (v2.5) of FGRM-222 (v2.2 - v2.4),
included the device in my PR @Robin, needs to be a completely new device because the product type also changes, but its practically the same device