Re: [mh] Where next with MisterHouse

Looks like the ia7 config page documentation needs updating. There is an ia7_config.json setting for on/off default rather than to pull up the property page. Toggle buttons are identified by a black border.

The ia7_config.json setting is direct_control:yes, for example:


  "objects" : {
	  “toggle_object" : {
		  "direct_control" : "yes"
	  },

> On Jan 4, 2021, at 9:15 AM, Richard F <[email protected]> wrote:
> 
> ...
> 
> UI. Much of my merge/update work in #Lockdown1 was on IA7. It needs a bit more work, but a huge amount has been done, and it works well, providing real state feedback for many of my items without much sweat.  I have made some improvements to multi-state items (e.g. Squeezeplayers control/show states), added optional 1-click activation for on/off's that was sorely missing, and 1 or 2 other tweaks. I got stuck on the missing drop-downs that I use a fair bit in IA5, and that's when summer came round.  I vote for more work on top of the great IA7 contributions already made.
> 
> ...
> 
> On 4/01/2021 10:54 am, Giles Godart-Brown wrote:
>> There has been quite a bit of activity recently on the Forum and I was wondering if we should plan what to do next.
>> 
>> Here are some questions that you may have views on;
>> 
>> Should we do another major release of what's currently in Master?
>> 
>> Do we need a new web UI?
>> 
>> How do we get more people to use and contribute to MisterHouse?
>> 
>> Is there anything we should deprecate or provide with a health warning?  Going through the docs and ./lib files, there are a lot of modules for redundant kit which is unlikely to be developed further (or even fixed) and is often not documented fully.
>> 
>> There has been a big change recently with cheap bi-directional Wi-Fi devices and MisterHouse wasn't really created with this in mind, notably we don't have a defined  feedback mechanism to check that when we change an item state this actually happens and we don't have a defined way of having an item with multiple states (perhaps we should encourage JSON for this), or multiple triggers (mqtt poses this question). I believe the industry is moving further in this direction, Tasmota wont be the last and only solution, so this begs the question; 
>> 
>> Do we need some architecture changes to support bi-directional devices with feedback?
>> 
>> If you have views/suggestions, please respond to this thread, if it gets too cumbersome, I'll split it onto a number of individual threads.
>> 
>> Stay safe
>> 
>> Giles
>> 
>> 
>> 
>> 
>> 
> ________________________________________________________
> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>

________________________________________________________
To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users