Releases: mabunixda/node-red-contrib-alexa-home
v1.3.1
v1.3.0
1.3.0 (2021-03-04)
🎁 Feature
- update to semantic versioning (96a3b9f)
🐞 Bug Fixes
- merge artifacts... (efeb904)
- missing supertest dependency... (91d5b8d)
- updates from master (73d9dc7)
- revert linting script (be24760)
- ci gh action (c3dce59)
- allow linting bypass argument 1 (a51a240)
- upgrade mustache from 4.0.1 to 4.1.0 (#85) (65c476d)
- upgrade mustache from 4.0.1 to 4.1.0 (#85) (279d50f)
Fix detection of gen3 devices
Thanks to @nepee for the input to fix some json stuff within the detection process.
Codecleanup + Registration fix for gen3 devices
Internal Code cleanup because of introduction of linting the Code... but
Also take fix from derSebbl to get Alexa Gen3 devices to work and hopefully fix #16
The change of the port is not made per default, because i expect not everybody to have port 80 open and available. It might also cause permissions problems, because that port might not be used by a default linux user e.g.
fix http/https configuration setup
http/https setup was incorrect routed through the node to reflect http/https setup of node-red
Start webserver for item information
SSDP and HTTP Server are now seperate components to provide information about items.
multiple fixxes
Fixing #21 to get on/off command back - this is now
msg.payload.command = "switch|bri|color"
and also round normalized bri to integer values
With this pull request also colors can be set as quested in #19 ..
the broadcast bug of #16 should now be solved because node-ssdp is listening on all available interfaces already. The setup.xml generation already used the host http header to reflect the incoming request to the setup output.
Also a finding was that alexa does not support endless response bodies. To get around this i stripped all spaces and unused settings from the json files. Hopefully this will solve the update problems #16
fix ssdp location announcement
Remove debug() dependency to cleanup logging
Logging is now done entirely via node-red routines
add error logging for missing node
#16 displayed the need that also error logs must be written when no controller node is available - even when this spams the logs when multiple alexa nodes are already present