Works with the S31!

[boojew]

Just an FYI, without any mods, I got this to work with the S31!

One (quick?) request, would it be possible for you to make it possible to pass the docker container the mqtt parameters instead of having to fiddle with the downloaded hassdevice config file?If not, no worries!

What's interesting is that this model supports energy monitoring, but doesnt seem homemate can currently handle that..

[boojew]

Edit: Nope, I was not patient enough..

`2019-01-25 23:39:01,753 - b'458nlc0757rhtmor3vn3n5qm4vrsc9yj' sent payload: {'cmd': 127, 'serial': 18, 'uid': '2c3ae82f88b2', 'timestamp': 1548477541, 'energy': '0.85'}

Wow! Awesome. I assume that this is not being sent to HASS as I don't THINK the mqtt switch accepts energy as a parameter.. Likely a separate sensor would need to be built that.

What is also strange is that energy doesnt seem to be published to the mqtt stream quite as often as I would expect. When using the app it is pretty fast to update. In this scenario, it seems to publish fairly randomly.. I wonder if there is a message to send to provocate the switch to send energy data more frequently.

[insertjokehere]

Awesome! Nice find!

You are correct, the energy parameter isn't going to get passed to Home Assistant; in theory this shouldn't be too hard to get set up, but in practice... the MQTT abstraction code is a complete mess, and I've been meaning to clean it up for about a year now.

You should be able to configure everything by passing environment variables, whatever you would pass via the command line, make it all caps, and replace - with _ (so --mqtt-host becomes MQTT_HOST etc)

[boojew]

A clear sign I was tired - I didn’t even try environment variables. Ok cool. Will try tonight. I’ll try and see what I can figure out with MQTT. I’m a bit of a MQTT noob. I’m python isn’t that much better either, but hopefully I can get this going. :)

…

On Sat, Jan 26, 2019 at 12:24 AM Will Hughes ***@***.***> wrote: Awesome! Nice find! You are correct, the energy parameter isn't going to get passed to Home Assistant; in theory this shouldn't be too hard to get set up, but in practice... the MQTT abstraction code is a complete mess, and I've been meaning to clean it up for about a year now. You *should* be able to configure everything by passing environment variables, whatever you would pass via the command line, make it all caps, and replace - with _ (so --mqtt-host becomes MQTT_HOST etc) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA9_Dl2jtHLzQp_CRfVeDzr0vFPWzQpMks5vG-aWgaJpZM4aT_PB> .

[mssmison]

@insertjokehere awesome work on this. Confirmed working on my s31's as well. The easiest way I found after running the script was to put the device in pairing mode and attempt to add it in the homebridge app.
@boojew Did you figure anything out to pass the power data to HA over mqtt?

[boojew]

Yea and no. I have an open PR that will intercept the data and send it over mqtt, but it seems s31 only sends it on a useful frequency when the app tells it too, so I need to figure out how to send the command for that

[mssmison]

Sounds like you've got a great start and idea as to where to go
I'm happy to help with any packet captures from the app. Just let me know

[mkormendy]

Got this to work with homebridge too. Just waiting for @boojew to finish his modifications for his pull request to incorporate the energy monitoring.

[boojew]

@mkormendy getting it work with project required a (very) minor rewrite of an upstream library that insertjokehere maintains, but didnt want to immediately change. Meantime, I published this container with my changes https://hub.docker.com/r/boojew/homemate-bridge. I havent updated the main page at all.. sorry. There are 4 issues that I am aware and I documented them here https://github.com/boojew/homemate-bridge/issues. I will get around to fixing them soon. I hope.

[mkormendy]

LoL. No worries. This is github!

[boojew]

@mkormendy I have updated the container to work now properly as an energy sensor... but for some reason I broke the switch functionality... and I am really not sure why.. but in the meantime while I figure that out, if you want an energy sensor, there you go :)

[mkormendy]

LMAO... well I appreciate your silver lining perspective :-) I think I'll wait, as I need the switch more than the sensor, it's just an added convenience.

[boojew]

Actually - I think it may be an issue with my switch. I reverted back to @insertjokehere's container and I have the same issue. If you wouldnt mind trying mine, I wold be curious to see if it works

[mkormendy]

I think it’s the MQTT broker. My devices that rely on MQTT have suddenly stopped working. What MQTT broker are you using?

[boojew]

I'm using Mosca. I'm also using several services publishing to it and I havent seen any issues with them

[mkormendy]

I'm using Mosquitto .. any reason why you use Mosca? (just curious)