Originally posted by kingfetty
View Post
Announcement
Collapse
No announcement yet.
wemos NodeMCU
Collapse
X
-
The form I'm using for the release number is automated:
Major.Minor.MMDDYY.HHMMSS of build
As for Beta/Release, if I compile it as debug it generates the Beta file package and uploads to the server, if I compile it as release it generates the Release package and uploads to the server. I also have another profile called LOCAL that does not generate a package.
Comment
-
Originally posted by kingfetty View PostJust to give you an update here and set expectations. I've combed through the fauxmo code and documentation (the code flashed to the nodeMCU that emulates Wemo) and it does not seem to support a few vital commands such as "GetBinaryState" or event subscriptions.
To level set here's what will be possible once I've completed my part.
- Status of the devices will always be unknown, you will not know if it's on/off and there's no way to find out.
- You will be able to control on/off of nodemcu devices with event actions or button click, but it will be a blind command.
- It will auto discover nodeMCU devices and create them in HomeSeer, I'll likely whip up a separate icon for them.
I'm brainstorming to see if there's a way I could either implement the nodeMCU commands with custom firmware I release or find some other trick to get the missing features working. I'll keep you updated here as things change, but I didn't want to leave you in the dark.
have you ever considered support for Tasmota or ESP Easy. Node MCU can be linked to HS3 by using MQTT. But it would be much cleaner to avoid MQTT by using you PI.
Comment
-
Originally posted by kingfetty View PostJust to give you an update here and set expectations. I've combed through the fauxmo code and documentation (the code flashed to the nodeMCU that emulates Wemo) and it does not seem to support a few vital commands such as "GetBinaryState" or event subscriptions.
To level set here's what will be possible once I've completed my part.
- Status of the devices will always be unknown, you will not know if it's on/off and there's no way to find out.
- You will be able to control on/off of nodemcu devices with event actions or button click, but it will be a blind command.
- It will auto discover nodeMCU devices and create them in HomeSeer, I'll likely whip up a separate icon for them.
I'm brainstorming to see if there's a way I could either implement the nodeMCU commands with custom firmware I release or find some other trick to get the missing features working. I'll keep you updated here as things change, but I didn't want to leave you in the dark.
any progress on the wemosMCU support?
Comment
-
Originally posted by kingfetty View PostBeen traveling for business the past 2 weeks and haven't had much free time. Hang in there it's coming.
thanks in advance.
Comment
-
Originally posted by kingfetty View PostSorry about the slow progress guys. A lot of stuff's come up lately to where I've not had the time I need to finish it up. The crappy thing is, the code is about 80% complete for the nodeMCU stuff, I just need to find the time to finish it. Just be patient, I promise it's coming.
Comment
-
Originally posted by kingfetty View PostSorry about the slow progress guys. A lot of stuff's come up lately to where I've not had the time I need to finish it up. The crappy thing is, the code is about 80% complete for the nodeMCU stuff, I just need to find the time to finish it. Just be patient, I promise it's coming.
Comment
Comment