The following show up in my hapush.log when I turn on then off the light in HASS
2016-10-11 23:44:17,187 INFO switch.office_floor_lamp -> state = off, brightness = 30
2016-10-11 23:44:19,500 INFO switch.office_floor_lamp -> state = off, brightness = 30
The reason why I use light instead of switch in HASS is that the light toggle switch is much easier to click on compare to the on off lightning bolt switch. I did copy the hadimmer widget to halight and started to modify it, can you point me to the right file for cutting out the dimmer code, thanks
Something is mixed up in HASS then - both times hass is telling HAPush that the light has been turned off which explains the behavior - not sure why this is but it isn’t something I can fix in HADasboard.
You are right, I just tried the mqtt switch and I get this
2016-10-12 01:50:59,250 INFO switch.digoo1 -> off
2016-10-12 01:51:03,174 INFO switch.digoo1 -> on
and the switch icon works fine in hadashboard.
I guess I will convert all my mqtt lights to mqtt swtiches in HASS then I get both the problem solved.
Have you found any problem in the rss feed? Thanks
Sorry, my previous test on the switch is just a command swtich not a mqtt switch, the below logs are on the mqtt switch that I just converted from mqtt light.
Can you explain the behaviour b/w hass and hapush, for some reason, I still get “switch.office_floor_lamp -> state = off, brightness = 30” before it get the correct command everytime I toggle the swtich.
2016-10-12 02:09:44,409 INFO switch.office_floor_lamp -> state = off, brightness = 30
2016-10-12 02:09:44,474 INFO switch.office_floor_lamp -> on
2016-10-12 02:09:47,913 INFO switch.office_floor_lamp -> state = off, brightness = 30
2016-10-12 02:09:47,982 INFO switch.office_floor_lamp -> off
ps. the converted mqtt switch settings are identical to the old mqtt light settings, I just changed the title from light to swtich as it share all the same options.
I was toggling from the HASS dashboard, but I don’t know what happen, after rebooting the pi, it looks like that line is gone, so now it is behaving normally as follow.
INFO switch.office_floor_lamp -> on
INFO switch.office_floor_lamp -> off
I am going to reinstall the whole server from scratch soon, at the moment, the hadashboard can hang for few mins everytime I restart dashing and somehow causing the HASS halt too.
Fresh installed hassbian, hadashboard and hapush, a lot of weird problems disappeared, not sure what caused them to malfunction at the first place. Everything seems to load quicker and smoother, but my mqtt switch works unreliably after converted from mqtt light, so I have to convert them back to mqtt light and started to modify hadashboard (becaused i don’t want the dimmer function), cloned haswitch widget and created a new widget halight then modified jobs/homeassistant.rb and /hapush/hapush.py, everything works perfectly.
Next step is to find out how to get the rss works, if anyone can make the rss link from australia site works in the widget, please give me some hints, thanks
here are the 2 sample links that doesn’t work at the moment.
Yeah, looks like it’s happening using Sprockets, which is included in Dashing.
I’m trying to figure out if we can add an asset source path for SCSS files from the HADashboard application without modifying the Dashing gem. Ideally we could add the path to the Sprockets config when Dashing is initialized. Ruby is not my thing though so I’m really starting to get out of my element. What is the config.ru file for in the project?
After spending a day installing HADashobard on my Raspberry Pi1B! for an experiment, I thought I’d write some instructions on how I did that. Method is using Docker. Instructions have been built from a one day old memory so if any steps aren’t right, let me know.
I also tried to get the camera-widget to work, but no matter what i do, i can’t get it to write a new file, is that your case too?
I also tried to modify the unifiVideo widget to use hass camera api (/api/camera_proxy/camera.outdoor?token=19391345504), but still no luck, can’t write anything to the image folder, wondering if its permission issue, is there any error log in dashing so I can track down the errors?
Guys, found the log file and looked at the errors, and I finally got the camera widget working, stay tune, will test it thoroughly then upload here soon.
almost there, now the camera widget is working with hass camera api without SSL, can someone help to enable https in this function?
def fetch_image(host,old_file,new_file, cam_port, cam_user, cam_pass, cam_url) rm #{old_file} mv #{new_file} #{old_file}
Net::HTTP.start(host,cam_port) do |http|
req = Net::HTTP::Get.new(cam_url)
if cam_user != “None” ## if username for any particular camera is set to ‘None’ then assume auth not required.
req.basic_auth cam_user, cam_pass
end
response = http.request(req)
open(new_file, “wb”) do |file|
file.write(response.body)
end
end
new_file
end
Finally got it working using the hass api, so if your camera work on hass interface, now you can use it on hadashboard too. code based on the broken grubernaut/camera-widget
So now, what’s the best way to upload the code or if anyone want it at all, seems like I was talking to myself on all the post above, hahaha