Issue with Shelly 2.5 voice control using mcsMQTT after HS4 upgrade

[alloyd]

Hi all,

I am 99% sure this is just me thing stupid but I cannot figure this out, I just updated from hs3 to 4, now using the hs4 interface I can control the devices fine, as in on/off, however what I cannot do is discover the devices in Alexa, other devices work ok and the Shelly devices via mcsMQTT worked fine with Alexa under hs3, now it may be something odd in my HS3 setup because it was so long ago I cannot remember but I cannot find anything to change in hs4, I had to delete all old devices from Alexa as none of them worked with hs4.

one thing I read was about how not having a control state can cause this, in hs4 I cannot even view these (on the Shelly devices, shows fine on others) but using the device utility page I can see they are set, so it might be my issue is nothing to do with this plugin and rather an hs4 issue but thought I would start here.

any help is appreciated,

Thanks,

Anthony

[Michael McSharry]

one thing I read was about how not having a control state can cause this, in hs4 I cannot even view these (on the Shelly devices, shows fine on others) but using the device utility page I can see they are set,

I do not use Alexa through HS so only can suggest based upon what I have picked up in the discussions. Your first picture show two control states and the controlUse is set to Off and On so this looks good for ability to control via Devices and Events. Your third picture shows the checkboxes to enable Alexa Discovery. There are multiple checkboxes and I think only one in HS3 for voice control. The settings look reasonable to me.

If there is something that is different between HS3 and HS4 for voice control then I would like to know so I can make any changes in the plugin if needed. You may have better luck in the General Discussion forum as it likely has broader viewing and would cover better specific HS expectations for voice control.

[alloyd]

Thanks Michael, I have just posted there, my gut is that it is an hs4 UI rather than your plugin specifically, massive thanks for the plugin by the way without it I would have gone to HA And I would have had many more headaches and a very annoyed wife when it falls over. Il come back to you if people come back with anything.

As a side point I tried changing the UI setting in your plugin from button to number to see if anything would change, it didn’t so I changed it back but I now don’t see the buttons in HS4 but if I go into the device utility view they still appear and operate fine so again likely not a you problem but HS4, im wondering if I would have been better with a clean install but it’s a bit of a pain.

[Michael McSharry]

A Shelly device, as well as most of the special case topics that are recognized work on the basis of HS Device/Feature creation upon first recognition of the topic. This allows the user to them customize without the plugin changing it back.

In your case there are two approaches that can be taken. One is to manually add a graphic (from HS Devices page) and any other edits desired after the button Control/Status UI was reselected. If you change the VSP definitions then do it from the Edit tab and not the HS Devices so the plugin remains in sync.

The other is to obsolete the specific Shelly device. One way is on the MQTT Page, General Tab, Obsolete Row and enter shellies/XXXX/# where XXXX is the identification used by Shelly for that specific model and serial number. For example shellies/shellyswitch25-C3DE88/#. This will remove this specific Shelly Device and its Features from HS as well from mcsMQTT Association table. The next time a topic is seen from this Shelly device then HS Device and Features will be created (with new Ref numbers). The other way to obsolete it is from the Association tab with a "O" column checkbox on the row where the parent Device is shown. This should complete the "O" checkbox for all the child features. Then use the Delete button at the top of the table for the "O" column.