Securifi Community Forum
Sensors and Home Automation => Home automation => Topic started by: btosch on August 19, 2014, 02:50:55 am
-
This gets detected as an unknown device and does not work. It was working with my MiCasaVerde
-
Another one we haven't tested.
Can you do me a favour and go to Help, Send Logs and send a log where you include the name of the sensor in the text box provided and we'll see if we can't figure this one out, as we do support Z-Wave dimmers.
-
I sent the logs. It took several tries to add it again with removes in between.
-
I have the same problem I have the HA02 and the HA03. The HA02 which does not have dimming ability recognizes as a alarm and you can turn the light on and off from the Almond+ but you can't do it from the app. the HA03 plain just does not work. It comes up as an unknown device that you can set the setting of 1,2,3 etc on but I think that is referring to the dimming level. Hopefully you can resolve this issue soon!
Thanks
-
We'll have some Z-Wave bug fixes in the next firmware which we're hoping to have out next week. This should fix the HA02, not sure about the HA03.
-
The HA03 adds and shows up as an unsupported device. I can set it to 0/1 on the device UI but nothing with the web ui and it cannot be added to rules.
-
It's not something that's for sale anymore, so not sure if we can add support for them.
It should just be another dimmer, but apparently not.
-
I have several of these and they're not working for me either. Would love to see support for this.
-
I too have several of these. I hope you can add support for them.
-
I also agree that support for these switches should be added.
While they are no longer in production, there are tons of them out there (I still have a few myself). If people want to migrate their existing system over to Almond, it makes sense to ensure that these folks are as accommodated as possible. The last thing you want is for people to have significant issues moving their (expensive) Z-wave environment over to Almond, and finding out that X% of their modules aren't supported.
-
...The last thing you want is for people to have significant issues moving their (expensive) Z-wave environment over to Almond, and finding out that X% of their modules aren't supported.
100% for me. This was actually why I bought the Almond+ in the first place...
-
Well, they're no longer for sale, so it's going to be really hard for us to add support for them, as for whatever reason, they're not using the standard dimmer command class that the other dimmers we support use.
If one of you is willing to give one up for the cause, we can add support for it.
-
Lars, I'd consider doing it if no one else steps up. Where should I send it?
How about this: I'd swap you an HA03 module for a Peanut.
-
If these are using the same Z-Wave profile as the in-wall dimmers, they should start working once we add those, otherwise we might take you up on your offer.
-
Let me know. I'd really like to salvage these things.
-
I have quite a few Intermatic devices I've found that the HA03 is Recognized and Usable from the ALmond + but the website displays it as an Unknown Device. I'm using the Latest Firmware R069cb BETA
-
I can confirm the same. It's moderately functional on the Almond+, not functional at all on either web or app.
-
Web is what? connect.securifi.com? or the local web UI on the Almond+ itself?
We have major updates coming to the apps alongside or shortly after the next firmware release which is this week.
-
Web is either connect.securifi.com or the local IP address. The device shows up and displays Get/Set fields under Connected Sensors on the Almond+. Looking forward to the next round of updates!
-
Ah, get/set means it wasn't detected properly, so that's why it doesn't show up properly in the other UI's.
Fingers crossed these work in the next release, but I wouldn't be money on it if I was a gambling man...
-
I can confirm no improvement with Firmware R070. :(
-
Very strange, we've added support for all the dimmer profiles we're aware of for Z-Wave, so I'm not sure what Intermatic has done in this case.
We support multiple different types of plug-in dimmers and in-wall dimmers. As I can't find the details of the device class for this product, I can't even ask if that type is supported or not.
What I'd need is the basic class, generic class and specific class for this device and then I can at least find out if it's something that should be working or not.
I presume you've removed and added it back after updating to R070? We can't re-detect something that has already been connected to the Almond+ when a firmware update has been done, so the device has to be removed and added again.
-
I not only added and removed one module, I added a second with the same firmware. Same results--recognizes that something is there, but comes up as an unknown device with get/set fields. I don't know if the manual would help, but here's a link: http://www.jclautomation.com/docs/1181.pdf
I can give you the FCC ID, but beyond that there's not a lot of info on the device.
Edit: Here's what a search on the FCC ID turns up: https://apps.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=791561&fcc_id=DGZH0003
-
Sadly that's of little to know help when it comes to knowing the Z-Wave classes for the device, as these are generally not mentioned in the sensor documentation. :-\
-
Well, let me know where to send a module and I'll sacrifice one for the cause. Or, preferably, swap you for a Peanut. ;)
-
Let me see what we can do.
-
Hey Lars, any progress on this?
-
Sorry, I've been on holiday and managed to get sick at the same time and I'm off to Europe for two weeks now. I'll pick this up once I get back.
-
Is this dead in the water? Ever hopeful the HA03 will get some love...
-
Well, whaddya know...HA03 now works with R076! Sweet!