Closed realAkhmed closed 8 years ago
Hey realAkhmed
I think this is normal behavior. This generally happens when a z-wave device is first linked with Home Assistant. Usually, a generic ID is given to the device. For example, when I link some Aeotec Multisensors, they'll come up as sensor/multisensor1
. Once I restart HA, the proper entity ID is given, which is something like binary_sensor/aeotec_multisensor1
sensor/aeotec_multisensor1_temperature
and so on...
For more info, see a similar discussion on the forums: https://community.home-assistant.io/t/zwave-entity-names-changing-on-their-own/1476/2
I'm guessing once HA restarts, the light disappears because it is now recognisesd as a remote, and you should then be able to configure it as normal. I'm guessing it won't show in the device list, because it is a remote and not a sensor/switch.
@philhawthorne thanks for your reply! The issue is that once HA restarts there are no remote controls anywhere.
The entity_id page does not have any remote controls so there is no entity_id for the Minimote and it cannot be used for anything (unless I am missing something?)
Basically, minimote only appears inside HA entity_ids for a very brief period (until a restart) and only as a light.
Ah I see what you're saying
https://home-assistant.io/components/zwave/#aeon-minimote
So I'm guessing you can't see any device named like aeon_labs_minimote_1
etc?
Yes, aeon_labs_minimote_1
does not exist in the entity list and so does not work as a trigger.
Damn. Out of curiosity if you click a button on the remote, does an entity appear in HA?
Also, have you tried using Open Zwave Control Panel to see if the device is being recongized in that correctly?
Damn. Out of curiosity if you click a button on the remote, does an entity appear in HA?
Unfortunately, no
Also, have you tried using Open Zwave Control Panel to see if the device is being recongized in that correctly?
Yes, ozwcp recognizes it correctly. Your idea is interesting: it looks like it goes to sleep quite fast. And nothing I do seems to prevent it from moving to "Sleeping": the manual says to hold 'Learn' for 3 seconds -- this does not seem to work.
Thanks @philhawthorne! Your advice was perfect: what was needed is to go back to ozwcp
and play with it more.
The trick is twofold:
ozwcp
for the first time you only have a few seconds to click Configuration
and switch from Group to Scene. aeotec_minimote_2
and it will survive multiple restarts.The rest of configurations in configuration.yaml
is just about following the instructions above
automation:
- alias: Minimote Button 1 Pressed
trigger:
platform: event
event_type: zwave.scene_activated
event_data:
entity_id: aeotec_minimote_2
scene_id: 1
action:
service: switch.toggle
entity_id: switch.aeotec_smart_switch_6_switch_3
By the way, HA assistant would still not show any entity_id for Minimote on the "Entities" page. Nevertheless, all the scripts work and the console clearly shows that the events are acting as triggers correctly!
Thanks for the advice again! Took me my whole day off.
@realAkhmed glad I could help! Zwave and OpenZwave can be a bit tricky. I'm still learning myself, but glad you were eventually able to figure this one out!
Out of curiosity, why was this closed? I haven't seen any documentation added to address this, I needed to google search and finally found this issue (and the fix suggested here worked).
I haven't looked at everything open-zwave emits, but it seems like the steps above should be able to be integrated automatically into HA. Here's what I would expect:
It's quite likely/possible other devices will need similar things, so having HA automatically do it when adding seems much better than making people Google around for a solution.
Home Assistant release (
hass --version
): 0.20.2Python release (
python3 --version
): 3.4.2Component/platform: Raspberry Pi 3 Model B
Description of problem: Aeotec Minimote is misinterpreted as 3 lights by Home Assistant
Hardware:
Expected:
Minimote should be recognized as a secondary controller
Problem-relevant
configuration.yaml
entries and steps to reproduce:The basic
configuration.yaml
+ addedzwave
clause:zwcfg_xxxx.xml
correctly identifies node id=2 as minimote and remote controller. There are only 2 nodes in the xml (attached)zwcfg_xxxx.xml
consistently shows the presence of minimote.Traceback (if applicable):
Below is the traceback of everything that happens right after zwave/add_node is initiated
Additional info: