Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

{x10_id} not set in MH 3.1 for X10MS motion sensors #474

Open
hollie opened this issue Oct 28, 2014 · 0 comments
Open

{x10_id} not set in MH 3.1 for X10MS motion sensors #474

hollie opened this issue Oct 28, 2014 · 0 comments
Labels

Comments

@hollie
Copy link
Owner

hollie commented Oct 28, 2014

As reported by Giles through the mailing list:

During my upgrade to Misterhouse 3.1 I noticed that devices set up as X10MS in items.mht don’t seem to have their {x10_id} set any more, clearly a workaround is to set them myself but its a but annoying.
e.g.
items.mht
X10MS, D5, Back_hall_MS13PIR, X10_item, MS13

Code to test if {x10_id} correctly set - in a loop through all X10_items;

print_log("found this list item $item->{x10_id} , $item->{object_name}");

Gives
30/08/2014 15:04:28 found this list item , $Back_hall_MS13PIR
where I would have expected;
30/08/2014 15:04:28 found this list item D5 , $Back_hall_MS13PIR

@hollie hollie added the bug label Oct 28, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant