Testing for v5.3.1 Release Candidate #1192
Comments
|
awesome! will check it out. thanks for the continued work. |
|
Thank you, all my devices have been rediscoverd! |
|
@gohamstergo Thanks for pointing that out! |
|
Finally got to working on this as staying home more during these times. Everyone stay safe and social distance.... |
|
Setting Device Brightness to 3% is not working. Alexa says OK but on the app, it shows Brightness 4%. I am Using 3% level to execute some routins. |
I didn't get that message, but i used the website (https://alexa.amazon.de/spa/index.html#appliances) to search for new devices. My Alex still says that the device seems not to work properly, but this is a different problem. |
|
For the devices saying that.. do you have "No State (Do not update state for device)" true or false? I've noticed Alexa saying that when I have that setting set true. When false, the problem goes away. |
|
It did not work for me. I still cannot discover HA-bridge devices. |
|
@gohamstergo Same thing if you do it from Mobile app by Deleting the Devices one by one then Alexa will not discover the Deleted Devices. |
|
Same here. It doesn't work. |
|
@cylon147 I don't use the web interface... what is your comment related to? Were you meaning to reply to @altheeagle? @Nachtfalke49 have you tried creating a completely new device AFTER updating and trying to discover that? You might have to recreate your devices if any possibly have the device ID errors related to bug #1139. |
|
@gohamstergo It works with new devices. |
|
Oh i have a lot of devices. That is a hard work. Thank you for the fast solution! |
|
I tried creating a brand new device. It still will not discover any Ha-bridge devices. |
Can anyone test this and Confirm Please. |
|
Can confirm. Here's my Domoticz log:
Four "On" commands and then the level+1. Interesting. I only have it set to send two commands. Not sure why it's doubling. |
|
Interesting as I get 3 for saying set to 3... Mar 27 11:45:29 condopi java[8865]: 2020-03-27 11:45:29,455 [qtp15028939-96] DEBUG com.bwssystems.HABridge.hue.HueMulator - Calling dim as requested. |
|
Hi, I tested it with two more new devices. Alexa has found the newly created devices. Then I hit "Forget All" and I had created more new devices. After that Alexa doesn't find any of my devices again. Unfortunately, that was not the full solution. |
|
Oh I have to make more devices. The last two have now been found. So it's a number problem. It seems that I cannot use the number again in Alexa after pressing "Forget All". |
|
Figured out my duplicate issue was just my two echos each sending the command...thought they were smarter than that, oh well. I asked for level 3 and am indeed getting 4 tho. Think its something to do with converting the 3% 0-100 scale to bri:9 0-255 scale? 03-27-2020 16:02:02.942 | DEBUG | HueMulator GET called on api/* with request <<</api/--/lights>>>, and body <<<>>> | com.bwssystems.HABridge.hue.HueMulator |
|
@gohamstergo So how did you get 9? I have the echo sending 7 and if I use the test dim on the page I get 8. Which both of those numbers get converted back to 3. What source are you using to control the ha-bridge to get 9? |
|
Im just asking my echo dot gen3 to 'set hallway to 3' and the log above is what i get. edit: tested with my echo dot gen1 and get same values. |
|
I just updated from 5.3.0RC9 to 5.3.1RC1. Alexa is not finding new devices with either. |
|
@EnGamma choose a device, edit/copy, give it a different name, then add bridge device. see if that one gets discovered. |
|
ok... I have come across the Major bug in my previous post I have mentioned that Alexa Executing different commands. This is because after Doing Renumber Device Alexa Not finding the change in uniqueid. As this is not being Changed when we do renumber devices. To test this out I have entered Devices with the name "Test 100" with Device ID 100 and so on up to Test 110 with Device id 110.
Now, I pressed the Renumber device so it did the re-id all the device. Again I rediscover the device as there is no Device Added only the IDs are changed Alexa Didn't find any Devices. this is Correct behavior but should work as it is as we have sent the updated Device list with Changed Device Ids but not when I execute Test 100 it Executed Device 102 as its Unique id didn't get updated after Renumber Device. So I have done Wireshark to check before and after the response(after pressing the Renumber Devices) of the Alexa nad Fond it's not updated the Uniquid means it's keeping the same uniques ID and this Brokes the whole Setup. I am POsting the Json Device list. Before pressing the Renumber Devices. After Pressing the Renumber devices as you can see Device id and Name gets reassociated but uniqueid remains the same. and this is why Alexa not differentiating the change.
To fix this problem i guess Device id and uniqueid and Device Name should be linked with each other. |
|
After update the device status update works fine. The REST API curl 192.168.0.2/api/pi/lights/3 works fine, but i can not switch on/off curl -X PUT -d "{"on": true}" "192.168.0.2/api/pi/lights/3/state" Did i do something wrong? |
|
#1044 fix is working fine, thanks |
|
@juergen2345 That looks correct. Did you turn on trace state changes and look at the log? |
When i send the off command:.. 4-08-2020 19:54:19.318 | INFO | Tracestate: hue state change requested: pi from 192.168.0.2 body: {on: false} | com.bwssystems.HABridge.hue.HueMulator i have also tried this on 5.3.0 - same result. |
|
Ok, the off command is represented properly by the {on:false} body. |
|
The log above was from an off command, when i try on then the log shows but ha-bridge doesn't execute the script.. (On 4.5.6 curl responses {"success":{"/lights/3/state/on":true}}, And the script was executed.) When i use for example the Test Off Button, the Command will be executed and the log shows 04-09-2020 07:17:05.616 | INFO | Tracestate: Calling on-off as requested: false | com.bwssystems.HABridge.hue.HueMulator 04-09-2020 07:17:05.635 | INFO | Tracestate: Decode Json for url items: [{"item":"/home/pi/Fernbedienung/Sonnenschutz.py up","type":"cmdDevice"}] | com.bwssystems.HABridge.hue.HueMulator 04-09-2020 07:17:05.676 | INFO | Tracestate: Calling Home device handler for type : cmdDevice | com.bwssystems.HABridge.hue.HueMulator |
|
@juergen2345 will take a look |
Had to rollback to 5.3.0 because Alexa Voice Control wasn't reliable anymore -> Sometime Alexa sends the "ok signal" but nothing happens, sometimes Alexa didn't recognized the device etc. Not sure if this is realy HA-Bridge related but I will observe the situation now after the rollback |
|
Switched to 5.3.1RC1 after Alexa stopped working with my devices on 20. April 2020. I got the message 'Device not responding' for all my devices. So I upgraded to RC1, added a new device in ha-bridge but Alexa is unable to discover neither any of the old devices nor the new one. I´m running on a Pi 2 port 80 and have 3 3rd gen. Echos, 3 FireTV Sticks and one Show 5 in my system. |
|
I'm using echo dot v1 & fibaro. facing issue that cant discover any device. Here's the log of me trying to discover, then turn on/off on of the device, then discover again.
I've tried using different version, v5.2.1, v5.3.0. all of them dont work too. any advice? |
|
Have you tried v5.3.1RC1? I did get it to work, but I often have to "Discover" about 5 times before it works. |
|
yeah the log that i posted is using v5.3.1RC1 thats why i posted here. but the log says v5.3.0. not sure if it is my mistake to use wrong version or this is designed by @bwssytems that it wont be 5.3.1 before official release. |
|
That is why I posted the comment. Your log header says 5.3.0. Perhaps your version update did not take? Take a look at the HABridge headers at the top and click "About" and see if the correct version shows up there. |
|
hmm do you mind to check if yours show 5.3.1? Im away at the moment. I'll try to reinstall and probably get a v3 echo dot to try since i saw ppl reported about bug with v1 |
|
MIne does show 5.3.1RC1. I checked before I posted. :-) I had no luck with V3 Dots. I bought a V2 and finally a V1, before I got it to work. |
|
ouch my bad then. will do another test tmr with 5.3.1RC1. thanks for the info! |
|
Ive tried with 5.3.1RC1, but still cant detect the devices.. any advice?
|
|
update |
|
I got this brightness issue. "Turn On [device]", the brightness gets set to 100%. |
|
Im trying to install 5.3.1RC in my RPi4, but it shows error below. anyone knows whats wrong? edit to add comments: I've confirmed that I've created habridge.service file and put in the code in /etc/systemd/system according to the procedure. May 23 09:20:03 raspberrypi kernel: [ 101.215378] fuse init (API version 7.27) |
|
Deleting Echo from my account and starting again did the trick , thanks jamietang68 :-) |
Same problem here after updating to latest release. I think it has something to do with the user name? Do we have to emulate creating a user first and then use the username from the response for the url? |
Try to escape the " with \" in the request: |
|
For those having control issues, make sure that you create a new uniquely named device to test. For example, I had an old device called heating, I deleted it, updated bridge versions, then created a new device called heating. Alexa found it and i could turn it on and off but alexa would always complain that the device want responding even though it worked. The way to check for a caching issue is to turn off all your Alexa devices, delete your device in ha-bridge, disable ha-bridge, delete the device in alexa app or web interface then do a discovery via app or web interface. If the deleted device comes back even though it doesn't exist anymore that may be causing issues for you. Even though I'd read that using the Alexa web interface was the way to remove all devices, it never worked properly as the deleted devices always reappeared on a discovery. The only way I found to successfully delete devices is to remove one at a time through the app, then turn off all Alexa devices and leave off for a few hours or more, then cross your fingers. I had to do this a few times to get it to forget all my deleted devices. Amazon need to sort there shit out. To reiterate. When deleting ha-bridge devices, first delete from the bridge, then delete from the Alexa app, then turn off your Alexa devices, then do a discovery via the alexa app or web interface to see whether these deleted devices have actually been cleared out Amazon's cache or not. If not you'll find these devices get recreated even though they no longer exist. |
|
Updated the link target for RC3, it was broken until now. |
|
All color conversions look to be fixed |
Perfect! THX |
Please post your issues or success with this new release candidate
https://github.com/bwssytems/ha-bridge/releases/download/v5.3.1RC5/ha-bridge-5.3.1RC5.jar
https://github.com/bwssytems/ha-bridge/releases/download/v5.3.1RC5/ha-bridge-5.3.1RC5-java11.jar
This release fixes the following issues:
#1044 Alexa app, error "Device doesn't support requested value" bug question
#1118 Device status update in Alexa App is not working correctly for ha-bridge devices bug duplicate question
#1126 Can't get XY ColorData into URL enhancement question
#1127 Can't get separate hue, saturation and brightness enhancement question
#1128 Wrong color calucation in HS mode bug question
#1131 Changing color temperatur is not working correctly bug question
#1132 Conversion from CIE to RGB incorrect bug question
#1139 Device ID creation fails bug question
#1170 Alexa not sending the correct color codes duplicate
#1171 Please add option: If bright request present with on, only send dim enhancement
#1184 Alexa will not discover HABridge question
#1191 When "Use UPNP Address Interface Only" is selected, echo cannot find ha-bridge bug
#1210 [Enahnacement] Have link button timeout be configurable enhancement
#1215 Alexa unable to discover recently added devices to ha-bridge duplicate question
#1227 Feature request: ${intensity.previous} value passing control enhancement
#1239 HA-Bridge has suddenly given up itself - Exception in thread "main" java.lang.NullPointerException bug question
#1243 Alexa device discovery now broke question
#1253 HABridge hue ColorDecode 0 0 0 bug question
The text was updated successfully, but these errors were encountered: