SMUSEBY wrote:Thank you - but regrettably I need more guidance.
Basic question: for the gen1, I made the settings using the assigned IP address. Reading the forum, I think you mentioned that the settings can me made within Indigo. I took that to mean, use the 33.1 address to assign the Mac address, get the IP address, and do the rest in Indigo.
That is the goal. almost all the shelly settings can be updated via the MQTT protocol, so as long as the device and Indigo are talking over MQTT, the config setting should be configurable from Indigo.
SMUSEBY wrote:So when I attempted to follow the screenshot and use the IP address, and rebooted, does that update Indigo? - or should I do everything with the IP address as I did for the first gen products?
I'm not really following 100% here. When I get a new device, I power it on, connect to it's WiFi AP (go to the 192.168.33.1), and do the initial wifi and mqtt configuration from the browser.
SMUSEBY wrote:The MQTT Prefix in the screenshot includes 'shellyplugus' - is that a general heading for the US - i.e., is it no longer necessary to enter the product type?
That's because it is a screenshot of one of my devices - a Shelly Plus Plus (US). Your value will be different.
SMUSEBY wrote:What is the type? MQTT Connector Event, ShellyMQTT Event, or ShellyNGMQTT Event? Both of the Event types relate to switches, so I used the first,
-- Begin Action Item --The only trigger we are about right now is the MQTT Connector Event type. It is what listens to all MQTT traffic and determines which messages are put into the message queue to be processed by the Shelly Plugin.
You have a trigger named "MQTT Connector Event", and you have it configured to match on "shellies" and then "ANY". Therefore, this trigger will be executed any time a message comes across under the "shellies/<some_topic_path_here>" topic path. This is sufficient to match on ALL gen1 shelly device traffic. So we configured the trigger to then queue ALL these messages into a queued with a message type of "shellies". This works ONLY for the ShellyMQTT plugin.
Gen2 devices have basically no overlap in how they communicate with MQTT. Hence the need for this different plugin. This means we use a 2nd queue of messages (a different message type) and therefore a second trigger. I recommend you delete your existing trigger named "MQTTNG Connector Event" and make a new one. You need to configure it with:
- Code: Select all
Match: shellies-ng
Any:
and queue the message with a message type of "shellies-ng". This will result in all MQTT messages in topics under the "shellies-ng/<ANY_TOPIC_NAME_HERE>" to be put into a queue named "shellies-ng". This works because you correctly set the MQTT Prefix in the Web UI to be "shellies-ng/shelly1plus-b8d61a885b6c". It will match this new trigger's topic pattern because it is using the "shellies-ng/<SOMETHING>" topic pattern.
-- End Action Item --SMUSEBY wrote:Two screenshots attached showing my two triggers. Notice that for the gen 1 trigger, I don't have "/#" after the shellies. - but it works.
Please don't touch that gen1 trigger - we have it working
SMUSEBY wrote:As in my original screenshot, the device is not reporting a state, which I'm guessing has to do with the device, and not the trigger. - but I probably have the trigger wrong as well...
The device in Indigo has no state because it is not getting any data from MQTT. This is because your current trigger is wrong and isn't sending the MQTT messages to the plugin to therefore update the Indigo states.
SMUSEBY wrote:Here's another potential clue: in the Indigo Edit Device Settings, I am unable to make both the System and WiFi settings stick.
- In system, I enter the Device Name (same as in the LAN device configuration),
- or the WiFi page, I only complete the SSID, Password fields only for WiFi 1, and tick the Enable box for 'if the network is enable for use'.
- For both pages, I press 'Write Configuration' and 'Save', but when I reopen them, the fields are bland, and the MAC address: and Firmware: fields are grayed out (and blank).
Access Point is not enabled - my guess that the Access Point is only useful when using the 192.168.33.1 address, and only needs to be enabled for the initial setup.
Any more ideas?
--merged--
Another good catch - I corrected the MQTT prefix from shelly1plus to shellyplus1 - and now, in Indigo I'm happy to report some progress: the Indigo edit device settings are sticking for both system and wifi, but the device is not connected in Indigo.
Update - I just checked again, and the System & Wifi fields are once again blank. How can that be?
This is torture.
None of that works because this all relies on Indigo talking to the device over MQTT, which we have established is not working yet.