AUX1–4 switches workaround #30
Replies: 2 comments
That's not a bug...
...and that's not a workaround, that's a prelimiary condition, that NPAux works. See also HA thread NPAux command are never build-in in Tasmota firmware by reasons, it must always be provided by the Berry command extension. This integration does not build commands for your sugar valley, it's a MQTT-interface between Tasmota + NeoPool and HA. Commands must always be provided by Tasmota + NeoPool (+ Extension). |
Hi. @curzon01 explained it perfectly. The real bug is the release notes of v5.0. I'll amend them immediately explaining the pre-requirement to execute those commands.
I just want to add that the integration is not a "companion", but it replaces the package. I'll probably archive the package inviting users to replace it with the full integration that is much better, and we will maintain only that one in the future. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi Alex,
I'm not really reporting an issue, but wanted to provide some information.
I'm running your latest v5.1 yaml package.
V5.1 release notes:
Known issues (carried over)
AUX1–4 switches (neopool_mqtt_aux_switch) send
cmnd/SmartPool/NPAux — that command name does not exist in the
Tasmota NeoPool driver's command table (verified against kNPCommands at
driver lines 1301–1340). State reads work (from
NeoPool.Relay.Aux[]), but writes are silently ignored by the
firmware. This bug is present in both this package and the companion
Python integration.
On my installation your neopool_mqtt_aux_switch code works perfectly with this workaround:
https://tasmota.github.io/docs/NeoPool/#esp32-adding-user-defined-neopool-commands-to-tasmota
All reactions