SHAC/MQTT/HomeAssistant recall previous level

True story. Sensors are one way. The others are bi-directional because they are MQTT integrated in HASS, so any change there results in a topic publish which the SHAC is subscribed to and responds.

I think Powerwall data direct from SHAC might be more elegant than you think. It's the way I'd do it. Just one resident script.

If I get a moment I'll give the approach more naval gazing.

 

thanks for clearing that up. there have been many attempts to conquer Tesla Powerwall in HA and only recently did this integration appear - and it works. there are 2 control elements here that it is important to capture. they are "select options". covering operating mode, and backup reserve level + lots of sensors. it is called tesla_custom but I cannot locate it for some reason. there is no rush on this from my perspective now that a viable alternative is in place - thanks to you. others may be keen to see something. Note that the integration also covers Tesla cars

 

I haven't got one of those either. Just five BMs with engines that loudly go bang. I'll have a look at some LUA for you and others. Given I don't have any of this kit I might call on you for some testing if you're up for it.

 

happy to help if I can

 

Phenomenal work! I've finally gotten around to trying Home Assistant this week, so I thought I'd give your scripts a go.
For the most part, auto discovery works really well, I do seem, to have some issues with bsensors.
I've got a tag saved as :-
MQTT, bsensor, pn=Landing PIR, sa=Landing,

Which I believe should discover as a read only, on off value, but actually generates nothing.

Log errors are:-
* string: Warning: Read undeclared global variable "off"
* string: Warning: Read undeclared global variable "on"
* string: Error publishing outstanding CBus discovery topics: [string "Resident"]:633: attempt to concatenate global 'on' (a nil value)

If I change the tag to binarysensor, the device discovers it as a dimmable light

 

Thanks, @vworp. This is fixed and pushed as part of commit 1459706.

The keyword for binary sensor type is "binary_sensor". I have added the type without underscore as a synonym to prevent others also falling foul of a simple missing character.

 

Thanks.
I can confirm MQTT, bsensor, pn=Landing PIR, sa=Landing, on=Motion detected, off=No motion, is discovering correctly now.

 

Awesome, @vworp. For some reason, I don't get notified by email at cbusforums. So If you've any further issues then open an issue at https://github.com/autoSteve/acMqtt.

Cheers.

 

I've been thinking about this lately, Michael. How about something simple like this...

Tag an AC object with something like the below, with "isensor" being an inbound sensor? acMqtt could subscribe to the topic and publish any changes in the user parameter/GA. Should be quite simple to implement I reckon.

Code:

MQTT, isensor, topic=mymadeupsensor/value

 

This is done, @philthedill, committed at autoSteve/acMqtt.

 

Yep. My Python brain inadvertently does this at times to Lua. Thanks Daniel. Fixed.

 

And @daniel, if you like acMQTT (and are a Home Assistant user), then you might like https://github.com/BJReplay/ha-solcast-solar. I am a co-code owner over there doing much Python.

 

@ssaunders - Bloody Brilliant. Got this going tonight and I appreciate all your hard work - when I'm next in Melbourne I'll definitively PM you and buy you a few rounds of beer

Now its time to transfer all my PICED coding into HA and kiss goodbye to my CTC...

 

Having read through this chat, I am concerned that my Wiser 2 CBus system my fall outside of the scope of application for this script.
@ssaunders Before I attempt to do something that sends me down a deep dark rabbit hole, would you happen to know if the approach described here would work in my "first Gen" (circa 2017) Wiser 2 (5200WHC2) aka Wiser Home Controller 2 - which I understand is different to the later versions of Wiser Home controller.