saveKey throws deprecation warning
mschwartz opened this issue · 25 comments
In that.saveKey(), you call writeFile() without a callback. Node complains about it.
Maybe you want to call writeFileSync() ?
Or provide a default cb that does nothing.
Cheers
I think it's on line 140.
Awesome. You saved me the trouble of fork/PR
should be fixed with 6508cea
Sweet!
Thanks
Nice! I'm curious and looking forward to your release! :)
I'd be interested in collaborators, too.
I already got a quite comprehensive home automation running, based on MQTT as central message broker, incorporating Homematic, Homematic IP, Zwave and FS20 Actuators/Sensors for Heating/Shutters/Doorbell/Remotes/..., several Pis, NodeMCUs, DMX-, Hue- and Lightify-Lighting, Mopidy/Airplay based multiroom Audio, a selfmade Polymer UI and Node-RED, InfluxDB/Grafana, Splunk, Nagios and more... :) Most of the Software I'm using is contained in this List: https://github.com/hobbyquaker/awesome-mqtt
So I can't promise if I will contribute, depends if your architecture fits in my environment ;)
I'm using MQTT connected to microservices that collect device information.
The server is express, the client is React and react-bootstrap
The microservices are all dockerized and each can run on any host on your LAN.
I'm using one central server for the home automation software, though I run the microservices on my development machine while I'm working on them.
The separation between backend, client, and collection concerns makes it all plug and play. You can swap out the front end UI for one written in Polymer even :)
I've seen your awesome-mqtt page before. It's truly a great resource.
Here's what the dashboard looks like on tablet:
(it could use some visual love, but it's very functional)
And on phone:
My intent is to hang tablets on the wall in some of the rooms and phones in others. I have a $29 phone on my nightstand.
The software supports multiple dashboards so you can have one for the kitchen and a different one for the bedroom, each with appropriate display.
Nice, MQTT based microservices sounds good and your UI looks good too :) Put the stuff on Github and I will check it out! ;)
PS. found it, already watching the autodomo microservice-core repo :)
That's the one. Also on dockerhub;)
BTW, I bought one of these to be my Home Automation server:
https://www.amazon.com/gp/product/B00VBNSO8U/ref=oh_aui_detailpage_o02_s01?ie=UTF8&psc=1
I had a spare 60G SSD and bought a 4G RAM stick for it. The whole thing cost about $150. Not a whole lot more than the Raspberry Pi (I have one of those, too), but much faster CPU, far more RAM, it runs standard Linux distros, has USB 3 and gig ethernet, etc.
@mschwartz - Any update on your open source project.
Also how do you send commands for up and down through this?
The repos are here:
The main server/client repo:
https://github.com/RoboDomo/RoboDomo
LGTV microservice is here:
https://github.com/RoboDomo/lgtv-microservice
The onscreen joystick logic, which sends up/down/left/right/select:
@mschwartz - Awesome thanks.
I would like to add a "Screen off" feature. This is available in Settings -> ECO mode -> "Screen off" and this will turn the display off while leaving the TV and any music playing in the background.
Any idea on how I can add this button to RoboDomo? I cant see a direct method to turn screen off, so will probably have to use the KEY_LEFT, KEY_ENTER and so on and then navigate to ECO mode to turn it off?
It never occurred to me to use the screen off feature.
Adding a button to RoboDomo is trivial. I don't know what the code would be to toggle the screen on/off, though.
And the key codes are here (I don't see one for ECO modes):
@mschwartz Yes, looks like adding a button with a corresponding key code is trival on RoboDomo.
However, I cannot find the key code directly. Do you recommend me creating a chain of commands like Settings, UP, ENTER, ENTER, DOWN, DOWN, DOWN, ENTER and so on?
That way one button on the interface does all necessary steps in the background to navigate. I hope this makes sense. Do you recommend any other way?
It looks like it is missing a settings button. From there you'd choose "disable screen" (or whatever), right?
I haven't seen this "screen off" feature on my OLEDE6P, but I do see it on my Sony Bravia TV.
I play music with Spotify and use my AVR only, with the TV entirely off. FWIW.
Thats fine. Thanks for your help. I will just code it to chain commands in series and give it a go.
Yes, I have a growing youtube playlist with all unique songs that are not available on spotify and others.









